-
Bug
-
Resolution: Fixed
-
Medium
-
10.67
-
None
-
1
-
Severity 2 - Major
-
Dementors - SCORP3
Issue Summary
worktree team view (extra config & tier one) don't filter out by PI/release. Users expect that if the tier one is set to only filter associated work related to that team & the PI the report would do so. This isn't the case.
Steps to Reproduce
- Step 1 - Navigate to the work tree view
- Step 2 - Select a team & a PI/Release tier one
- Step 3 - Enable Team View via extra config
- Step 4 - Notice the work that appears in the view
Expected Results
PM ER: Team view should function like the Bottoms-up view with the additional filter of the team selection. So with that said, we should consider the tier 1 PI selection in this view.
Supports View:
If we allow users to select a PI/Release in the tier one we should show the expected data, if we have a limitation on showing the data or there is an internal reason why we have configured this report this way then we shouldn't allow users to filter by team in the tier on or PI/Release, and if we are going to allow and keep the logic the same we should at least show a message that would level set a users expectations of this view.
Actual Results
We show work tied to the team (via extra config) that's across all PIs not just the tier one selection
Workaround
No workaround at this time
- is related to
-
-
- Closed
-
- resolves
-
![[Atlassian Support System]](/images/icons/generic_link_16.png "[Atlassian Support System]")
ALIGNSP-2455
You do not have permission to view this issue
[JIRAALIGN-1331] [JIRAALIGN-1331] Work Tree Team View Doesn't Filter By PI
@Caz This defect moved to resolved state but i still see that the issue exist. That is number of stories seen in Work Tree view are different from the number of stories in the "Stories Grid"
Resolved in scope of https://jira.atlassian.com/browse/JIRAALIGN-1477
Hi 352999efc716 yes, we started investigation on this issue last sprint, but misunderstood the problem at hand. tsapra@atlassian.com has re-clarified the problem and we are re-investigating. Please stay tuned.
Hi Team,
I see that this issue has been moved into the next Sprint. Please let me know if you need us to perform a quick test on your environments to make sure this issue is resolved. Also, can you provide the current status on the ticket?
Hello cgottlieb@atlassian.com
On the customer's instance (ASML) I can still see this bug, in terms of number of stories reported on the work tree view and comparing that with the number of stories for a specific team for a specific PI on the story Grid view
ae25bd46c9bb can you please work with support (ddortch@atlassian.com ) to provide more details / screenshots? it could be a data configuration issue, but if not, we'll definitely reopen