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!


“Work Item Links” functionality


Is it advisable to enable “Work Item Links” functionality in Jira Align considering the below pros and cons? Also, please share alternate solutions if there are any?


  • Allows teams to identify story dependencies and sequence stories
  • Easy to turn on/off with no negative consequences


  • Users may lose their collaborative nature by focusing on predecessor/successor
  • Users may over-use links since they are highly visible since they has their own tab and TDP users are used to creating links.
  • Randy recommends a strong communication plan to provide guidance on the purpose and usage of Links so they don’t encourage unwanted behaviors.
  • people try to recreate Gantt charts and continue the waterfall mentality and not follow Agile

Possible Alternatives to Links:

  • Story Map
  • Impediments

1 answer

1 accepted

3 votes
Answer accepted
Rich Sparks
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 02, 2020

I counsel teams to avoid using work item links for exactly the reasons you list in the Cons section. Having them in place doesn't necessarily lead to any clearer decisions or actions to be taken.

A team thinking about it's own work should use Story Maps as you suggest. And they can also use the Story Backlog Kanban sprint view to make sure their work is laid out in the best way to deliver what they need.  My colleague @Rob Phillips wrote about this here:

If you need to track work between teams (for example, my team needs something from your team in order to complete our work) then that's when Dependencies help. A dependency represents a contract between two teams (whether they be teams in the same Program/Release Train, or across different Programs/Release Trains) to provide something by a needed date or sprint.)

Dependencies show up on the program board and help stakeholders see where there are links between work, and the program board highlights when dependencies are at risk or late. I wrote about building out the Program Board during planning cycles here:

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events