Opened 16 years ago
Closed 16 years ago
#7865 closed enhancement (fixed)
Add owner name to TickeyQuery macro in compact form.
Reported by: | Owned by: | Christian Boos | |
---|---|---|---|
Priority: | normal | Milestone: | 0.11.3 |
Component: | ticket system | Version: | 0.11.1 |
Severity: | minor | Keywords: | query |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
I believe the syntax was added in #2502.
This allows for grouping in compact mode. It is nice but could be improved. In my trac I currently have:
[[TicketQuery(format=compact,group=owner,status=!closed,milestone!=future)]]
which renders as:
#17,40, #1,8,10,13,26,27,34,35,41,43,44,45,48,50,52,55,58,59, #54, #33, #16,22,23,24,30,31,32,36,47,49,51,56,57
This is very nice but I believe the grouping should have the label prepended, so:
[[TicketQuery(format=compact,group=owner,status=!closed,milestone!=future)]]
would render as:
userX #17,40, userY #1,8,10,13,26,27,34,35,41,43,44,45,48,50,52,55,58,59, userZ #54, userW #33, userQ #16,22,23,24,30,31,32,36,47,49,51,56,57
This way it will be a lot simpler to identify which group is what not only the grouping itself.
I believe this is a very trivial change, but I'm not entirely sure where is this variable stored, is it query.group?
Attachments (0)
Change History (3)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Description: | modified (diff) |
---|---|
Keywords: | query added |
Milestone: | → 0.11.3 |
Owner: | set to |
Severity: | trivial → minor |
I'll look into this.
comment:3 by , 16 years ago
Milestone: | 0.11.4 → 0.11.3 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Fixed in r7847.
I'm really sorry I messes up :( I forgot to preview and now the ticket looks like spam, could someone edit the description.