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

Scope Change Report doesnt distinguish between items removed from original commitment and items added then removed

    XMLWordPrintable

Details

    • 1
    • Severity 3 - Minor
    • Stubborn Dragons - USH2, Stubborn Dragons - USH4, Stubborn Dragons - USH6, Stubborn Dragons - BBSH

    Description

      Issue Summary

      Scope Change Report doesn't distinguish between items removed from original commitment and items added then removed

      Steps to Reproduce

      1. Begin with active release (quarterly increment) with no scope changes
      2. View Scope Change Report and note list of items assigned before beginning
      3. Remove one or more item from scope
      4. Add a different item to scope
      5. Observe added item shows in report's "added" list. Removed item moves from "assigned before" list to "removed" list
      6. Remove the item that was added
      7. Observe no items appear in added list. Two removed items now show in "removed" list

      Expected Results

      For items appearing in removed list, ability to tell if that item was part of release before it began or if it was added after beginning

      Note that in Jira's report the items added then removed show with an asterisk. This allows the user to identify things that were added/removed. Items that show removed without an asterisk were part of original commitment.

      Actual Results

      For items appearing in removed list, not able to tell if that item was part of release before it began or if it was added after beginning

      Workaround

      Use a combination of reports or view work item histories

      Attachments

        Issue Links

          Activity

            People

              kforeman@atlassian.com Kyle Foreman
              tevans Tim Evans (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync