I want to be able to make sprint a required field however its locked and I can't make the simple change needed.
So...why would the sprint be a required field? Secondly, using vanilla Jira, I'm not sure you can do that. All the tricks to make a field required, would make the field ALWAYS required, which defeats the purpose of things.
If it can't be done fair enough however the reason I asked is because we have on occasion tickets logged where users forget to add the sprints and those tickets don't get grouped with the others when needed.
Being able to make that option a required selection when logging a new ticket would have fixed the issue.
Um, the whole point of the sprint field is that issues are mostly logged without a sprint. Then the team does sprint planning where they place the issues in the right to-do order and then plan them into a sprint. Knowing which sprint a new issue should be added to is an edge-case which is supported, as you can fill it in. Making sprint mandatory is not even vaguely Agile, it makes planning, scrums, velocity and so-on pointless, and hence it's not possible in JIRA Software.
Well tbh not all teams works the same and there are things known as backlog/planning sprints which issues go into before being moved to another sprint at a later date.
If you don't agree with the question thats fine but please respect that not everyone works the same and that agile itself is fairly adaptable depending on the needs of a project or business.
Seens as the original question has been answered we'll find another solution to our problem
When the first transition occurs (Open) you cannot add a condition to look for the field, but you can add a validator that checks to see if a certain field has data, i.e. the sprint field. Not ideal if you need to add this to a bunch of workflows, but it can perform the expected result.
It looks like you're new here. Sign in or register to get started.
