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

how can I assign sprints to a fix version?

hi guys

how can I assign sprints to a fix version?

I don't want assign issues to release directly . in fact I wanna assign issues to sprints then assign sprints to a fix version.

2 answers

1 vote
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Dec 18, 2022

Welcome to the Atlassian Community!

That's not what versions or sprints are for.  There's no way to associate a sprint with a version directly, versions are markers for issues.

If you want to equate them directly (give a sprint a version), then there's a really simple option - stop using versions, you don't need them because the sprint is the version.

I'm trying to resolve this now where I'm not sure how to name fix versions as we move to mutliple releases in a sprint - your comment makes sense. However I need to solve stakeholder management about what version/release/when a feature (epic) will be done. The current dashboard shows planned targets per monthly releases (fix versions)

Any suggestions on what to use in the case of multiple releases in a sprint which may not equate to a feature/epic being complete in the sprint ?

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 23, 2023

I think the best option is to automate something - two things I'd do:

  • when a sprint is created, create a version with the same name (in all projects that the board includes)
  • when an issue is moved to "done" during a sprint, select the version for the current sprint on it

I don't think you can do either of those with automation unfortunately, I think you'll need a scripting app for it (I'm obliged to yell "Scriptrunner" at this point because I work for Adaptavist)

0 votes
Tom Lister
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Dec 18, 2022 • edited

Hi @hdlk forex 

I see this would make sense to do in some setups. But sprint and version are usually different ideas. A sprint is an iteration of work. A version/release usually has some external meaning.

Unfortunately Fix Version is an issue field so has to be applied to each issue individually.

You could however try bulk applying the fix version once you have added all planned issues to a sprint.

You can use JQL to get a list of all issues in a sprint

project = BLAH AND sprint = "Sprint V1"

Sprint

You can then use the bulk change option to add a fix version to all issues.

You may need to specify the project as Fix version has project scope and all selected issues must belong to the same project to be able to bulk update it.

Suggest an answer

Log in or Sign up to answer