-
Bug
-
Resolution: Fixed
-
Highest
-
10.65
-
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
- Login.
- Add Feature to any PI.
- Assign Feature to different PI.
- Go to Scope change Report.
- 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
- is duplicated by
-
JIRAALIGN-2013 Scope Change Report doesnt distinguish between items removed from original commitment and items added then removed
- Closed
- resolves
-
ALIGNSP-1451 Loading...
-
ALIGNSP-5598 Loading...
-
ALIGNSP-5622 Loading...