Ticket #4005 (closed enhancement: duplicate)
Opened 5 years ago
Last modified 4 years ago
[PATCH] - Enable user-definable Ticket Query Result Fieldsets
| Reported by: | ilias@… | Owned by: | mgood |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | report system | Version: | devel |
| Severity: | normal | Keywords: | query |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description
There are several methods to implement user-definable ticket query fields (fields which should shown in the query result table).
The basic one would be to define the default fields within the trac.ini
The location within the code should be this one:
source:trunk/trac/ticket/query.py#rev=3999#L106
Other options could be defined there, too (e.g. "verbose").
Several thoughts can be found here (not yet verified):
http://dev.lazaridis.com/base/wiki/PlanTicketQueryMacro#FieldSelection
Is there any document available, which shows the planned changes mentioned in [http://groups.google.com/group/trac-dev/msg/377b428936e0676a this message}?
Attachments
Change History
comment:1 Changed 5 years ago by ilias@…
Changed 5 years ago by ilias@…
- Attachment TicketQueryDefaultFieldsOrderOption.diff added
basic implementation
comment:2 Changed 5 years ago by ilias@…
reminder: see description in thread
Most of the code is already in trac 0.11dev.
What is missing is the part with the user defined query-result-fieldsets, which overrides the automated fieldset selection completely, thus a user can control the format of the resulting table.
diff against older version of trac (some code is already within trac 0.11dev)
see a related discussion subjecting naming and further functionality.
I can provide the final patch, but would need to know the preferred naming.
(Note: the code is actively tested on my and on the customers 0.11dev production environments since a few weeks)
comment:3 Changed 5 years ago by ilias@…
- Summary changed from Provide Option to Define Default Ticket Query Fields to [PATCH] - Enable user-definable Ticket Query Result Fieldsets
comment:4 Changed 5 years ago by ilias@…
An alternate implementation would be:
- ability to define fields via a query parameter "fields"
- fields=ID|title|modified|*dev
"*dev" would be defined within the trac.ini (naming as suggested by mgood: fieldalias)
comment:5 Changed 5 years ago by cboos
- Milestone set to 0.12
comment:6 Changed 5 years ago by cboos
- Component changed from general to report system
- Keywords query added
- Owner changed from jonas to mgood
comment:7 Changed 5 years ago by ilias@…
can this please be included with the 0.11 version?
This is the last part of the "ticket query" commercial task.
The functionality is ready implemented, and tested on 2 production systems, and enables a very flexible use of queries within the wiki.
I can provide the initial patches and modify them based on the further requests from the team.
comment:8 follow-up: ↓ 9 Changed 5 years ago by cboos
- Milestone 0.12 deleted
- Resolution set to duplicate
- Status changed from new to closed
This will be possible in 0.11 with a combination of #2409 and the possibility to add things like e.g. col=priority&col=user_field and row=description to the default query.
comment:9 in reply to: ↑ 8 ; follow-up: ↓ 10 Changed 4 years ago by ilias@…
Replying to cboos:
This will be possible in 0.11 with a combination of #2409 and the possibility to add things like e.g. col=priority&col=user_field and row=description to the default query.
That's not the same effect. For anyone interested:
http://dev.lazaridis.com/base/browser/infra/tracx/tracx/query.py@152
I have this addition ready, but must first apply the other patches prior to producing the final patch.