/
Key JIRA fields
Key JIRA fields
Key Feature fields
Field | Use |
---|---|
Summary | High level description of the feature |
Fix version/s | PO uses this field to assign a feature to a Release |
Description |
|
Potential workaround | PO/dev/SME will enter details as to an available workaround solution that an institution may use until feature is implemented. |
Epic link | Link each feature to an epic |
Key Labels |
|
Development Team | Assign to Development team to implement Feature |
Assignee | Assign to Product Owner responsible for Feature |
Linked Issue | Link all applicable issues to feature. Use the applicable link relationship value. |
Key non-feature/epic issue type fields
Field | Use |
---|---|
Summary | High level description of the non-feature/epic issue |
Description |
|
Release |
|
Hot Fix Approved by Cap Planning? | Enter cap planning group's decision |
Development Team | Assign to Development team to implement issue |
Affected institution | Select the institution(s) impacted by issue |
Fix Version/s | Used by developer(s) to assign issue to the applicable module release |
Linked Issues | Link all applicable issues to issue. Should only link one feature to an issue. |
Key labels |
|
/wiki/spaces/DQA/pages/2662181 | Root Cause Analysis (RCA) is a required field on all bugs. It is used to better understand the cause of bugs and where to focus our efforts for improvement. |
Potential workaround? | Proposed by Dennis to add this field. |