Sub-status does not make sense - the status is there to tell you where an issue is in your process. Imagine status as something that is completely clear as to where something is - "It's in progress", "We're working on it", "We're done". Sub-status is bad, because you could say "we're working on it, but not, at the same time".
But there's nothing to stop you having more status in your workflows, in order to represent your process properly.
@Nic Brough -Adaptavist-
Can you please explain me how does this workflow support in Jira Service Desk or how to design this workflow. Can we have action that to change status ike custom buttons or custom actions.
Thanks in advance
Throw away your "status" and "status to" columns as they're nonsense. Treat the "sub-status to" column as status, as this is what your process actually is.
Thank-You
It looks like you're new here. Sign in or register to get started.
