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

Negative impacts from turning on the Approach toggle on features to enable Multi-ART Features

Our team recently learned about the "Approach" toggle that can be enabled on features to allow multi-release train features. Our team is thinking about turning this on to allow better transparency on work that is needed from dependent release trains. Before turning it on I had a couple of questions I wanted to clarify. 


1. I see that you can only select the primary release trains PI's. Does this mean that the feature will not show up on the release train board for the other release trains that have work associated? 

2. Has anyone seen any negative impacts of turning this on? 


Any insight from teams who have enabled this would be very helpful. Thanks!

1 answer



based on my understanding of the problem you are trying to solve above. This will not solve your issue.  

given that Features may only :

1) be assigned to a single PI 

2) integrate to a single JIRA project (and maintain synchronizations) 

unless all associated trains are working g in the same PI this approach will not provide visibility - especially on the affiliated program boards. 

I would recommend 2 things- 

1)easy solution- enable program to program (if in same portfolio but different PIs) and portfolio dependencies (if in different portfolios) or use external dependencies on each board to reflect the team level dependencies (the last is a hack - and should be last resort) 

2) conduct a value stream workshop and portfolio workshop to gain better alignment on your system/product and value flows in order to align trains appropriately. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events