Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature suggestion - custom tags #146

Closed
nickbe opened this issue Feb 1, 2018 · 10 comments · May be fixed by shaneomatz/opensupports#7
Closed

Feature suggestion - custom tags #146

nickbe opened this issue Feb 1, 2018 · 10 comments · May be fixed by shaneomatz/opensupports#7
Assignees
Projects

Comments

@nickbe
Copy link

nickbe commented Feb 1, 2018

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
Copy link
Author

nickbe commented Feb 26, 2018

Are custom tags considered?

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

@nickbe
Copy link
Author

nickbe commented May 3, 2018

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
Copy link
Contributor

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

@ivandiazwm ivandiazwm added this to To review in Features May 4, 2018
@nickbe
Copy link
Author

nickbe commented May 5, 2018

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

@ivandiazwm ivandiazwm moved this from To review to Ready for dev in Features Oct 9, 2018
@ivandiazwm
Copy link
Contributor

@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:
    custom_tags1

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

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

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

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

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

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.

  1. 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
Copy link
Author

nickbe commented Oct 16, 2018

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
Copy link

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
Copy link
Author

nickbe commented Oct 18, 2018

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

@versavius
Copy link

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
Copy link
Author

nickbe commented Oct 23, 2018

Rules are too complicated to handle.

@guillegiu guillegiu moved this from Ready for dev to In progress in Features Nov 26, 2018
@guillegiu guillegiu moved this from In progress to Code Review in Features Mar 1, 2019
@ivandiazwm ivandiazwm moved this from Code Review to Merged in Features Mar 6, 2019
@ivandiazwm ivandiazwm moved this from Merged to Released in Features Mar 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Features
Released
Development

Successfully merging a pull request may close this issue.

4 participants