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

Bridging the gap between Team managed and Company managed projects

Inspired by the discussion (I started) Workflow controls...How do you do? ( I thought I'd share an experiment I did around bridging the gap between Team managed and Company managed projects.

 Below is the user story (written in Next-gen/Classic terminology)


The problem statement: How can we maintain Programme/ART level reporting (where we use a standardised SAFe workflow scheme for all ARTs) while allowing certain teams to experiment with Next-Gen (Team managed) projects.

The acceptance criteria were all met using automation for Jira on Jira premium cloud.

In order for this automation suite to work a few simple rules had to be applied on the team managed project.

  1. First column must be To Do, last column must be Done. This was so the transition issue automation trigger could be used....all in progress statuses (the ones in-between could be handled by Status category)
  2. They must use Story and Feature as their main issue types (as they will be the types that the automation would monitor and sync back to the Classic project)

Below are the titles of each automation:


The "Linking classic epic from NG Story" automation is probably the most cryptic in terms of description and was the hardest to conquer. The idea being, we need a way to sync any stories linked to a Next Gen Feature but post creation of that story (a likely scenario)


The net result of all of this was, a team could "go rogue" with a Next-gen (team managed) project, but enough high level information could be created and kept in sync with their ART/ Programmes Classic project by the automation suite to not disturb or make the team disappear from existing reporting, metrics and visualisations.

If you are interested in further details of the automation rules, feel free to hit me up about them.


Taranjeet Singh Community Leader Apr 20, 2021

@Curt Holley thanks for sharing this knowledge. This looks like a good way to bridge the gap between Team-managed and Company-managed projects.

Like Curt Holley likes this
Bridget Community Manager Apr 20, 2021

Yes, thanks for this article @Curt Holley !

Like Curt Holley likes this

Great idea @Curt Holley 👍

Like Curt Holley likes this


Log in or Sign up to comment

Atlassian Community Events