Unlock the Sprint Field

[Fouad Fares]

I would like to unlock the Sprint field in order to set a default value when creating an issue.

[Nic Brough -Adaptavist-]

You should never default or set a sprint value automatically.  If you really think you want to do that, you have a non-Agile and probably broken process and shouldn't be trying to use Scrum tools. 

Creating an issue in a sprint should be an exceptional act, rarely performed.  Issues should be drawn into a sprint during sprint planning, not creation.

You can't unlock fields on Cloud.  They are locked to prevent you misconfiguring them.  Defaulting a sprint is a misconfiguration.

[marcinnowak]

That's a subtle difference between software working for people, and people working for software. And Scrum is not the only one agile methodology which Jira can handle :)

[Nic Brough -Adaptavist-]

That is very true.  But it doesn't change the fact that Scrum tools tend not to work for non-Scrum processes, or that defaulting a sprint is a complete failure to be Agile.

[marcinnowak]

Yes, defaulting a sprint can be failure for Scrum, but I can easily imagine a future sprint (which will be never started) used as a grouper for backlog, to hold important tasks for Very Important Customers. Issues matching some criteria can have this sprint assigned automatically.

You can think about this as a kind of priority over priority :) Grouping of backlog items helps a lot during planning sessions. Same as expedite lanes on the scrumboard are helpful for solving bugs and breakdowns on production during active sprint (typical challenge for production and maintenance of released product).

Jira is very elastic. Sometimes it is hard to setup, but solves our 90%+ cases. It is good to have possibility to break the rules, if this help with work in the spirit of agile manifesto :)

I've unlocked Sprint field by adding scrum board to kanban-like project. Thanks :)

[Nic Brough -Adaptavist-]

Yes, that's not a Scrum approach, it's a lot more Kanban.  You should use the process that works best for you, and get your tools to support it.  With Kanban, you don't need to "unlock" the sprint field, Kanban doesn't have sprints, so there's nothing to unlock.

[Trudy Claspill]

Do you want to initialize the field and then allow users to modify it while creating the issue? Or do you want to have the sprint value fixed programmatically during issue creation?

You could look at modifying the workflow to set the field during Post Functions.

There are apps that can be added to JIRA that would help you initialize a field during issue creation when the Create Issue dialog is opened, allowing users to edit the value after it is initialized and before the issue is saved.