Resolutions and Permissions Missing from Simple Issue Tracking or Software Development Project

Symptoms

In Simple Issue Tracking or Software Development Projects:

• Moving an issue to 'Done' fails to set a resolution on the issue.

• Reopening an issue fails to clear the Done resolution from the issue

• Any user (not just assignable users) can see and use the Reopen, Done, etc. buttons to transition an issue.

N.B. This behaviour won't be observed straight away in a new project, only after some time has passed or the instance has been restarted.

Cause

Prior to JIRA version 6.2.1 / JIRA Project Templates plugin version 2.27, a bug in JIRA Project Templates (JRACLOUD-66503) prevents permissions and resolution functions from persisting to the database. This means that as soon as the workflows cache is cleared, resolutions stop being set or cleared, and issue transition permissions are lost.

Workaround

To Manually Reinstate Resolutions and Permissions for a Project

Use the workflow editor found via the Project Administration page ( at Projects >> Your Project >> Administration ) to re-add missing Post Functions and Permissions.

For a Simple Issue Tracking Project Workflow,

• Add an Update Issue Field post function to set resolution to Done to the two transitions named Done (ids 21 and 41)

• Add an Update Issue Field post function to blank out the resolution to the Reopen and the Reopen and Start Progress transitions (id 51 and 61)

• Add a Permission Condition to each transition to Assignable (or Resolve Issue permission, as preferred)

For a Software Development Project Workflow,

• Add an Update Issue Field post function to set resolution to Done to the three transitions named Done (ids 21, 91 and 151)

• Add an Update Issue Field post function to set resolution to Blank to the Reopen, Reopen and Start Progress and Reopen and Start Review transitions (51, 61 and 101)

• Add a Permission Condition to each transition, either Assignable or Resolve Issue permission, as appropriate.

To Fix Issues in an Invalid State

Once resolutions have been reinstated by upgrading JIRA or manually (as above), issues with an incorrect resolution can be repaired.

• Find invalid issues in the issue navigator, one status at a time, using JQL like the following:

  • project in (Your, Projects) AND status = "In Review" and resolution is not empty

  • project in (Your, Projects) AND status = "Done" and resolution is empty

  • project in (Your, Projects) AND status = "To Do" and resolution is not empty

• For each set of issues, progress through the list transitioning issues out of and back into their status to reset the resolution to the correct value. This can be done rapidly using the j/k or up/down keys and the dot dialog (pressing . and typing the transition required). NB: Watchers and participants in the issue will receive email notifications if there is a notification scheme set up. For example:

  • For Done issues with no resolution, Re-opening then re-marking as Done will set the resolution properly.

  • For issues that are To Do, marking as Done then re-opening will clear the resolution.

Resolution

• Upgrading to JIRA 6.2.1 or above will correct this bug in any new Software Development and Issue Tracking projects.

• Upgrading will also repair permissions / resolution post functions for any existing Simple Issue Tracking and Software Development projects that have not had their permissions / resolution post functions modified. In other words, if an existing project's workflow has had any transition permissions added, permissions for the workflow will not be added upon upgrade, even if there are still some missing. If that same project hasn't had any post functions added to set resolutions, however, these will be added.

• The JIRA Core templates plugin can be downloaded or installed via the UPM for JIRA 6.1.6+ . This will correct new projects created using these templates, but will not repair existing projects.