The only way (natively, without 3rd party plugins) I can think of that Jira might allow you to edit a field, but not leave it with a blank value would be if your field configuration scheme was setup to make the Sprint field a required field. The problem with this is that when you set a field to be required, then from the time that issue is created, all the way through the life of that ticket, it is required to have some value there.
This might be feasible, but it would require everyone that creates a ticket in the project using this field configuration scheme to assign issues to a sprint at the time of creation. This change might cause more headaches than it solves. This could be a problem for a number of reasons:
- Sprint is a field that only Jira-Software users will be able to edit. If you have users that are only Jira-Core, or Jira Service Desk agents, they could see these issues, but they might not actually be able to create an issue if they can't enter a value for this required field at the time of issue creation.
- Having users enter some random value for that sprint could be problematic in regards to understanding if an issue should exist in that sprint, or if it might just be serving as a placeholder for the time being
There is an existing feature request that if implemented, I think would provide a solution for you. Please see JRASERVER-65813 for more details. Basically this feature request states that if Jira could only make a field required during a certain state transition (like "In Progress"), then it could do what you want. The work-around listed on that ticket is to use the plugin, Suite Utilities for Jira in order to implement a field required validator in the workflow. That plugin might provide a better solution for the time being than trying to make the field required in the field configuration.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.