Priority Scheme is missing in Jira

‘Priority Scheme’ is a new feature that is introduced since Jira 7.6, which allows you to customize the priority for different projects.

We recently upgraded a Jira box from 7.5.1 to 7.6.6, but we did not see the ‘Priority Scheme’ in the newer version. It turns out that it is disabled by default in some cases. You have to enable it in the Dark Feature.

How to:

1) Go to /secure/SiteDarkFeatures!default.jspa
2) Type ‘jira.priorities.per.project.enabled‘ on the left side input field.

By now, you should be able to see the ‘Priority Scheme’ in the Issue tab. Also there should be a ‘Default Priority Scheme’ listed there (if you are lucky). Also one thing to notice is that the message ‘Priority schemes are only available in JIRA Service Desk from 3.9.4.‘ that is mentioned in this Atlassian documentation is not right. This has been confirmed by Atlassian support. Only Jira service desk 3.10.0 or newer supports priority scheme. Read more in 3.10.x release notes.

In our case, we don’t have the ‘Default Priority Scheme’ in the ‘Priority Scheme’. So I contacted with Atlassian support, per them the related database records were not successfully created when upgrading. So we need to manually create those records.

Here are the How to:

1) Stop JIRA and take a database backup.

2) Run the following select statements to verify whether any entries with the ID exists. If any of it returns a result, please do not proceed with the INSERT and get back to Atlassian on which table has result, and provide Atlassian the entire table output (select * from tablename). We try not to insert the entries after the last ID so that we don’t have to mess with the sequence of the tables if there is any.

select * from fieldconfigscheme where id = 10050;
select * from configurationcontext where id = 10050;
select * from fieldconfigschemeissuetype where id = 10050;
select * from propertystring where id = 10050;
select * from propertyentry where id = 10050;
select * from fieldconfiguration where id = 10050;
select * from optionconfiguration where id = 10050 OR id = 10051 OR id = 10052 OR id = 10053 OR id = 10054;

3) Proceed with the following insert if you have verified that the above does not return any results.

INSERT INTO fieldconfigscheme(id, configname, description, fieldid, customfield) VALUES (10050, 'Default priority scheme', 'This is default priority scheme used by all projects without any other scheme assigned', 'priority', null);
INSERT INTO configurationcontext(id, projectcategory, project, customfield, fieldconfigscheme) VALUES (10050, null, null, 'priority', 10050);
INSERT INTO fieldconfigschemeissuetype(id, issuetype, fieldconfigscheme, fieldconfiguration) VALUES (10050, null, 10050, 10050);
INSERT INTO propertystring(id, propertyvalue) VALUES (10050, 10050);
INSERT INTO propertyentry(id, entity_name, entity_id, property_key, propertytype) VALUES (10050, 'jira.properties', 1, 'jira.scheme.default.priority', 5);
INSERT INTO fieldconfiguration(id, configname, description, fieldid, customfield) VALUES (10050, 'Default configuration for priority', 'Default configuration generated by JIRA', 'priority', null);

INSERT INTO optionconfiguration(id, fieldid, optionid, fieldconfig, sequence) VALUES (10050, 'priority', 1, 10050, 1);
INSERT INTO optionconfiguration(id, fieldid, optionid, fieldconfig, sequence) VALUES (10051, 'priority', 2, 10050, 2);
INSERT INTO optionconfiguration(id, fieldid, optionid, fieldconfig, sequence) VALUES (10052, 'priority', 3, 10050, 3);
INSERT INTO optionconfiguration(id, fieldid, optionid, fieldconfig, sequence) VALUES (10053, 'priority', 4, 10050, 4);
INSERT INTO optionconfiguration(id, fieldid, optionid, fieldconfig, sequence) VALUES (10054, 'priority', 5, 10050, 5);