Page Comparison

...

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
Jira Legacy
server System JIRA
jqlQuery filter=10006
serverId 3420e60a-4e6f-3f80-8335-059c22bb40aa
(project = Reveal AND parent is EMPTY AND status = Done)
These can be used to populate dashboards

Import issues using the CSV import from the Jira Issues and FIlters page (https://smartregister.atlassian.net/issues) - Top right Horizontal Kebab menu icon.
Image Added
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
Image Added

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

...

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?)