nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sprint Field - Multiselect

Any Russenberger

Hi Community! I have an urgent question...

Less than a week ago, the Sprint field allowed selecting multiple values. Starting today, I can only select one, and that's a problem for our projects.

I can't edit the field configuration, its' blocked, and I haven't made any other changes.

I also couldn’t find any notes about changes in the Jira backlog. Does anyone know if this can be reverted?

Help please!!

Accepted answers

Trudy P Claspill

Hello @Any Russenberger

An issue can be assigned to only one Active or one Planned sprint at a time. That has always been true, in my years of experience with both Jira Cloud and Jira Server/Data Center.

If you were able to select multiple values and assign one issue to multiple Active and/or Planned sprints at one time, that was a serious bug rather than working as designed.

All comments

Trudy P Claspill

Hello @Any Russenberger

An issue can be assigned to only one Active or one Planned sprint at a time. That has always been true, in my years of experience with both Jira Cloud and Jira Server/Data Center.

If you were able to select multiple values and assign one issue to multiple Active and/or Planned sprints at one time, that was a serious bug rather than working as designed.

Any Russenberger

For sure, we could do that! We were able to select more than 1 sprint.

Actually, last week we added a validation in the workflow to make the Sprint field mandatory during the last transition... Could that have "solved" the bug?

It's apparently a mystery...

Trudy P Claspill

Note that Sprint is a multiple-value field; it should hold the values from Sprints to which the issue was previously assigned where the sprint was Completed but the issue itself was not completed and was not removed from the sprint. But I have not seen the capability of actually selecting multiple values of Active and/or Planned Sprints at one time.

Adding a workflow Validator to require the field should not have made a difference. That would only require that the field have some value.

Are you sure that is the native Sprint field that you were using when selecting multiple values, and not another custom field with the same name?

Any Russenberger

I'm absolutely sure Trudy! It's not a custom field.

Anyway, I guess my teams will only use it that way now: just passing through the sprints and completing multiple sprints automatically.

Thanks for your help and concern!! I just wanted to be sure, and there's nothing more I can do for the teams now.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

sprint

field-configuration