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,456,603
Community Members
 
Community Events
176
Community Groups

What is the best way to set up Jira for a team working on multiple builds at the same time?

Edited

I have both an Android and an iOS team who work on multiple builds at the same time.  I inherited a Jira set up where there is one project and the builds are represented by sprints.  Each sprint represents a build and there could be as many as 3 different builds being worked on by either team at any given time.  It's very confusing for the dev team to have to reference multiple sprints even when the build date is included in the sprint name in an effort to make it as clear as possible.  It also makes stand up hard having to cycle through multiple sprints (which are referred to as boards within the company) not to mention it's difficult to understand everyone's workload. 

What is the best way to set Jira up to accommodate one team working on multiple builds at the same time?  I've considered creating a new board pulling in all of the active sprints and am thinking if you can base swimlanes on sprints the devs could be working from one board but still have the individual sprints separated out visually.

As an aside, we aren't using sprints as anything other than a way to filter the issues within a build.  The sprint length is however long we have until a build is due and that date is set by the business.  Is it possible to calculate velocity in this situation?

 

 

0 comments

Comment

Log in or Sign up to comment