- 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)Jira Legacy server System JIRA jqlQuery filter=10006 serverId 3420e60a-4e6f-3f80-8335-059c22bb40aa - 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 typesThis document describes the process of issue and feature tracking and managing their scheduling into new releases of Reveal. This tracking will take place in Jira, through Atlassian platform that integrates with Confluence, where project scoping, note-taking, and general documentation is stored.
Issue Types
There are various issue types enabled in the Reveal Jira configuration. 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
...
Epic (User Story of Feature): Epics will be used to track user stories or features, which will often represent a collection of development tasks. Epics will be entered by implementation users, the product manager, or the development manager. The development manager will work to split Epics into individual development tasks. Other issue types can be linked to Epics if they must be addressed to complete the work for that particular epic.
Bug: Bugs will be entered against current Reveal versions by any user who discovers said bugs.
Form Change: Form changes will often be country specific requests to modify the forms that are attached to tasks in Reveal.
Question: The question field may be used by developers or implementers to resolve a question related to scoping or intended functionality.
Task: Tasks will represent individual development tasks.
Adding an Issue
- Press 'C' and enter details for the issue. Note the required fields differ slightly depending on which type of issue is selected.
- Fields include:
- Epic Name used to name the feature or user story.
- Summary to include all keywords for searching and should be as short and succinct as possible.
- Platform field used to capture which Reveal platforms are most relevant for this issue.
- Device/Hardware entered if a bug or issue is experienced on a particular hardware type.
- Operating System entered if a bug or issue is experienced on a particular OS.
- Priority as perceived at the time of entering the issue
- Extra detail to go in the Description field. Screenshots can be pasted here or uploaded as attachments (former preferred).
- Affects version to capture the release version that this bug or issue is related to.
- Implementation/Location captures which locations or implementations this issue or bug is relevant to. This is a label field, meaning the user can create different values on-the-fly.
Triaging Issues
The issue workflow will move issues through set of statuses which can be visualized on the Kanban board.
- Any user should be able to add a bug or feature to ‘New’. Akros Product Manager monitors ‘New’, ensures that issues are not duplicates and , cleans up Task TitleSummary and Description, Description and ensure that ensures all necessary info is included (e.g. steps to reproduce, task type, software version, OS, browser version etc). Move items to ‘Triage’Craig/Ona Discusses priority with CHAI and VW and modifies as necessary.
- Move to ‘Triage’
- Move to 'Won't Fix' if the issue is not relevant.
- Ona Development Manager 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.
- Moves to 'Ready for Dev'
- 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 necessaryAny user should be able to add a bug ‘New’.
Releases
- Releases will be tracked through Jira release versions.
- Users can track issue progress against versions.
