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

Next challenges

Recent achievements


  • Give kudos
  • My kudos


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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 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,


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!



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

Hello Dan, 


Could you please share: 

- the screenshot of the Dependency edit panel;

 - the screenshot of the Team edit panel? 




Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Align

Best Practices in Jira Align

Hello Jira Align customers! In order to better serve you on your journey with Jira Align, the Community team has worked with the Jira Align team to curate the content in this collection to better s...

406 views 0 11
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you