Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,467,605
Community Members
 
Community Events
177
Community Groups

Kanban teams unable to commit to Dependencies

I'm seeing strange behaviors with dependencies and Kanban teams. When a Kanban team attempts to provide a commitment date, instead of having a box to provide the date, there is simply an "i" for more information. When you hover over the "i" it tells you "The Depends on Team has no Sprints that fall within the associated Program Increment date range (XXX-PI_NAME-XXX). Click here to set it up! Note: This Team requires at least one Agile Team to be associated to it as well."

It appears that since the Kanban team have no sprints that they can't provide a commitment date. Is that correct? Can anyone provide guidance as to what we need to do to allow Kanban teams to commit to dependencies?  Thanks!

3 answers

Hello Dan, 

 

Could you please share: 

- the screenshot of the Dependency edit panel;

 - the screenshot of the Team edit panel? 

 

Thanks,

Roman

0 votes

Howdy!

 

It may be that the team is not actually configured to be a Kanban team in Jira Align? because, if set up properly, the team can be shown on the program board and can commit to dependencies using a calendar view

Screen Shot 2020-09-18 at 9.05.08 AM.pngScreen Shot 2020-09-18 at 9.05.55 AM.pngScreen Shot 2020-09-18 at 9.05.34 AM.png

Hi Jesse - Great idea - I can see how that could mess things up if it was an Kanban team marked as an Agile team with missing sprints. Unfortunately, this doesn't seem to be my problem. I've confirmed that the team is set accordingly as a "Kanban Team (Labs)" in Align.  Thanks for the great screenshots with your idea.

Like Jesse Pearlman likes this

@Jesse Pearlman  Thank you.  Your suggestion to check the team configuration solved this exact problem for me. 

Like Jesse Pearlman likes this

Hello @Dan Sigrist

 

Thanks for your question. 

I have reviewed this functionality and was able to trigger the message you see in one case. It appears when you have a Dependency from the Agile Team to Program Team. And Program team has no Program Increment associated. 

So, could you please double-check that Depends on Team is a Kanban team, not a Program Team? 

 

Best Regards,

Roman

Hi Roman - Thank you for providing your above response. You were pretty close to getting the cause of the issue. On a call with @Darryl Dortch on Friday (about a different topic), I mentioned this issue and he suggested that we look into Programs that don't have Agile teams or Sprints assigned to them. We were attempting to create team to program dependencies but the problem was that the program didn't have specific Agile Teams or sprints associated. Even though there are people assigned to roles within the Program and PIs assigned to the Portfolios, Jira Align won't let us commit to a date until there is an Agile Team and a Sprint assigned (by Atlassian design). Not exactly the answer I was hoping for, but glad I have an answer now and was able to demonstrate a solution for the issue.  Thanks to you all for your help!

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events