Over the last 2 years, the FDT team has received tons of ideas (about 600) for feature requests and improvements, both big and small. With so much feedback it can be hard to ‘see the forest for the trees’, both for the community (when voting and making suggestions) and for the team. There also is the issue that so many great ideas are submitted but get lost in the shuffle.
For this reason when we start seeing a trend of ideas that look related, we’ll begin consolidating the ideas into a ‘Meta_Ticket’. The prefix ‘Meta_Ticket’, is really to help for searching JIRA for such trends. It’s not the typical JIRA way and it has drawbacks but it’s something we’re going to try. If it turns out that a better solution exists, we’ll move on to that.
So far we’ve seen some interesting things when we combine these tickets and it’s looking good. An example of this is this ASDocs ticket:
When we started to pull these ideas together, we could see that users are asking for better ASDoc support in many different places and ways. When we consider how to deliver this feature best, we now have an outline of how people want to use an ASDocs implementation, as well as how important it is to them.
Searching For Tickets
When you’re about to file an improvement or feature request, consider looking at existing ‘Meta_Tickets’ first. This way you can see if other users have been voting on a similar theme. If so, you can submit your comment about this theme and even improve upon suggestions from others.

After going to FDT’s search page, you can simply do a search for ‘meta_ticket’ in the Text Search box seen in the screen above. Give it a try and let us what you think.
Comments