Jira Process (Proposed)

• Get buy-in from the developers, product owners and client (CHAI)
• Add columns in the Reveal Board (Add ‘New’, ‘Triage’, “in Review’ ) – Workflow would be New ->Triage -> To Do -> In Progress -> in Review -> Done (Or back to triage or To Do)
  • Need LOE on each card

Adding a Task 

• Press 'C' and enter details for the Task
• The Summary should include all keywords for searching

Board

• Tasks can have an image which shows up on the card
• Filtering on the left  and grouping on the right are very powerful

Task Types 

Releases and Roadmap

• Releases will be tracked by using Epics - these can be seen in a Gantt-like roadmap

• Add a category
  • Android client
  • Web
  • Superset
• Define who is responsible for each stage
• Annie as Product Owner monitors  ‘New’, ensures that issues are not duplicates and cleans up Task Title, Description and ensure that all necessary info is included (steps to reproduce, task type, software version, OS, browser version etc). Move items to ‘Triage’
• Craig/Ona monitors ‘Triage’ and ensures that issues are ready for dev, schedules tasks
• Developers handle ‘To Do’ – move to In Review when dev complete
• Akros then review Issues and move to done if completed, or back to ‘Triage’ (with a red  ‘Reopened’ label) if necessary
• Any user should be able to add a bug  ‘New’
• Set up Release Version in Jira
• Import all bugs, form changes and new requirements into Jira using csv import
• Import all Roadmap user stories and New Feature Requests in Jira using csv import
• Add fields to issues (story points, software version, priority, others?)