You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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)
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.
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.