Would it be possible to skip the use of resolution values on lifecycle statuses in just one issuetype within in a project containing multiple issuetypes, that do use them.
Currently i'm using resolution values when reaching a specific state. Which sometime leads to confusing end states of a ticket. e.g end state : "Complete" with resolution showing as "Rejected"
People raising the ticket complain that Completed/rejected makes them feel lost.. they don't know how to consider the state. Hence i want to step away from resolution values in favour of more straightforward lifecycle values... where 'completed' is a lifecycle state and 'rejected' would also be one.
hope my above explanation makes any sense :-)
Anyway, thanks in advance for sharing any knowledge !
@Bart Van den Bossche, welcome to the Community.
Yes you can you just need to create a different workflow for the issuetype and remove the screen from the transition done transition.
With that said it is always a good idea to have a resolution for all done items. you might want to consider using a post function on this one issuetype workflow and force the resolution to something meaningful but your call.
Hey Jack,
Glad to hear that there's a solution to my issue... but could you clarify what you mean with "Remove the screen from the transition done transtion"?
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
the purpose of the screen on a transition is to define what, if any, screen pops up when the transition is encoded.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hey Jack, all clear now. thanks for your swift reply on my question... appreciated !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.