display ticket-summary in "tags-query"

[developer@…]

I could not find any information, how I can modify TracTags, that in the tags-query-result the ticket-summary is shown additional to the ticket-no.

Is there any option for that?

Or is a hack necessary to handle that? If so... where to dive into what code?

[developer@…]

actual result for tags-query, no ticket-summary displayed

[Steffen Hoffmann]

Found this right now. Did you care to ask on the th-users mailing list first?

Because you're here on a plugin development tracking system, your request doesn't fit in so good. The maintainer has gone for months, if not years - well actually a couple of reasons, why you really should follow my advise to ask about non-bug-issues on the list first.

You don't mention the exact version you use(d) for testing this. Only recently we've added several new ways to display (listtagged) query results. This is already in the trunk development branch, if you like to check it out. Or wait a few more months for the next release (tractags-0.7).

You certainly know, you can find all available options with some documentation at the TracIni page of your own Trac site(s), don't you? Watch out for the options

• default_format and
• listtagged_default_format

Hopefully you'll see, that you don't need to hack it yourself. Please reply with your findings.

[Ryan J Ollos]

Replying to hasienda:

You certainly know, you can find all available options with some documentation at the TracIni page of your own Trac site(s), don't you?

I find that this point frequently escapes users, perhaps mostly new users. I added a note to the project page about the additional configuration options in 0.7dev.

[Steffen Hoffmann]

Replying to rjollos:

...
I added a note to the project page about the additional configuration options in 0.7dev.

Sure, +1 for making this more explicit.

[Steffen Hoffmann]

Seemingly the documentation changes have been sufficient, because we didn't see similar complaints and questions recently.

[Steffen Hoffmann]

For reference: Relevant changes have been done when resolving #9064. This ticket has driven the complementary documentation update.