General Issue Statuses
Generally applies to all kinds of issues.
- "Dev Backlog": The issue is waiting to be scheduled to be worked on by the software development team. Tickets are moved from the "Dev Backlog" to "Scheduled for Dev" status depending on business prioritisation and development team capacity.
- "Needs BA Clarification": The agent who was busy with the issue is unsure on how to best address the issue and has asked one of our Business Analysts to investigate and assist them clarifying how best to proceed with the issue.
- "BA Clarifying": A business analyst has assigned the issue to themselves and investigating it further.
- "Needs QA Clarification": The software developer who was busy with the issue is unsure of some aspect of the issue and has asked for more information from the Quality Assurance agent who initially logged this issue.
- "QA Clarifying": The quality assurance agent has assigned the issue to themselves and investigating it further.
- "Scheduled for Dev": The issue has been scheduled to be completed in the current development "cycle". Cycles can be up to 6 weeks long.
- "Dev In Progress": A software developer has assigned the issue to themselves with the intention of completing it.
- "Waiting for Deploy": The developer who was busy with the issue has completed their work and the completed work is now waiting to be deployed to the Quality Assurance testing environment. Depending on the current phase of development team's cycle, it can be anywhere from a few hours to a few weeks until the work is deployed.
- "Ready for QA": A new version of the software has been built which includes work from this issue and has been deployed to the Quality Assurance environment. The issue is now ready and waiting to be tested by a quality assurance agent.
- "QA In Progress": A quality assurance agent has assigned the issue to themselves with the intent of validating the work done by the software developer who initially worked on the issue. If the the issue passes the quality assurance testing, it will be moved to the "Closed" status. If the issue fails the tests, then it will be moved back to the "Scheduled for Dev" status.
- "Closed": The issue has been closed. If the "resolution" of the ticket is "Done", this means that hopefully within the next few weeks, once the current testing version passes all quality assurance testing and is deployed to our live production environment, the work done for the issue will be visible and effective to yourself and other end users.
Other Issue Statuses
Generally applies only to "improvement" and "new feature" issues.
- "Product Backlog": The issue has been logged in the system, but it has not been analysed or assessed yet. During regular business prioritisation sessions, issues are moved from here to the "Analysis Scheduled" or "Dev Backlog" status depending on the complexity of completing the issue.
- "Analysis Scheduled": Issues in this status are in a queue to be analysed by a Business Analyst when they have capacity.
- "Analysis In Progress": A Business Analyst is now looking at the issue.
- "Analysis Complete": A Business Analyst has completed their analysis of the issue. They have also created a specification from which a software developer can work off to implement the changes to the system required by the issue. Depending on the business importance of the issue, it will be moved to either the "Dev Backlog" or "Ice Box" status.
- "Ice Box": This status is similar to the "Dev Backlog" status, except that it's typically only used for small / simple issues. Although it may not be specifically scheduled by the software development team, if they find they have some spare time, they may take issues out the "Ice Box" and work on them.
Issue Statuses Specific to Tasks
Tasks are types of issues that typically do not require actual software development, but may require a software developer's skills for completion, for example, manually correcting data in the database.
- "Scheduled for Dev": The issue is waiting for a developer to look into it. Depending on the priority and nature of the issue, it is usually in this status for no more than a few days.
- "In Progress": A developer has assigned the issue to themselves with the intent of completing the task.
- "Done": The work on the issue is completed.