I keep trying to allow the resolution field to be active in my various issue screens, however, as soon as I activate the field users can't create a new issue or edit an existing issue without entering a resolution in the field.
There is no option (that I can find) that allows this field to stay as blank.
Because I can't get this field to work properly - none of my issues have been set as resolved and I just have a status for Closed and everyone has to create their own "open" issues list, as the system defaults won't exclude status = closed, only identifies Open as those that aren't resolved. A bit irritating.
Do not do this.
The intended use of the resolution field is for you to place it only on screens that are transitions into a closed type status (generally the green ones). The field is working "properly", you just need to use it as it is intended.
If you don't want to put it on a transition screen, then set it with a post-function instead (and don't forget to clear it on re-open type transitions)
You must never put it on a create or edit screen.
The Resolution field is an important field in Jira. Mosty it means that the issue is Resolved that is why you should link the field to a transition screen only if you really need the field to be filled. For example, if you resolve an issue then you have to provide a Resolution. You can not resolve an issue without a Resolution. If you do not resolve an issue then there is no need for the resolution field. I guess you need to reconsider your current process.
Unfortunately, both of these answers bring me back to a question a year ago I sent to support which was how do you automate a task to transition to the resolution screen I have setup? The only transition that works for me is when I switch to Testing Required - that workflow auto-opens a separate issue screen to allow entry of testing specific details before the item transitions over to the new status (this transition though was automatically configured - I didn't do anything to make this happen). Anyone have a useful link to a help resource for this setup?
Ok, that's quite confusing and does not sound like Jira. Specifically:
> how do you automate a task to transition to the resolution screen I have setup?
I'm not sure what you mean by "a task to transition to the resolution screen". A transition is a path from one status to another, not to a screen. However, transitions can have screens attached to them, which are popped up when you use the transition.
> The only transition that works for me is when I switch to Testing Required -
Do you mean you use a transition called "testing required"? Not "switch to" (as I don't understand that)
>that workflow auto-opens a separate issue screen
Jira does not do that. It can open a transition screen in the current window that asks for information and then takes you back to the issue view or board you were on before (i.e. it's not "separate")
Going back to the original question though, it remains quite simple - you need to put the resolution field on a transition screen when closing issues.
I'll close this question. Unfortunately, I'm in the same place I was with this one a year ago. I can't get a separate screen to open when I transition an issue (ideally, any screen with the Resolution fields) - I can't find any help documents on it and when I submit to support I don't get a response. I'm obviously not explaining my missing information properly. I'll continue with the process of not having issues in the resolved status - thanks for your patience.
I really don't understand this. Popping up a screen with a resolution on it is an incredibly simple standard function that we all use all the time, and it ships in some of the default workflows.
What happens when you try the following?
Create a new issue and move it through the workflow. You will get a screen pop up with the resolution on it.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot