-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
10.77
-
1
-
Severity 3 - Minor
-
Stubborn Dragons - USH2, Stubborn Dragons - USH4, Stubborn Dragons - USH6, Stubborn Dragons - BBSH
Issue Summary
Scope Change Report doesn't distinguish between items removed from original commitment and items added then removed
Steps to Reproduce
- Begin with active release (quarterly increment) with no scope changes
- View Scope Change Report and note list of items assigned before beginning
- Remove one or more item from scope
- Add a different item to scope
- Observe added item shows in report's "added" list. Removed item moves from "assigned before" list to "removed" list
- Remove the item that was added
- 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
- duplicates
-
JIRAALIGN-1231 [JIRAALIGN-1231] Scope Change: Removed Features doesn't appear in the report
- Closed