Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Bridging the gap between Team managed and Company managed projects

Inspired by the discussion (I started) Workflow controls...How do you do? (atlassian.com) 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)

thestory.png

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:

titles.png

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)

auto7.png

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.

3 comments

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

Comment

Log in or Sign up to comment
TAGS

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