starred/ViMbAdmin-opensolutions
1
0
Fork 0
mirror of https://github.com/opensolutions/ViMbAdmin.git synced 2026-04-26 08:45:54 +03:00
Code Issues 16 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #48] Quota fields should indicate what measure will be used #41

New issue
Closed
opened 2026-02-26 09:35:22 +03:00 by kerem · 6 comments
kerem commented 2026-02-26 09:35:22 +03:00
Owner
Copy link

Originally created by @rimas-kudelis on GitHub (Sep 16, 2013).
Original GitHub issue: https://github.com/opensolutions/ViMbAdmin/issues/48

The quota fields currently look like "Quota: [___x]" It's unclear whether that quota is in bytes, kilobytes, megabytes or whatever.

I suggest that either the labels should be more concise (e.g. Quota (KB):), or the fields should have add-ons (similar to the address field when creating new mailbox).

Originally created by @rimas-kudelis on GitHub (Sep 16, 2013). Original GitHub issue: https://github.com/opensolutions/ViMbAdmin/issues/48 The quota fields currently look like "Quota: [____x_]" It's unclear whether that quota is in bytes, kilobytes, megabytes or whatever. I suggest that either the labels should be more concise (e.g. Quota (KB):), or the fields should have add-ons (similar to the address field when creating new mailbox).
kerem closed this issue 2026-02-26 09:35:22 +03:00
kerem commented 2026-02-26 09:35:23 +03:00
Author
Owner
Copy link

@barryo commented on GitHub (Sep 16, 2013):

Fixed in the yet to be released v3.

<!-- gh-comment-id:24537296 --> @barryo commented on GitHub (Sep 16, 2013): Fixed in the yet to be released v3.
kerem commented 2026-02-26 09:35:23 +03:00
Author
Owner
Copy link

@rimas-kudelis commented on GitHub (Sep 24, 2013):

I don't see the relevant commit. Or do you mean the bug was fixed before I even reported it? If so, then which branch is it?

<!-- gh-comment-id:24990824 --> @rimas-kudelis commented on GitHub (Sep 24, 2013): I don't see the relevant commit. Or do you mean the bug was fixed before I even reported it? If so, then which branch is it?
kerem commented 2026-02-26 09:35:23 +03:00
Author
Owner
Copy link

@barryo commented on GitHub (Sep 24, 2013):

On 24/09/13 11:06, Rimas Kudelis wrote:

I don't see the relevant commit. Or do you mean the bug was fixed before
I even reported it? If so, then which branch is it?

This has been pushed to GitHub yet. All V3 work is being done offline
until pushed later.

  • Barry
<!-- gh-comment-id:24991768 --> @barryo commented on GitHub (Sep 24, 2013): On 24/09/13 11:06, Rimas Kudelis wrote: > I don't see the relevant commit. Or do you mean the bug was fixed before > I even reported it? If so, then which branch is it? This has been pushed to GitHub yet. All V3 work is being done offline until pushed later. - Barry
kerem commented 2026-02-26 09:35:23 +03:00
Author
Owner
Copy link

@rimas-kudelis commented on GitHub (Sep 24, 2013):

Hm, if I may wonder: why is the v3 work not public (yet) then?

<!-- gh-comment-id:24992649 --> @rimas-kudelis commented on GitHub (Sep 24, 2013): Hm, if I may wonder: why is the v3 work not public (yet) then?
kerem commented 2026-02-26 09:35:24 +03:00
Author
Owner
Copy link

@barryo commented on GitHub (Sep 24, 2013):

On 24/09/13 11:42, Rimas Kudelis wrote:

Hm, if I may wonder: why is the v3 work not public (yet) then?

It's development was / is part of a commercial project and we took the
decision to work on our internal development platforms (as part of the
bigger project) for it.

It will all be public as soon as I get a chance to tidy, document and
push it.

  • Barry
<!-- gh-comment-id:24993044 --> @barryo commented on GitHub (Sep 24, 2013): On 24/09/13 11:42, Rimas Kudelis wrote: > Hm, if I may wonder: why is the v3 work not public (yet) then? It's development was / is part of a commercial project and we took the decision to work on our internal development platforms (as part of the bigger project) for it. It will all be public as soon as I get a chance to tidy, document and push it. - Barry
kerem commented 2026-02-26 09:35:24 +03:00
Author
Owner
Copy link

@rimas-kudelis commented on GitHub (Sep 24, 2013):

2013.09.24 13:50, barryo rašė:

It will all be public as soon as I get a chance to tidy, document and
push it.

Do you have an ETA on this? Or at least the list of biggest changes?

Rimas

<!-- gh-comment-id:24996892 --> @rimas-kudelis commented on GitHub (Sep 24, 2013): 2013.09.24 13:50, barryo rašė: > It will all be public as soon as I get a chance to tidy, document and > push it. Do you have an ETA on this? Or at least the list of biggest changes? Rimas
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
dependabot/composer/smarty/smarty-4.3.1
v2
3.4.1
3.4.0
3.3.0
3.2.1
3.2.0
3.1.1
3.1.0
3.0.15
3.0.14
3.0.13
3.0.12
3.0.11
2.2.4
3.0.10
3.0.9
3.0.8
3.0.7
3.0.6
3.0.5
3.0.4
3.0.3
3.0.2
3.0.1
3.0.0
2.2.3
2.2.2
2.2.1
2.2.0
2.1.0
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.1
2.0.0
0.3.4
0.3.3
0.3.2
0.3.1
0.3
Labels
Clear labels   
bug

   
feature

   
feature

   
improvement

   
improvement

   
pull-request

Mirrored from GitHub Pull Request

No labels
bug
feature
feature
improvement
improvement
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ViMbAdmin-opensolutions#41
No description provided.