Issue Tracking with Jira
Issues affecting the development of the Archive of Our Own software are tracked in Jira.
| Term | Description |
|---|---|
| Issue | A single issue affecting AO3: bug, new feature, task, improvement... |
| Status | Where that issue currently sits in the workflow |
| Workflow | The semi-automated process of getting an issue from its creation when it is first created in Jira to its closure when the code that addresses the issue is deployed to the live Archive |
| Status | Meaning | Triggered by | Who puts an issue into this state |
|---|---|---|---|
| To Do | The issue has been approved for work and is waiting for someone to work on it. | The creation of a new issue in Jira | AD&T |
| In Progress | The issue has been picked up by a developer and is being worked on. | The creation of a new branch for the issue or commits being made with its issue number, once the issue has an Assignee | Developer (automatic) |
| In Review | A pull request has been submitted for this issue and is waiting to be reviewed by developers and merged by AD&T. | The creation of a pull request mentioning this issue | Developer (automatic) |
| Merged | The pull request has been reviewed and merged into the Archive code base and is waiting for the Archive QA&T lead to confirm it has been deployed to our staging environment and is ready for testing. | The merging of the pull request mentioning this issue | AD&T (automatic) |
| QA | The code for the issue has been deployed to our staging environment and is waiting to be tested by the Archive QA&T team. | Manually | AD&T |
| Ready for Release | The code for the issue has been verified by the Archive QA&T team and it is waiting to be deployed to the live Archive. | Manually | QA&T |
| Broken on Test | The code for this issue has failed QA and needs additional action from the original developer. (If the developer is unavailable, a new coder may be assigned.) | Manually | QA&T |
| Broken on Test-SPR | A pull request has been submitted to address the issue that caused the code to fail QA. The pull request is waiting to be reviewed by other developers, merged by AD&T, and set back to QA by the QA&T lead. | The creation of a pull request mentioning the issue, if the issue currently has Broken on Test status | Developer (automatic) |
| Deployed | The code has been deployed and is now part of the Archive. This status also closes the issue with the resolution "Deployed to Beta." | Manually | AD&T |
For issues which do not involve development or don't require a release to the live Archive, or which are not valid to begin with, there are two extra statuses:
| Status | Meaning |
|---|---|
| Done | The task in the issue is complete but doesn't require reviewing, testing, and/or a code deploy to the Archive. |
| Closed | The issue does not need to be worked on and/or completed (e.g., because it is invalid or duplicates another issue). |