- Get buy-in from the developers, product owners and client (CHAI)
- Add columns in the Reveal Board (Add ‘New’, ‘Triage’, “in Review’ , and 'Backlog') – 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 (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 necessaryInstead of labels, we will manually link if necessary after import. - 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 - We will not use Epic for releases
Task Types
There will be various issue types. The configuration of the different types is defined here:
Releases and Roadmap
Releases will be tracked by using Epics - these can be seen in a Gantt-like roadmap- Releases will be tracked through Jira release versions or label - tbd Craig Appl
Dashboards
Categories
Suggest using Labels for these
We have a custom field "Platform" that we will use for this field
- Android client
- Web UI
- Superset/Canopy
- Data Warehouse
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’