Issues in projects with hidden fix version field are not imported into Portfolio plans

XMLWordPrintable

    • 8.2
    • 2
    • Severity 2 - Major
    • 14
    • Hide
      Atlassian Update – 19 October 2023

      Dear Customers,

      I am pleased to announce that a fix for this issue will be a part of the Jira 9.13.0 release.

      Hiding a field removes it completely from the Lucene index, and Advanced Roadmaps used to always append a subquery related to 'Fix Version/s' when loading issues in the Scope view of a Plan - even when there were no release exclusion rules setup in the given Plan.

      Our fix involved adjusting the filtering logic so that if there are no release exclusion rules in a Plan, the subquery will not be appended, so that all issues can still match and thus be displayed in the Scope view.

      Please note that if the 'Fix Version/s' field is hidden and the Plan uses release exclusion, not displaying the affected issues is expected behavior. This is not a bug but a misconfiguration. The 'Fix Version/s' field should not be hidden in this scenario. Instead, we recommend un-hiding it, removing it from screens, and triggering a re-index.

      Thank you for your patience while we worked to resolve this bug.

      Best regards,
      Daniel Rauf
      Software Engineer

      Show
      Atlassian Update – 19 October 2023 Dear Customers, I am pleased to announce that a fix for this issue will be a part of the Jira 9.13.0 release. Hiding a field removes it completely from the Lucene index, and Advanced Roadmaps used to always append a subquery related to 'Fix Version/s' when loading issues in the Scope view of a Plan - even when there were no release exclusion rules setup in the given Plan. Our fix involved adjusting the filtering logic so that if there are no release exclusion rules in a Plan, the subquery will not be appended, so that all issues can still match and thus be displayed in the Scope view. Please note that if the 'Fix Version/s' field is hidden and the Plan uses release exclusion, not displaying the affected issues is expected behavior . This is not a bug but a misconfiguration. The 'Fix Version/s' field should not be hidden in this scenario. Instead, we recommend un-hiding it, removing it from screens, and triggering a re-index. Thank you for your patience while we worked to resolve this bug. Best regards, Daniel Rauf Software Engineer

      Issue Summary

      When setting up an issue source that contains projects with hidden Fix Version/s
      field, no issues are shown in the Scope view.

      This is reproducible on Data Center: (yes)

      Steps to Reproduce

      1. Use a software project with the field Fix Version/s enabled in the create/view issue screen.
      2. Create a plan using the above Project as Issues Source
      3. Navigate to ⚙ > Issues > Field configurations
        • Search for Fix Version/s and mark as Hide
      4. Perform a Re-index (Project re-index can be done and may be required on multiple projects, used in Issues Sources)
      5. Plan does not show any issues

      Expected Results

      • Issues should be displayed in the Scope view of the Plan

      Actual Results

      • Issues are not displayed in the Scope view of the Plan

      Workaround

      • The only available workaround is to make Fix Version/s visible such that Issues are displayed in the Scope view of the Plan
        A reindex is suggested after making Field-related changes.

      Tested with Jira Software v9.4.6 and Advanced Roadmaps for Jira 9.4.6 

        1. screenshot-1.png
          screenshot-1.png
          304 kB
        2. screenshot-2.png
          screenshot-2.png
          83 kB
        3. Screen Shot 2016-02-19 at 5.46.26 AM.png
          Screen Shot 2016-02-19 at 5.46.26 AM.png
          22 kB
        4. screenshot-3.png
          screenshot-3.png
          53 kB

            Assignee:
            Daniel Rauf
            Reporter:
            Martin Sturm (Inactive)
            Votes:
            38 Vote for this issue
            Watchers:
            58 Start watching this issue

              Created:
              Updated:
              Resolved: