TagPlugin should support Custom fields

[anonymous]

This would really increase this plugin usefulness

[Alec Thomas]

Patches welcome ;)

[anonymous]

I'd make a patch if I had more python chops and time.

But to add to the wishlist on this ticket, it would be useful to be able to not only create tags from custom fields, but to also map custom fields to a tag 'realm'. Realms already exist to differentiate between tickets and wiki pages.

The use case I have in mind is to use tags to group all the tickets related to an umbrella 'feature' together. By adding a separate 'feature_tag' custom field - we can do some interesting report to track the number of open/closed tickets per major feature per milestone, etc. If we could make the feature_tag value a tag as well, then it would make it easy to search for the tag to find all the tickets (and wiki pages) associated with a given feature. Taking that one further, if we could create a 'feature:' realm, we could then show just the tag cloud for that realm -- essentially auto-generating a high-level list of features.

Anyway that's the idea.

[Steffen Hoffmann]

#4200 has a patch, that proposes changes for providing some of the basic functionality requested here.

[Steffen Hoffmann]

In 13815:

TagsPlugin: Completing preparation for v0.7 release.

Availability of that code as stable, tagged release
closes #2429, #3359, #3610, #3624, #3677, #3754, #3864, #3947, #3983, #4078, #4277, #4503, #4799, #5523, #7787, #7857, #8638, #9057, #9058, #9059, #9060, #9061, #9062, #9063, #9149, #9210, #9521, #9630, #9636, #10032, #10416, #10636, #11096, #11147, #11152, #11274, #11302, #11658 and #11659.

Additionally there are some issues and enhancement requests showing progress,
but known to require more work to resolve them satisfactorily, specifically
refs #2804, #4200, #8747 and #9064.

Thanks to all contributors and followers, that enabled and encouraged a good
portion of this development work.