Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-60803

Updating custom field description does not update field description on field configuration

XMLWordPrintable

      NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.

      Summary

      When updating a custom fields description, it seems logical that this description would update every place that custom field is used. This is not the case.

      Environment

      Cloud

      Steps to Reproduce

      1. Create a new custom field
      2. Add a description to the field
      3. Add this custom field to a field configuration
      4. Update the description of the custom field on the custom fields page
      5. Look at the custom field on the field configuration

      Expected Results

      The description of the custom field on the field configuration should be updated to match the changes made on the custom fields page

      Actual Results

      The custom field description on the field configuration retains the original description if there is one.

      Workaround

      The user will need to update the description of the respective field on the field configuration the field is being used on

            [JRACLOUD-60803] Updating custom field description does not update field description on field configuration

            Heitor T (Inactive) added a comment -

            Hello there,

            Thank you for your feedback in this report.

            We've confirmed that this is actually expected behavior. Giving you more context, the description of the custom fields visible in the custom fields is intended to describe the purpose of this field in Jira, while the description visible in the field configuration is intended to indicate the purpose of the field in the project level, and this is the reason why the description set in the field configuration is displayed in the issue creation form.

            We agree the way how it works currently can be misleading, and we will work on a solution to make the difference between the description fields clearer.

            Apologies for the inconvenience.

            Kind regards,

            Atlassian Cloud Support

            Heitor T (Inactive) added a comment - Hello there, Thank you for your feedback in this report. We've confirmed that this is actually expected behavior. Giving you more context, the description of the custom fields visible in the custom fields is intended to describe the purpose of this field in Jira, while the description visible in the field configuration is intended to indicate the purpose of the field in the project level, and this is the reason why the description set in the field configuration is displayed in the issue creation form. We agree the way how it works currently can be misleading, and we will work on a solution to make the difference between the description fields clearer. Apologies for the inconvenience. Kind regards, Atlassian Cloud Support

            Robert Anthony added a comment -

            I'm pretty surprised that this bug is still occurring in the Cloud environment more than 3 years after it was initially reported. Obviously it's not occurring in every cloud instance or it would have been fixed by now. Is there some specific instance config option that's causing it to occur so that we may rectify? The workaround is rather tedious and as we scale will become more of a hassle to perform. Any additional information is appreciated. 

            Robert Anthony added a comment - I'm pretty surprised that this bug is still occurring in the Cloud environment more than 3 years after it was initially reported. Obviously it's not occurring in every cloud instance or it would have been fixed by now. Is there some specific instance config option that's causing it to occur so that we may rectify? The workaround is rather tedious and as we scale will become more of a hassle to perform. Any additional information is appreciated. 

            Nilesh Patel added a comment -

            Any chance this issue will be resolved?
            If one has 20 projects in Jira then performing the workaround in 20 project would take at least one day to correct and test the change in each project.
            When can we expect this to be resolved? There appears to be no one assigned to this ticket does that mean it will never be resolved? (Original ticket created on April 28, 2016.

            Nilesh Patel added a comment - Any chance this issue will be resolved? If one has 20 projects in Jira then performing the workaround in 20 project would take at least one day to correct and test the change in each project. When can we expect this to be resolved? There appears to be no one assigned to this ticket does that mean it will never be resolved? (Original ticket created on April 28, 2016.

            Brad as Paul added a comment -

            The workaround of accessing field configurations through project settings works.

            Project _____ Settings > Fields > Edit Pencil > Find Field and "Edit" > enter description

             

            I hope this is fixed soon to eliminate the need for this workaround.

            Brad as Paul added a comment - The workaround of accessing field configurations through project settings works. Project _____ Settings > Fields > Edit Pencil > Find Field and "Edit" > enter description   I hope this is fixed soon to eliminate the need for this workaround.

              Unassigned Unassigned
              mlavender mlavender (Inactive)
              Affected customers:
              11 This affects my team
              Watchers:
              26 Start watching this issue

                Created:
                Updated:
                Resolved: