Feature suggestion - custom tags

[nickbe]

I'd like to suggest that managers are allowed to create custom tags which can latter be assigned to tickets by staff members.

This would be a great way to be able to filter tickets without over complicating things.
Tags could be used to represent tickets status as well as different projects or technical terms....

[nickbe]

Are custom tags considered?

Afterthoughts:
Tags could be used like this
(Milestone 1.1) (Bug) (Idea) (Feature) (Rejected) (billable) and suchlike

[nickbe]

Any thoughts about this? I wonder why no one has asked about this. It seems so easy to handle and can be used for so many purposes.

[ivandiazwm]

Yes, this is a feature that should be added to our list.

[nickbe]

Excellent! In my opinion one of the most useful funtions when you think about it

[ivandiazwm]

@nickbe @mredigonda @guillegiu I've some ideas for the design of custom tags. Please let me know what do you think.

1. We will first need a new tab for managing custom tag, it should look like this:
   

2. We can use the component ColorPicker (like Topic form) supporting add/edit a tag
   
   

3. Regarding presentation, we could have it in a second line under the title
   

4. Or it may be better to have it the same line and move to a new line if it overflows.
   
   

5. An alternative could be to put inside the tooltip to avoid style breaking.
   

6. We will also need to add a field in the ticket view header and in the ticket list filter.
   

I'm thinking we could make something similar to the Semantic-UI multiple selector:
https://semantic-ui.com/modules/dropdown.html#multiple-selection
The component could be DropDownMultiple or something similar.

8. If we want to avoid to create this component because we feel it could take a lot, we may just add checkboxes with the tags.

[nickbe]

Hi Ivan,

first - thanks for all this effort. Excellent drafts and ideas 😄

The semantic selection (https://semantic-ui.com/modules/dropdown.html#multiple-selection) looks great and I cannot imagine a better way for multiple tag selection. It's defintely something worth implementing for this task.

The ticket line: In this example the ticket title is only one word, but taking a look at our real world titles they are at least one line, two most of the time. I'd try to take no.3 - but I think the best way is to show the tags ABOVE the title line(s) and not below. Maybe you could give this a shot.

I have nothing to add to the custom tag editor. Simple and effective. Great thing!

As for the popup: I would rather try to avoid it completely. The open/closed status should be in the list. The same goes for the owned flag - although I would replace it with a simple icon, together with the comments counter - just use a simple bubble counter in the list.
Finally the priority: I would replace it with the custom tags completely. Same effect and the tags filter would definetely suffice.

Thanks Ivan. OpenSupports is definetely is going to be fine!

[versavius]

Yes this would be a very powerful feature, something to consider is with tickets having tags you can do all sorts of reporting based on tags.

You could even later on create automatic rules to auto tag tickets based on certain criteria, but that is something for another day, just a thought for after this gets added

[nickbe]

I think it's definetely too complicated to maintain and handle. OpenSupports should be installed / configured within a minute.

[versavius]

I think it's definetely too complicated to maintain and handle. OpenSupports should be installed / configured within a minute.

Do you mean tags or rules ? If you mean rules then yes i agree that can get quite complex

[nickbe]

Rules are too complicated to handle.