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 !