That's not possible.
The best approach would be performing a bulk-change Transition operation to set a resolution on all issues in Closed status, by using a workflow transition previously set to set a resolution.
Look at this other answer on how to remove that restriction:
(Edited: Despite of the title of the question "Change Security Level", the actions described in my linked answer have nothing to do with security levels)
It's more complex than that - it's not in bulk-edit because it's not on your edit screens. As a temporary fix, you can add it to the edit screens and then use bulk edit, but you must not leave it on the edit screens because your users will set the resolution accidentally on open issues.
Yeah, Nic is absolutely right, and I agree on the fact that temporarily adding the resolution field to the edit screen is a much easier and faster task.
You shouldn't forget to remove the resolution field from the edit screen after fixing the resolutions.
Also, do not forget to ensure that all transitions that go to the Closed status have a post-function for automatically setting the resolution field.
Alternatively to setting the resolution field automatically through post-functions, you may prompt users a screen which contains the resolution field as a required field, in order to force them to manually select a value. This approach requires to add a 'resolve issue screen' to each of the transitions that go to the closed status.
Likewise, in a similar manner, you should add a post-function for setting the resolution to None (clear the resolution field) on every transition that lets reopening the issue.
That's all transitions that go from the Closed status to any other statuses, including global transitions (those that have the 'All' tag, transitionable from every other statuses).
YOURS = the customer subdomain of your JIRA Cloud instance
KEY = the project's key (ie: Human Resources project is likely to have a project key like HR, which precedes every issue: HR-1, HR-124, and so on)
Click on the screen and add the Resolution field by selecting the Resolution field in the dropdown. That's easy and it's done as soon as you do it, with no need for saving anything.
Should you finally fix this, please, accept this answer
mmm... Try adding the Resolution field also to the View screen and let me know if that let's you fix the resolution.
If that weren't letting you set the Resolution, I would think that your query retrieves issues from some other projects where the Resolution field has not been added to the screen.
Perdon por el idioma pero sera mas facil explicar para mi.
Para un tipo de proyecto clasico funciona perfecto pero al usar otro flujo es distinto. Para que el campo Resolucion cambie a listo automaticamente cada vez que se cierra una incidencia se deben editar un par de acciones. Esto permitira correr un reporte de creado V/S resueltas (= Closed).
En la ultima transicion antes del ultimo estado copiar las propiedades y funciones de envío, ver adjunto que describe los pasos.
Lo siento pero mi sistema esta en español.
Hi @Thomas Fritzen ,
In the 10 gadgets offered by the add-on, there is a Release Burndown / Burnup Chart gadget than can be easily configured as Created vs Resolved Chart. Just take a look at this example.
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events