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

Jira admin UI doesn't allow choosing an archived project when changing the context of a custom field

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 8.20.0, 9.0.0, 9.4.0, 9.7.0, 9.12.0, 9.15.0, 9.16.0
    • Custom fields
    • None

      Issue Summary

      Projects that used a custom field might be archived, removing issues from the search index.
      Although not searchable, archived issues could still be accessed and having custom field values are important.

      A custom field might have been created with a global context and assigned to a project.
      This custom field was used within issues from this project, and the project may have been archived.

      If there's no plan using this custom field for other projects, the Jira administrator might want to change the custom field context, assigning it only to the archived project.

      However, when editing the custom field context configuration, the administrator won't be able to select an archived project.

      Steps to Reproduce

      1. Install a vanilla instance of Jira Software Data Center.
        • This was validated on versions 9.4, 9.12, 9.15 and 9.16.
      2. Create a Scrum software project with sample data.
        • In this example it's a scrum project with key SCRUM1.
      3. Create a custom field with global context and assign it to screens associated to project SCRUM1.
      4. Add values to this custom field on a couple of issues from SCRUM1 project.
      5. Archive the SCRUM1 project.
      6. Access one of the archived issues with custom field value and note the value for that CF is shown.
      7. Go to the custom field administration UI and choose configure context.
      8. Within Applicable contexts for scheme choose Edit Configuration.

      Expected Results

      The archived project SCRUM1 is part of the list within Available projects.

      Actual Results

      The archived project SCRUM1 is not part of the list within Available projects.

      This prevents removing this custom field from the global context by assigning it to the correct project.
      Creating a context on which SCRUM1 is not part of, without a global context, will prevent showing the CF value on the archived issue view.

      Workaround

      The Jira administrator may be able to use the custom field optimizer (CFO) to apply context that will consider archived projects.
      As detailed on JRASERVER-77748, although CFO doesn't show archived projects on scan results, applying the optimization will still consider them.

        1. screenshot-1.png
          screenshot-1.png
          166 kB
        2. screenshot-2.png
          screenshot-2.png
          160 kB
        3. screenshot-3.png
          screenshot-3.png
          235 kB
        4. screenshot-4.png
          screenshot-4.png
          239 kB
        5. screenshot-5.png
          screenshot-5.png
          326 kB
        6. screenshot-6.png
          screenshot-6.png
          370 kB

            Unassigned Unassigned
            tmasutti Thiago Masutti
            Votes:
            4 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: