Page Comparison

...

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.

Historical Issues

Issues imported from:
- 2019 Reveal Bug Tracker (mostly new user stories)
  - Issues for v1.0 were not imported
- Field Testing Feedback - Thailand
  - Bugs
    - Release Candidate bugs were not imported
    - Anything marked as fixed or NA was not imported
  - Forms
    - Anything marked as confirmed in notes column was not imported
  - User Stories
    - Anything marked as a duplicate was not imported
  - Translations
    - All imported
- Release 2 -3 Feature Groupings (Reveal 3.0 and Reveal vx sections)
Import files are here: https://drive.google.com/drive/folders/1vqLKGFhsq-Myg6VfmWGsQLDxwE9XmfZD

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, cleans up Summary and Description, and ensures all necessary info is included (e.g. steps to reproduce, task type, software version, OS, browser version etc). Discusses priority with CHAI and VW and modifies as necessary.
- Move to ‘Triage’
- Move to 'Won't Fix' if the issue is not relevant.
- Move to 'Backlog' if the issue is low priority and not something to focus on now.
Ona Development Manager monitors ‘Triage’ and ensures that issues are ready for dev.
- 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 necessary. Note the ownership of this task differs slightly for DSME user stories (see below).

Labels can be used for ad-hoc classifications that don't have pre-defined fields to measure them against. Please DO NOT create labels without consulting the Akros Product Manager.
The following labels exist currently
- Implementation/Location labels → for each country or location implementing, we have a label.
- Reopened → this label will be added to bugs or issues that are reopened after being completed
- DSME_User_Story → this label will be applied to user stories on the DSME road map
- Scoping planning tags
  - IRS_Plan
  - IRS_Features
  - FI_Plan

...

All user stories added to the roadmap will have a label "DSME_User_Story"
- User Stories will be considered complete when moved to the "Done" column. Akros will review the user story when in the "In Review" column and then reassign to VitalWave for a secondary review and move to the "Done" column.
DSME priorities will be translated as follows: