You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have dependencies that are cross portoflio. I want to find them easily, rather than building a view of program to portfolio on requestor and depends on.
I get this warning sign in said dependency but for the life of me I can't find that error/alert in any table in Enterprise Insights.
Anyone know where it's hiding?
This is the warning:
Planning Increment conflict. This Dependency and its associated work item are assigned to different Planning Increments
I don't believe there is a table that caches Planning Increment Conflicts. The follow SQL will find those in error, although I didn't take into consideration Kanban Teams:
Dependency ID | Dependency Title | Dependency Type | Status | Work PI | Dependent Work PI | Planning Error MSG |
2892 | Clarity on security and privacy laws to be implemented in consumer goods industry | Epic External Dependency | Committed | R5 | R4 | Planning Increment conflict. This Dependency and its associated work item are assigned to different Planning Increments |
2893 | Server updates | Program Dependency | Committed | R5 | R4 | Planning Increment conflict. This Dependency and its associated work item are assigned to different Planning Increments |
SELECT D.[Dependency ID], D.[Dependency Title], D.[Dependency Type], D.[Status], PI_REQUEST.[PI Name] AS [Work PI], PI_PLANNED.[PI Name] AS [Dependent Work PI],
'Planning Increment conflict. This Dependency and its associated work item are assigned to different Planning Increments' AS [Planning Error MSG]
FROM [current_dw].[Dependency] AS D
LEFT OUTER JOIN [current_dw].[Program Increment] AS PI_REQUEST ON PI_REQUEST.[Program Increment ID] = D.[FK Program Increment ID]
LEFT OUTER JOIN [current_dw].[MAP Dependency to Story] AS D2S ON [FK Dependency ID] = D.[FK Epic ID]
LEFT OUTER JOIN [current_dw].[Story] AS DEPENDENT_STORY ON DEPENDENT_STORY.[Story ID] = D2S.[FK Story ID]
LEFT OUTER JOIN [current_dw].[Program Increment] AS PI_PLANNED ON PI_PLANNED.[Program Increment ID] = DEPENDENT_STORY.[FK Program Increment ID]
WHERE D.[Delivered Flag] = 'No'
AND D.[No Work Required Flag] = 'No'
AND D.[Commited Flag] = 'Yes'
AND PI_REQUEST.[PI Name] != PI_PLANNED.[PI Name]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.