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,457,109
Community Members
 
Community Events
176
Community Groups

Default 'Sprint' field need to accept multiple values, like completed sprint as well as current one

 

Problem:  Default 'Sprint' field need to accept multiple values, like completed sprint as well as current sprint

We are JIRA Cloud, we are unable to add multiple sprint values to Sprint field of JIRA.

Example: Sprint0 (Completed), Sprint1(Current), Sprint2 (Future), expectation is user would like to add Sprint field of JIRA as Sprint0 + Sprint1 or Sprint0 + Sprint2

Current Project: Parallel Sprint Company managed project is ON

Attempted to fix this by reading Atlassian support documentation/community, still it is not working. Please help.

1 answer

0 votes

Issues do not go into multiple active sprints, it would make a nonsense of your reporting and confuse your users as to who should be actually working on it.

The sprint field is a bit complex though, it does contain multiple values, but they are not directly editable by the humans.  It shows all the sprints the issue has been in, including the current one

It is too far from a realistic situation. It happens most often in teams that a user story last for more than one sprint.

In the previous company we could have multiple sprint showing up in the sprint field. One of them was the active one and the others were more like read only field showing the history of the sprint this ticket lived.

Ok, but no, I'm afraid not.

> It happens most often in teams that a user story last for more than one sprint.

Argh.  No.  When a story rolls over into another sprint, then your team has failed.  It should be looking at why it has failed and trying to fix the problems the team has.

That's the whole point of doing sprints - a story should fit within a sprint, and when your team fails to do that, you know it has a problem that needs fixing!

"It happens most often" = broken process, broken team, broken expectations.  It should be "on the rare occasion it happens, we try to analyse and fix a broken thing"

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events