Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

  • 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
  • Add Task types – we should have Bugs and Stories at least (we could use labels for this but I think Type is better)
    • DSME User stories are Epics
    • Stories are below epics
    • Bugs
  • We need to create releases
    • Add Release Version to tickets
  • 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?)
  • No labels