• Type: Bug
• Resolution: Fixed
• Priority: High (View bug fix roadmap)
• Fix Version/s: 8.3.1
• Affects Version/s: 8.2.0, 8.2.1, 8.2.3, 8.3.0, 8.2.4
• Component/s: UPM (Universal Plugin Manager)
• Labels:

  None

1. Screenshot 2019-07-23 at 10.56.15.png

   23/Jul/2019 2:36 PM

   361 kB

   Maciej Swinarski

2. Screenshot 2019-07-23 at 10.56.15.png

   23/Jul/2019 2:35 PM

   361 kB

   Maciej Swinarski

3. Screenshot 2019-07-23 at 16.06.39.png

   23/Jul/2019 2:37 PM

   364 kB

   Maciej Swinarski

[JSWSERVER-20164] devstatus.customfield.development keys shown instead of name and description

Przemyslaw Czuj (Inactive) made changes - 01/Aug/2019 2:15 PM

Resolution		New: Fixed [ 1 ]
Status	Original: In Progress [ 3 ]	New: Closed [ 6 ]

SET Analytics Bot made changes - 27/Jul/2019 1:01 AM

UIS

Original: 5

New: 7

SET Analytics Bot made changes - 25/Jul/2019 12:40 AM

UIS

New: 5

Bugfix Automation Bot made changes - 24/Jul/2019 6:01 AM

Support reference count

New: 1

Maciej Swinarski (Inactive) made changes - 23/Jul/2019 2:37 PM

Attachment		New: Screenshot 2019-07-23 at 16.06.39.png [ 359884 ]
Description	Original: {panel} 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. {panel} h3. 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) h3. Environment  - Jira 8.2.0  - Not reproduced 7.13.0, 8.1.0 h3. Steps to Reproduce  # Build Jira with installer  # Move _Jira Administration > Issues > Custom fields_  # Check locked "Development" field h3. Expected Results Field name show "Development". Field description show "Development Summary Field for Jira Software use only".  !Screenshot 2019-07-23 at 10.56.15.png|thumbnail! h3. Actual Results Field name show "devstatus.customfield.development.name". Field description show "devstatus.customfield.development.desc". !Screenshot 2019-07-23 at 10.56.15.png|thumbnail!	New: {panel} 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. {panel} h3. 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) h3. Environment  - Jira 8.2.0  - Not reproduced 7.13.0, 8.1.0 h3. Steps to Reproduce  # Build Jira with installer  # Move _Jira Administration > Issues > Custom fields_  # Check locked "Development" field h3. Expected Results Field name show "Development". Field description show "Development Summary Field for Jira Software use only".  !Screenshot 2019-07-23 at 16.06.39.png|thumbnail! h3. Actual Results Field name show "devstatus.customfield.development.name". Field description show "devstatus.customfield.development.desc". !Screenshot 2019-07-23 at 10.56.15.png|thumbnail!

Maciej Swinarski (Inactive) made changes - 23/Jul/2019 2:36 PM

Description

Original: {panel} 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. {panel} h3. 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) h3. Environment  - Jira 8.2.0  - Not reproduced 7.13.0, 8.1.0 h3. Steps to Reproduce  # Build Jira with installer  # Move _Jira Administration > Issues > Custom fields_  # Check locked "Development" field h3. Expected Results Field name show "Development".  Field description show "Development Summary Field for Jira Software use only". h3. Actual Results Field name show "devstatus.customfield.development.name".  Field description show "devstatus.customfield.development.desc".

New: {panel} 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. {panel} h3. 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) h3. Environment  - Jira 8.2.0  - Not reproduced 7.13.0, 8.1.0 h3. Steps to Reproduce  # Build Jira with installer  # Move _Jira Administration > Issues > Custom fields_  # Check locked "Development" field h3. Expected Results Field name show "Development". Field description show "Development Summary Field for Jira Software use only".  !Screenshot 2019-07-23 at 10.56.15.png|thumbnail! h3. Actual Results Field name show "devstatus.customfield.development.name". Field description show "devstatus.customfield.development.desc". !Screenshot 2019-07-23 at 10.56.15.png|thumbnail!

Maciej Swinarski (Inactive) made changes - 23/Jul/2019 2:36 PM

Attachment

New: Screenshot 2019-07-23 at 10.56.15.png [ 359883 ]

Maciej Swinarski (Inactive) made changes - 23/Jul/2019 2:35 PM

Attachment

New: Screenshot 2019-07-23 at 10.56.15.png [ 359882 ]

Maciej Swinarski (Inactive) made changes - 23/Jul/2019 2:30 PM

Link

New: This issue is related to JRASERVER-69388 [ JRASERVER-69388 ]

Bugfix Automation Bot made changes - 23/Jul/2019 2:30 PM

Introduced in Version

New: 8.02

Load more older history items