Opened 18 years ago
Last modified 10 years ago
#4980 new enhancement
configurable default value for "Group results by" in Milestone view
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | low | Milestone: | next-major-releases |
Component: | roadmap | Version: | |
Severity: | minor | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
It would be nice to have ability to define default value for field "Group results by"
Attachments (0)
Change History (4)
comment:1 by , 18 years ago
Description: | modified (diff) |
---|---|
Milestone: | 0.11 |
Resolution: | → wontfix |
Status: | new → closed |
Summary: | Ticket Query → ue |
comment:2 by , 18 years ago
Component: | ticket system → roadmap |
---|---|
Summary: | ue → configurable default value for "Group results by" in Milestone view |
comment:3 by , 10 years ago
Priority: | normal → low |
---|---|
Resolution: | wontfix |
Severity: | normal → trivial |
Status: | closed → reopened |
Hey @cboos,
I second this option.
This is the most frequently used view at our company. Everyone uses it because we work by Milestones, always. I do not use the "View Tickets" tab, only the "Roadmap" tab.
Also, every time I open Trac I have to change the default value with three clicks, not one. The default of "Group Results By: Status" is changed by1) Opening the drop down, 2) clicking on the value you want, and 3) clicking on "Update"
Also, if it is configurable, it won't affect those that don't touch it, so I don't think it will be "not optimal" for anyone, since those that like the current default will not be affected.
Hopefully this can change your mind. We love using Trac. If not, feel free to mark it as wontfix again, I only changed it for re-consideration. Thanks for the hard work :-).
comment:4 by , 10 years ago
Milestone: | → next-major-releases |
---|---|
Owner: | removed |
Severity: | trivial → minor |
Status: | reopened → new |
Probably ;-) But for every default choice in the system, the choice will look good to some, and not optimal to others.
As a rule of thumb, if the alternative is just one click away (as it's the case here), then it's probably not worth making it configurable. Unless it's a very frequently used view, like for example the default report or query one can see when clicking on View Tickets, but that's not the case here.