#11847 closed enhancement (fixed)
context navigation link to query should be renamed "New Custom Query"
Reported by: | Christian Boos | Owned by: | Christian Boos |
---|---|---|---|
Priority: | normal | Milestone: | 1.2 |
Component: | query system | Version: | 1.1dev |
Severity: | minor | Keywords: | |
Cc: | Branch: | ||
Release Notes: |
Renamed contextual navigation link Custom Query to New Custom Query. |
||
API Changes: | |||
Internal Changes: |
Description (last modified by )
It is not obvious to know beforehand whether following the "Custom Query" navigation link will return to the last custom query or start a new one.
It will always start a new one, so better make this clear.
See previous discussion in ticket:9617#comment:16.
Proposed change: [94561409/cboos.git]
Attachments (0)
Change History (10)
comment:1 by , 10 years ago
Summary: | context navigation link to query should be renamed "New Context Query" → context navigation link to query should be renamed "New Custom Query" |
---|
comment:3 by , 10 years ago
I've been confused by the behavior. The change looks good, and should help reduce confusion. New Query might even be sufficient if we wish to reduce the length of the navigation item label.
comment:4 by , 10 years ago
Milestone: | 1.1.3 → 1.1.4 |
---|
comment:5 by , 10 years ago
Milestone: | 1.1.4 → 1.1.5 |
---|
comment:6 by , 10 years ago
Milestone: | 1.1.5 → 1.1.6 |
---|
Retargeting tickets that I think won't be completed for 1.1.5, but please move back if I'm incorrect.
comment:7 by , 9 years ago
Milestone: | 1.1.6 → next-dev-1.1.x |
---|
comment:8 by , 9 years ago
Milestone: | next-dev-1.1.x → 1.2 |
---|---|
Owner: | changed from | to
Release Notes: | modified (diff) |
Status: | new → assigned |
I'm going to push the change if there are no concerns. Rebased in log:rjollos.git:t9617-new-custom-query.1.
comment:9 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Committed to trunk in [14232].
comment:10 by , 9 years ago
Owner: | changed from | to
---|
… of course ;-)