Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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
4,460,251
Community Members
 
Community Events
176
Community Groups

How can I get a perfect workflow using all the different tools (Jira, Autorabit, Bitpucket) ?

Hi All

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:

  • Jira
  • Autorabit ( because we work with salesforce) not sure if bamboo is compatible with Salesforce)
  • Bitbucket

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.

workflow.png

 

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.

  • What type of workflow do you use if you are using the same tools?
  • Any tips/ideas how i can improve this?
  • How best you can integrate all those tools?
  • Any suggestions or expiriences you can share?

thanks for your time.

best regards,

Tamara

 

0 comments

Comment

Log in or Sign up to comment