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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Would Jira Kanban project pose any challenge in Jira Align with respect to dependency mgmt?


We have Jira and Jira Align integrated. We are changing a Scrum Project to a Kanban project in Jira (Team project). Would it pose any challenge with respect to dependency management since it would not have target Sprint to plan the dependency completion (Needed By - Sprint & Committed By - Sprint)

Are there any other place(s) Kanban team project would pose challenge?

1 answer

1 accepted

3 votes
Answer accepted
Mark Cruth
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 18, 2021

@Vinay Sharma - in regards to dependency management, when you change a team from a "Agile Team" in Jira Align to a "Kanban Team" the Need By and Committed By dates will change to a date picker (vs selecting an anchor sprint). Here's what happens based on which team is changed...

  • Requesting team is changed to a Kanban Team, the "Need By" date will change to the last day in the selected anchor sprint (eg. Sprint 27 changes to 6/30/2021)
  • Requested team is changed to a Kanban Team, the "Committed By" date will be cleared out, but the dependency will remain committed if previously committed (this is a weird user experience, by can be easily remedied by updating the issue)

In regards to other implications of Kanban Team, take a look at this page:

I hope this helps!


Thanks Mark! It helps!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events