Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-1231

[JIRAALIGN-1231] Scope Change: Removed Features doesn't appear in the report

XMLWordPrintable

    • 5
    • Severity 3 - Minor
    • Stubborn Dragons - RHP8, Stubborn Dragons - USH3, Stubborn Dragons - USH6, Stubborn Dragons - BBSH

      Issue Summary

      Scope Change: Removed Features doesn't appear in the report

      Steps to Reproduce

      1. Login. 
      2. Add Feature to any PI. 
      3. Assign Feature to different PI. 
      4. Go to Scope change Report. 
      5. Check if Feature appears in the respective section. 

      Expected Results

      If a feature was added before the PI started, then removed after the PI started, it should appear in the. removed section with no lozenge. 

      If a feature was added to PI after the start of the PI, then removed, it should appear in the "Removed" section. For these features that were not committed to PI before the start, show a blue lozenge to the right of their name that says  "NOT COMMITTED"

      Actual Results

      The feature doesn't appear in Scope Change Report>Features removed from the Release

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

        1. In progress.png
          In progress.png
          2 kB
        2. Not_commited_lozenge.png
          Not_commited_lozenge.png
          46 kB

          Form Name

            [JIRAALIGN-1231] [JIRAALIGN-1231] Scope Change: Removed Features doesn't appear in the report

            Caz (Inactive) added a comment -

            Closed in 10.83. 

            If a feature was added before the PI started, then removed after the PI started, it will appear in the removed section with no lozenge. 

            If a feature was added to PI after the start of the PI, then removed, it will appear in the "Removed" section with a blue lozenge to the right of their name that says  "NOT COMMITTED" (in reference to the fact that it was not assigned to the PI before starting the PI). 

            Caz (Inactive) added a comment - Closed in 10.83.  If a feature was added before the PI started, then removed after the PI started, it will appear in the removed section with no lozenge.  If a feature was added to PI after the start of the PI, then removed, it will appear in the "Removed" section with a blue lozenge to the right of their name that says  "NOT COMMITTED" (in reference to the fact that it was not assigned to the PI before starting the PI). 

            Deleted Account (Inactive) added a comment -

            Seeing this problem again in 10.76. Reported here: https://getsupport.atlassian.com/servicedesk/customer/portal/51/ALIGNSP-5598

             

            Deleted Account (Inactive) added a comment - Seeing this problem again in 10.76. Reported here: https://getsupport.atlassian.com/servicedesk/customer/portal/51/ALIGNSP-5598  

            Kyle Foreman added a comment -

            This issue was fixed in the Jira Align 10.68 release. Now, features removed the release show in the Scope Change Report.

            Kyle Foreman added a comment - This issue was fixed in the Jira Align 10.68 release. Now, features removed the release show in the Scope Change Report.

              cgottlieb@atlassian.com Caz (Inactive)
              rpetrunyak@atlassian.com Roman Petrunyak (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: