You can edit this in the database. Please ensure JIRA is shutdown when you making changes. After JIAR is restarted you will need to reindex your data (Administration -> System -> Indexing). Please take a backup of the database before making any changes.

Also, please do not add the resolution if one was not set, or clear the resolution if one was present. Switching from one resolution id to another should be OK.

Thanks,
Anton

The whole problem, though, is that there is a resolution set and there should not be. What is the safe way for me to clear a resolution on an item incorrectly marked resolved?

If the issues are in the status that should not normally have a resolution, but the issues do have resolution set, you can clear it (set to null) in the database and then reindex your data (Administartion -> System -> Indexing. Please ensure that JIRA is shutdown while making the database update. If this is the case, can I ask how the issues got into this state?

Thanks,
Anton

I'll try reindexing, too, and let you know. In the mean time,I 'solved' the problem by making the field invisible on the default edit screen, then creating new issues for the old, frozen-out ones and killing them. I found the frozen ones by searching for statuses that are not closed but has a resolution, essentially.

For now you could do it in the database with SQL. The query would be something like:

update jiraissue set resolution=(select id from resolution where pname='Fixed') where issuestatus=(select id from issuestatus where pname='Resolved') and resolution is null;

and then reindex. Back up the database before doing this, of course. There is some database schema info in the docs.

Here is a small code extract:

1. Update fields
   $update_issue = $soap->updateIssue(
   $token,
   "MI9999-8",
   [
   { "id" => SOAP::Data->type(string => "summary"), "values" => SOAP::Data->type(string => "Some text") }, { "id" => SOAP::Data->type(string => "resolution"), "values" => SOAP::Data->type(string => "1") }

   ]);

Q1: Is this a coding problem, or can't the resolution field be changed via SOAP?

Jeff, ref: "For now you could do it in the database with SQL"
Some entries, here or on the forum, advise against changing the resolution field directly on the database.
What does "For now" means? We are running 3.6 and planning to upgrade to 3.10.

If you don't see a field on the "edit" screen, you won't be able to edit it by SOAP. If you temporarily add Resolution to the Default Screen, you'll be able to edit it via SOAP.

> What does "For now" means? We are running 3.6 and planning to upgrade to 3.10.

"For now" means until this feature request (bulk-editing of resolutions) is implemented.

By adding the Resolution field to the Edit screen of the project involved, I'm able to update it via Perl/Soap scripting.

Thanks for the tip, Karel