We use the resolution field in JIRA to reperesent various states of delivery for an issue during the Resolve phase of its lifecycle. For some reason when the issue is moved to Closed JIRA is automatically setting the Resolution back to "Unresolved" Is there any way to keep the current Resolution when moving issues to Closed?
Sounds like one of your administrators has either
* edited the workflow and included a post-function to clear the resolution
* created a listener that catches "close" events and set it up to clear the resolution field
I'd rule those two out first - have a quick look for listeners, and then check the workflow
I tried removing "any" and "none" but that didn't fix the issue.
I did a bit more digging and found that the Workflow Transition to Closed has a post function set which clears the Resolution field. However, I can't figure out how to remove the post function. It only gives you an option to add more, but not delete the existing ones.
Any ideas how I can edit the post function to remove the line item which clears the resolution field?
Reading back through this thread I see this is the first thing you suggested I look at. However, I didn't add the post function. I'm guessing it's part of the default JIRA install.
Regardless, how do I remove it?
ok i tried to do the same...
i chose a project using a modified workflow...in agile configuration i set "Simplify Workflow" and indeed there will be added a post funkction "The Resolution of the issue will be cleared." to the "closed" transition.
but i do have the choice to delete it...can you please check what persmission you have on the project?
check Permission Schemes and Project Roles
i see "The Resolution of the issue will be cleared." is going to be added to all transitions...which currently makes no sense to me...what is the use of setting a resolution to "none" if you resolve an issue...
i think this has to be checked out by Atlassian if this is really a feature or a bug.
I'm using our Sysadmin account, so I should have blanket permissions, no?
I agree with your note. Seems like clearing the resolution is making a pretty big assumption about people's workflows. We clearly need it to reamain set for ours. I would think it should have to be explicitly added as a post function.
Admin role wasn't set, so I added it, but still don't see any "Delete" button or link when I got to edit the workflow. I'm sure I'm still doing something wrong.
I've already fixed my problem by hand editing the XML, so I have little motivation to investigate this further ... that is until the next time I need to remove a post function ;-)
check if your sysadmin account is in the role "Administrator" for your project. this should be fine then.
then please go to administration/issues/workflow and select the greenhopper workflow which is currently assigned to that project and click "edit"
then open at lease the closed & resolved transitions ... you should see something like this:
(hmm attachement doesn't show up)
strange....what user groups your account is in?
your in jira-administrators and your got full admin access don't you?
if not did you set up global permissions using a stripped down administator-group like jira-systems-administrators
in one of these groups (is believe so) you must be in to see the "Administration" Link top right next to your username...only project administrator role won't let you modify the real workflow
Please bear in mind that "system administrator" rights mean you can administrate the system. It does NOT mean "I can do everything and ignore the permissions". That's a really badly broken approach to a system admin account for several reasons and an appalling default if someone does do it. But check your workflow permissions and permission schemes - it is fine to add in "system admins can do this", as long as you think it through.
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