Some users are unable to assign Sprint while creating a bug!

[Quality Assurance Traffic]

Some user with restricted policy are unable to assign Sprint while creating a bug on JIRA Cloud. The Sprint field says None.

The user can create a bug, but unable to assign Sprint to it.

Below is the attached image for reference.

Appreciate your quick response.

Thanks

[Tarun Sapra]

Hello @Quality Assurance Traffic 

Sprint assignment should always be done via the backlog view of the board by dragging and dropping issue on the desired sprint. If users start manually updating sprint values then if in case they map the issue to a wrong sprint then it can create lot of problems in the reports.

[Quality Assurance Traffic]

But why do we have this field then?

If you want to assign Sprint directly, then there is no need to drag and drop from the Backlog :)

[Tarun Sapra]

The fields exists because "Sprint" value is stories in a field. But I have seen so many users messing it up by specifying wrong Sprint because lot of sprint names are similar across multiple boards and once the issue lands up on the sprint board of another sprint then it will mess up the sprint related reports.

[Quality Assurance Traffic]

Actually, the above query is a bit different. In my case, some users with restricted policy are unable to assign Sprint to the bug.

That's what I posted.

[Tarun Sapra]

Yes, the original query is different, but my concern based on my experience of working with various clients is the fact that sprint field should ideally be auto-populated by movement of issue in the backlog. But rest I leave it upto your team.

[Quality Assurance Traffic]

Yeah, but still the query is not answered.

[Ollie Guan]

Hello @Quality Assurance Traffic ,

Are you sure there is a sprint that has been activated in the system? It seems that this value is empty from the picture.

[Quality Assurance Traffic]

Yes, Sprint is activated but it is not appearing in Sprint field for some users.