-
Bug
-
Resolution: Fixed
-
High
-
8.2.0, 8.2.1, 8.2.3, 8.3.0, 8.2.4
-
None
-
8.02
-
1
-
Severity 2 - Major
-
7
-
This bug is directly related to JRASERVER-69388, but had lower impact. JRASERVER-69388 was affecting all plugins creating custom fields in the @PluginEnabledEvent. This bug is related to plugins creating custom fields (or any entities) in a com.atlassian.upgrade.spi.UpgradeTask. This is the case for JSW Development custom field.
Issue Summary
Jira locked Development field name shows i18n key as it is. Other entities can be affected:
- custom field name and description (table: customfield)
- issue type name and description (table: issuetype)
- field configuration scheme name (table: fieldconfigscheme)
- field configuration name (table: fieldconfiguration)
- field layout item description (table: fieldlayoutitem)
- project role name and description (table: projectrole)
- search request query (table: searchrequest)
Environment
- Jira 8.2.0
- Not reproduced 7.13.0, 8.1.0
Steps to Reproduce
- Build Jira with installer
- Move Jira Administration > Issues > Custom fields
- Check locked "Development" field
Expected Results
Field name show "Development".
Field description show "Development Summary Field for Jira Software use only".
Actual Results
Field name show "devstatus.customfield.development.name".
Field description show "devstatus.customfield.development.desc".
- is related to
-
-
- Closed
-