Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-77531

When updating the context for a custom field(rank), after a jira restart, the changes revert back and global context is applied for the field

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • Custom fields
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      Issue Summary

      This is reproducible on Data Center: (yes) / (no) - Yes

      Steps to Reproduce

      1. Unlock the Rank field using the following query - xxxx -> id of the custom field
        UPDATE managedconfigurationitem set managed='false' where item_id in ('xxxx');
      1. The field configuration is then changed to remove all projects where the Ranking is not used. Changing from Global (projects) / Global (Issue types) to Project A, B / Global (Issue types).
      2. Lock the rank field again by using the following query  - xxxx ->id of the custom field
        UPDATE managedconfigurationitem set managed='true' where item_id in ('xxxx');
      1. Restart JIRA. 

      Expected Results

      The context change made in the field configuration should persist.

      Actual Results

      The field configuration reverts back to the global context(all projects)

      Workaround

      Required, if there is no workaround please state:

      The only workaround is to not restart Jira but it isn't viable. 

      Attachments

        Activity

          People

            Unassigned Unassigned
            2a58c9773847 Vijay Krishnan Subramanian
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: