Customize custom query report

[mape <th07@…>]

It should be possible to customize custom query output columns, like the code currently says:

• # FIXME the user should be able to configure which columns should, branches/0.10-stable/trac/ticket/query.py@6280#L101​
• # FIXME Make this configurable on a per-user and/or per-query basis, branches/0.10-stable/trac/ticket/query.py@6280#L139​

It would be nice if this could be configured statically to trac config. It should be still possible to override this on the fly, e.g. with query parameters or session variables.

[Emmanuel Blot]

Definitely not for 0.10.5: enhancements are not added to a frozen branch.

[mape <th07@…>]

I use ​TimingAndEstimationPlugin. Obviously I want to see estimatedhours & totalhours in reports. Thus the essential parts from config look like this:

[ticket-custom]
estimatedhours = text
estimatedhours.label = EH
estimatedhours.order = 1
estimatedhours.value = 0
totalhours = text
totalhours.label = TH
totalhours.order = 4
totalhours.value = 0

[ticket]
query_cols=id,priority,summary,owner,estimatedhours,totalhours

And results can be seen from Candidate1_screenshot.JPG​

If I want customized results, I can override columns with query string. For example I would use link below to report top level product backlog items (type=epic):

[query:order=priority&cols=summary&verbose=1&type=epic Epic Backlog Items]

[mape <th07@…>]

Replying to eblot:

Definitely not for 0.10.5: enhancements are not added to a frozen branch.

Should I propose this as defect and fix candidate then because code says: FIX_ME ;)

Ok, I don't know well your branching policy. I thought that this is still branch where small fixes & improvements are taken into account. It would make sense to keep development for 0.10.x because many production environments use it and can't migrate (e.g. depending on plugins that are available only for 0.10.x) to 0.11.

[osimons]

Replying to mape <th07@homepelko.com>:

Should I propose this as defect and fix candidate then because code says: FIX_ME ;)

Well, it is fixed in trunk - for upcoming 0.11 release. As eblot says, this won't be backported the 0.10-stable branch.

The policy for branches is essentially that it is reserved for important bug fixes and security issues. This request for configuring colums is an enhancement that changes various internals + adds some visual elements to actually make selections possible. Like many, many other 0.11 features you will have to upgrade to get them.

For 0.11, columns can be added as paramteres like this: &col=id&col=summary

Duplicate of #2821.

[mape <th07@…>]

Replying to osimons:

Well, it is fixed in trunk - for upcoming 0.11 release. As eblot says, this won't be backported the 0.10-stable branch.You will have to upgrade to get them.

Thanks for your feedback & great software!

I understand that your eyes are in 0.11 (even in 0.12/1.0 already). Thus you have little interest for 'shipped' versions.

Unfortunately many 3rd plugins are not 0.11 compatible and thus there is no change to upgrade. In general 0.11 should have been released 'officially' & tagged. Then it would take few months untill plugins are made compatible to tagged version. After that one could consider migrating production environments. I consider that realistic schedule to upgrade production environments to 0.11 is 0,5 - 2 years

But this is general discussion about opensource, stability, production, migrating etc. and thus should be recorded to somewhere else (where?) for others to refer. So I won't continue this discussion here anymore :)