...
- Any user should be able to add a bug or feature to ‘New’. Akros Product Manager monitors ‘New’, ensures that issues are not duplicates, cleans up Summary and Description, and ensures all necessary info is included (e.g. steps to reproduce, task type, software version, OS, browser version etc). Discusses priority with CHAI and VW and modifies as necessary.
- Move to ‘Triage’
- Move to ‘Scoping Needed’
- Move to 'Won't Fix' if the issue is not relevant.
- Move to 'Backlog' if the issue is low priority and not something to focus on now.
- If duplicate and any issues type but Epic, link to duplicate issue, and mark newer issue as 'Won't Fix'
- If duplicate and issue type of Epic, list duplicate Epic number in title and comments and mark newer issue as 'Wont' Fix'.
- Add appropriate labels.
- Ona Development Manager monitors ‘Triage’ and ensures that issues are ready for dev or may need scoping.
- Moves to 'Ready for Dev' or 'Scoping Needed'
- Adds 'Fix Version'
- Akros Product Manager monitors 'Scoping Needed', creates scoping documentation, assigns owner of feature scoping on the issue. When scoping is complete:
- Moves to 'Triage'
- Ona Development Manager and developers monitor ‘Ready for Dev’ and schedules.
- Moves to 'In Progress'
- Developers handle ‘In Progress’
- Move to 'In Review' when dev complete and version with the fix or feature is released.
- Akros to monitor 'In Review,' and move to 'Done' when testing passes, or back to ‘Triage’ (with a red ‘Reopened’ label) if necessary. Note the ownership of this task differs slightly for DSME user stories (see below).
As a product team, we will aim to look at the new and triage columns on a daily basis, working to move items from new into triage within 2-3 days.
Scoping and linking between Confluence and Jira
...