-
Bug
-
Resolution: Fixed
-
High
-
10.71, 10.95, 10.96, 10.97.3, 10.98.3, 10.99.3, 10.100.3, 10.102.0, 10.101.3, 10.103.0, 10.104.0, 10.103.1, 10.103.2, 10.105.0, 10.106.0
-
6
-
Severity 2 - Major
-
Sticky Bandits - WT2
-
No
Issue Summary
Use Case: When a team to team dependency or program to program dependency is requested outside of the target completion, this is causing the feature and dependency to be red (which is expected). However, when the team commits to it within the target completion the dependency and feature are still showing red which should not be the case since they have agreed to get the work done within the target completion.
Steps to Reproduce
- Step 1 - (Meet all requirements for workitem to show on the program board) Create a dependency that request for the work to be done outside the target completion date.
- Step 2 - Then commit to the dependency before the end of the target completion date
- Step 3 - Run the program board view to compare and see if there are planning issues.
Expected Results
If the team commits to the dependency within the target completion even though the request was outside the target we shouldn't flag a planning issue.
Actual Results
There is a planning issue shown on both the dependency and the feature turning them red
Workaround
No workaround
- has a derivative of
-
JIRAALIGN-4122 Reviewing a Feature with committed dependencies in a Team Swimlane shows a red planning issue due to the dependencies being worked by other teams
- Closed
-
JIRAALIGN-4123 A feature dependency with an original Committed By date after target remains with a red planning status after Committed By is changed to earlier than target
- Closed
- is related to
-
ALIGNSP-6740 Loading...
-
ALIGNSP-13888 Loading...
- resolves
-
ALIGNSP-9356 Loading...
-
ALIGNSP-12185 Loading...
-
ALIGNSP-12315 Loading...