Configurable Issue Information about tinyissue HOT 8 CLOSED

I do plan to build tags into the system which I think could replace all these. I am very against priorities but some people feel the need for them, which I understand. What do you think about having a tag system in place instead of 3 separate fields that you described?

from tinyissue.

I like tags too, as you can tag anything with anything. Makes it totally user driven.

The need for priority is in a multi-developer environment, where I as the lead, assign tasks to others. It would be nice to be able to say, stop what you are doing and do this one first.

So, how can I help?

from tinyissue.

Hi,

Perhaps it's worth splitting these up into different tickets. Status seems like the most important one to be implemented next. At the very least I'd like to be able to configure a list of statues for a ticket beyond open & closed. So onhold, invalid etc

from tinyissue.

Hey @mikelbring did you have any rough ideas on how the tags system might work? Seems like the next logical thing to add, would be happy to do some work on it to get things moving.

from tinyissue.

As developper I like to sort by priority, and sorting by tags is unpractical.

from tinyissue.

One solution would be to add a field for tags,
and to create tags like status:resolved, status:fixed, priority:A, priority:B and so on (you get the idea).

By enabling the user to get a list of all tags matching a wildcard pattern (e.g. status:*, priority:*), or better, a list of all issues grouped by the tags matching that wildcard pattern,
you could implement all three fields mentionend by North2Alaska,
while still staying completely user configurable.

In the future, sorting by priority could be implemented on top of this by employing the (yet to come) plugin API;
the same goes for coloring according to a priority.

from tinyissue.

What @ghost described sounds like a really good solution.

from tinyissue.

I started implementing this, and need some suggestions:

1. So far, I have defined status:open, status:closed, type:bug and type:feature. I reused the colors that come with the existing labels, but that's not enough. Can someone post a sample list of tags with colors that should come predefined with my commit?
2. Assuming that status:open and status:closed should come predefined, should I get rid of the issue status flag and tie the open/close process to the automatic management of these two tags?
3. How should the tag changes show up on the activity dashboard, and should they show up there at all?
4. Should tags be restricted to a certain regular expression, such as an alphanumeric prefix:suffix format?
5. Which roles should be able to add new tags to the system, and which roles should only be able to use existing ones?

Thanks.

from tinyissue.