Page History

...

I'm starting to wonder if there are ways we can improve our JIRA workflow that would also simplify some of our JIRA review processes (and help us start to catch up on our JIRA backlog and "categorize" tickets better.

...

Old JIRA Workflow

Our current old JIRA Workflow / Statuses looks looked similar to this:

1. A Ticket is created -> "Received" Status
   • If this ticket is invalid / not a bug it can be immediately "Closed"
2. If it is valid, it moves into the "Open" status
3. Once "Open", the ticket remains in that status indefinitely. There are two possible "next steps".
   • Ticket can move to "In Progress" to denote that it's being worked on (this is actually rarely done)
   • Ticket can be marked as "Resolved" to denote that it is fixed.

In total there were are 5 statuses:

• Received - Ticket just came into the system
• Open (& Re-Opened) - Just denotes that this seems to be a valid ticket & that it is not yet "fixed".
• In Progress - Denotes someone is working on it (rarely used)
• Resolved - Denotes ticket is fixed/complete
• Closed - Also denotes ticket is fixed complete (we use it interchangeably with "Resolved")

The last two are very similar and we use them pretty much interchangeably to mean the ticket is "complete". Traditionally, in JIRA, many consider "resolved" tickets to be complete but may require extra verification (e.g. code review) before they move to the "closed" status.

...

New JIRA Workflow

I 'd propose thinking about reworking our JIRA statuses to better represent what the Ticket may be "waiting on" or requiring. So, I'd propose instead using the following statuses:

...

Here's a diagram of how a ticket would transition from one status to the next:

So, what are some of the possible benefits here?

...