Issue Summary

Loading a plan and viewing it the roadmap includes an issue(s) with no Priority. Attempting to edit the Issue's Priority results in an empty drop-down list. Consequently the Issue's Priority cannot be viewed or modified.

The server error log indicates that the corresponding Project's Priority Scheme could not be retrieved.

Background

Jira introduced the concept of Priority Schemes in Jira 7.6. In addition to the default scheme, administrators can now create their own schemes with different priorities, relative order and/or default priority. By default, a Project is associated with the default Priority Scheme. A custom Priority Scheme can be associated with a Project by an administrator. A Project should always have a Priority Scheme, either a custom scheme or the default. You can find more information in the Jira product documentation.

In Portfolio 3.4, we added support for the Priority field in the roadmap. This allowed plan users to view/update an issue's Priority from the roadmap. In order to support this, Portfolio loads from Jira the Priority Scheme for each Project in the Plan. It does this so that it can correctly indicate which Priorities are available for an issue and their relative order.

Versions Affected

The underlying issue has been observed by customers on 3.13 and 3.14 and it is expected that all versions from 3.4 onwards are affected as this is when loading Priority Schemes was added. In 3.17 a check was added that minimises the impact.

Steps to Reproduce

The steps to reproduce are unknown at this time. We are raising this ticket to help us gather information about the cause.

It is possible, but not confirmed, that changing a Project's Priority Scheme may be the cause.

Expected Results

While viewing the roadmap, each Issue's Priority should be visible (provided the Priority field has been added to the roadmap). When editing an Issue's Priority, the corresponding drop-down list should contain the Priorities applicable to the Project that the Issue belongs to.

Actual Results

The Issue's Priority field is blank and the corresponding drop-down list is empty:

The following warning is logged in the atlassian-jira.log file:

No priority scheme for project: <project key>

Workaround

For at least one customer, associating a new Priority Scheme with the affected Project(s) in the Plan resolved the issue. This is configured through the Jira Administration menu, via Issues -> Priority Schemes.

No other workarounds are known at this time.