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 6 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

Adding a Task 

  • Press 'C' and enter details for the Task
  • The Summary should include all keywords for searching and should be as short and succinct as possible. 
  • Extra detail to go in the Description field

Advanced Task Views and Searching

  • This can be done through the standard Jira Issue Search : https://smartregister.atlassian.net/issues
  • JQL queries can be saved eg 'Reveal, Not Done, Parent' for all stories without a parent Epic 

    type key summary assignee reporter priority status resolution created updated due
    Refresh

     (project = Reveal AND parent is EMPTY AND status = Done)
  • These can be used to populate dashboards

Importing Issues 

  • Import issues using the CSV import from the Jira Issues and FIlters page (https://smartregister.atlassian.net/issues) - Top right Horizontal Kebab menu icon.
  • Epic links cannot be imported - these will have to be added once the import is complete - suggest using LABELS to indicate epics if necessary
  • Use LABLES for other types of data that may need to be used later

Board

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

Standard View

 Grouped By Epic


Task Types 

Releases and Roadmap

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


Dashboards


Categories

Suggest using Labels for these

  • Android client
  • Web
  • Superset

Responsibilities

  • 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’
  • No labels