When editing an issue during transition, (not available) may be appended to some custom field types.

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問


プラットフォームについて: Server と Data Center のみ - この記事は、サーバーおよびデータセンター プラットフォームのアトラシアン製品にのみ適用されます。

要約

During a transition, Changing a Parent value in the following custom field types to "none" and saving will result in having to save the transition a second time and will display a duplicated value with (not available) appended to it. 

  • Select
  • Multi select,
  • Cascading Select,
  • Radio
  • チェックボックス

参照先: 

Steps to Reproduce:

  1. Create a Cascading Select in the custom field configuration for a Project.
  2. Mark it as Required (Administration --> Issues --> Field Configurations) 
  3. Create a transition that uses a screen that has the Cascading Select.
  4. Create an issue and select a parent and child issue. Save it.
  5. In the Issue window, click on the Transition to edit the values.
  6. Under Parent select option, change to (none).
  7. Save the edit.
  8. Note that the save doesn't get written yet.

Observations:

  1. Selecting (none) results in a message saying the field is required.
  2. A duplicate option shows up with (not available) appended. (see attached screenshot)
  3. You can save after this, even without making changes. The issue will commit the last "known good" selection.
  4. Note that the previously used value is defaulted due to code changes in 8.8.0 to prevent data loss (likely the result of )

環境

8.13.9

原因

This behavior was introduced during a bug-fix attempting to prevent data loss. https://jira.atlassian.com/browse/JRASERVER-62455 has more details.

Background:

If an issue has a selected option saved in the database, that option will always be present in the edit form - even if the configuration of the field has been changed. The options not present in the configuration will have a "(not available)" suffix in their names. This prevents accidental data loss and allows users to edit parts of the issue without forcing them to change the historical values if custom field configuration changes.


Please follow this Engineering Ticket for any developments: https://jira.atlassian.com/browse/JRASERVER-72846

ソリューション


(lightbulb) Workaround to avoid end-user confusion:

1. Create a copy of <atlassian install directory>/atlassian-jira/WEB-INF/classes/com/atlassian/jira/web/action/JiraWebActionSupport.properties for backup purposes.

2. Change the line:

customfield.not.available.in.scheme={0} (not available)

to

customfield.not.available.in.scheme={0}

3. Restart Jira


 This will not prevent a second entry from showing in the Transition, but it will remove the (not available) tag from it and hopefully avoid end-user confusion. You will still have to save the transition twice.

quote

最終更新日 2021 年 11 月 20 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.