Key JIRA fields

Key Feature fields

Field	Use

Field	Use
Summary	High level description of the feature
Fix version/s	PO uses this field to assign a feature to a Release
Description	Use UXPROD features template Review Getting Started for Product Owners#UXPRODFeatures
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	Review Getting Started for Product Owners#UXPRODFeatures Review Getting Started for Product Owners#SplittingUXPRODFeatures delegate _candidate for UI only features
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

Field	Use
Summary	High level description of the non-feature/epic issue
Description	Use applicable issue template Review Getting Started for Product Owners#DevelopmentBacklogs If an issue type = Bug then provide Environment to reproduce (if all environments, please indicate) Steps to reproduce Outcomes - Expected and Actual outcomes Screenshots or Screencasts Attach any documentation/credentials that will reproduce issue Link to original requirement (if possible)
Release	To help track development, assign a release value for an issue. Starting with the Lotus release, the dropdown will display <<Release Name>> <<Release #> <<Release Year>> When to use <<Release Name>> <<Release #> <<Release Year>> Bugfix Only apply to work that will generate change in code, deploy to bugfest environment, and be included in module release. If you have non-code work then apply the next release value non-code is defined as not a release blocker and it is not required to be deployed to BugFest or be present in the release, when delivered. When to use <<Release Name>> <<Release #> <<Release Year>> Hotfix A candidate for hotfix release Only apply to work that will generate change in code, deploy to bugfest environment, and be included in module 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	ui-only (does not require backend dev) delegate_candidate for ui only work that any team can be assigned [a11y] for accessibility issue bugfest_<<release number>>.<<release year>> assign to any issue created as a result of bugfest support Support SIG assigns to a production issue
RCA Group	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.