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
I am trying to find a solution on the perfect workflow for our team who is using Jira.
Currently we are using the following tools:
The workflow that we created is huge in order to cover the connection between the tools and makes the live of our Scrum Masters and Squads difficult to track their work.
We work with SAFe Agile, which means we have sprints/iterations that close every 2 weeks.
When an sprint/iteration passes the 2 weeks the Stories arent closed, as we cover the entire process until a story is in production.
But since we have a huge workflow the stories actually never close until they are final in production - this means the iterations stay open the entire release. The Scrum Masters have to oversee the workf for all iterations, because it can happen that when "end to end testing" of a story happens, a bug is found, so the status moves back to "technical development", which again means the developer that created the part has to repare it.
If in our first iteration/sprint we had 20 story points and we would move the stories to next iteration, over and over - because they aren't closed-done, this would again not give us right data in reports and at last iteration/sprint of the release we might have 100story points.
The reason we created this type of workflow is because it covers a lots of happenings in autorabit and which triggers status change from Jira.
thanks for your time.