What happens when a Jira issue moves forward with a required step missing?

[Simone Tognozzi]

Hi everyone,

 I'm trying to understand how Jira Cloud teams handle one specific problem.

Think of the most recent time an issue moved forward even though a required step had been missed. How did you discover it, what happened next, and what do you do today to prevent it?

Curious to hear how others handle this in practice.

[Suresh]

@Simone Tognozzi Please review this Bug and this and others listed here

[Alan Bruce]

Hello @Simone Tognozzi 

How did i discover it - Either I was on the ticket or the Agent/Reporter reported the issue

What happened next - investigate the issue/workflow

• Did this happen by design?
• Did this happen by accident?
  • user clicked the button but didn't mean to
  • Validation check not added/configured properly
• Frequency 
  • once a year? Ignore
  • once a month or more? offer Jira remediation option or User Training

What do you do today to prevent it? - Add it to my lessons learned and attempt to do a better job in the info gathering prior to implementing.

Each situation is a bit different. I have created transitions that move back to a previous status and put permissions on it  so that only Admin's or specific users are able to apply. Remember that you may need to undo some steps that were applied (updated/edited fields, comments, assignee, etc)

Hope that helps you out. 

Have a great day!

[Noah Unabia]

What has worked for us is something like this:

• Normative process for assignees to make corrections:
  1. Create a filter based on the process step that outputs the identified work item and any others that follow the same pattern.
  2. Ask assignees to follow up to make corrections
  3. Provide a dashboard to highlight and report corrective actions.
• Put a restrict transition rule in the workflow transition 
  
  • Options based on specific process are: {"Restrict based on the status of subtasks", "Restrict to when a field is a specific value", "Restrict transition using a Jira Expression" (Paid App required)}
  • Publish process guide and be prepared to explain to users why/when they can't find the restricted workflow transition.
• Put a validation rule in the workflow transition
  • Options based on specific process are: {"Restrict based on the status of subtasks", "Restrict to when a field is a specific value", "Restrict transition using a Jira Expression" (Paid App required)}
  • Publish process guide and be prepared to explain to users when they receive a failed transition error message.