Is the Sprint Field editable to limit it's Dropdown Values?

[Deleted user]

Hi there,

Story: As a user on issue creation we want to only allow one option when users click the Sprint Field dropdown and that option is "Backlog".

Question: Is there a way to on Issue Creation only choose the Backlog to where the new issue goes? 

The goal: Not have users pick a sprint to upload the issue to. 

[Fazila Ashraf]

Hi @[deleted] 

To achieve the goal, you should simply not have 'Sprint' field on the issue screen.

There are lots of side effects that you would face even if you find a workaround to restrict the sprint choice to Backlog (there is no option to restrict as far as i know).

You should simply use the agile board's built in features to groom the backlog in the backlog section(instead of using creating a sprint by that name)

Sprints in JIRA are global entity. There could be different teams using the sprint name 'Backlog' but internally are different sprint entities, adding more to the confusion.

https://www.atlassian.com/agile/tutorials/how-to-do-scrum-with-jira-software might help you to get the built in features clarified.

Hope these helps! :) 

[Deleted user]

Hi @Fazila Ashraf ,

So you're saying if we remove "Sprint" field from [name] Screen when a new issue is created it won't show the Sprint Field, but when it is created it will be sent to the backlog correct? 

Thanks!

[Fazila Ashraf]

@[deleted]  That is correct. 

[Deleted user]

Hi @Fazila Ashraf ,

Is there a way to not make the Sprint Field mandatory on one specific screen, and only show Backlog as an option for the dropdown values? 

SCRATCH THIS NOT NEEDED

[Deleted user]

Hi @Fazila Ashraf ,

is there a way to only show certain users on issue creation the Sprint Field dropdown? We've deleted the field, but is there a way to give some users access to this on issue creation? 

[Fazila Ashraf]

If you are using server/datacenter deployment and have scriptrunner, you could write some behaviour scripts to achieve this. 

But with my experience, i do not recommend this. For JIRA to be used as a standard agile project management tool, ask the end users to use it how it is designed to be used, following agile ceremonies. New stories should be groomed in backlog before committing it to a sprint.