nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA 7.8 There is NO option for Priority Scheme

Elvis Haračić

Hi,

we have an issue with the Priority Scheme, on the UI under the Priorities tab there is only one option: "Priorities" but there is no "Priorities Scheme" option as it is spoosed to be agter the verion 7.6.0

UI - There is NO option for Priority Scheme. Installed versions:

JIRA Service Desk 3.11.0

JIRA Software 7.8.0

Regards,

Elvis

Accepted answers

All comments

Nic Brough -Adaptavist-

Jira 7.6 and above all have priority schemes - could you show us a screenshot of where you think it should be and confirm the version of Jira and Jira Software from the system info page?

Elvis Haračić

Please find attached the screenshot.

Regards,

Elvis

Nic Brough -Adaptavist-

The layout looks a little different to mine, but that should not stop us. At the top of any of the admin pages there should be a search - if you put "priori" into it, does it suggest "priority schemes"?

Are you a full administrator too? Not just a project admin?

Andy Heinzer

It looks like you upgraded directly from Jira 6.4. This could be a problem since there is an expectation that all Jira versions older than Jira 7.0.x should be upgraded in a path that goes through a 7.0.x version.

It could be this is something a Jira admin can't be, but a system admin can see. However if you are logged into Jira as a system admin, then my concern would be to see your logs from the time of this upgrade. I suspect you might have one or more upgradetasks that did not complete as expected. In support we have seen a number of cases have this happen when the version of Jira you are upgrading to does not have support for your specific database version on the back end (for example MS SQL 2008 or earlier versions were known to be unable to run the upgradetask in Jira 7.4 for the kanplan feature.

Would you mind creating a support zip from this Jira site and posting a link to it so we can take a closer look?

Elvis Haračić

Nic, I am a "full admin", also on serach there is no prioritie scheme option.

Andrew, I have created support.zip but I am not able to upload it?.

Regards,

Elvis

Andy Heinzer

I'm afraid our community site does not allow for the upload of non-images at this time. However you could use a service like Google Drive, Dropbox, etc in order to share that file to a public url, and then post that url to this thread so we can take a closer look.

Elvis Haračić

Hi andrew,

please find the support archive on the location:

https://drive.google.com/drive/folders/1Pmtad_VNjK17v-fknQAWVvumpLnPFX4l

Regards,

Elvis

Andy Heinzer

Hi @Elvis Haračić

In reviewing your logs I found that Jira 7.8.0 appears to be starting, however I also found this detail in the latest startup.

Database Version       : Microsoft SQL Server - 10.50.6000
Database Driver        : Microsoft JDBC Driver 6.2 for SQL Server - 6.2.1.0

That database version corresponds to a MS SQL 2008 database. This database version is actually unsupported in Jira since 7.2 versions and higher. As a result, it is likely that your data has not been fully upgraded to the Jira 7.8.x structure of the database layout yet.

The logs would tend to agree with this idea, since they do not indicate a completed upgrade to 7.8 yet:

___ Upgrade History _______________________
    
         7.0.0#70107
              Time Performed                                : 2015-10-23 16:23:20.76
              Original Version                              : 6.4#64014
    
         6.4#64014
              Time Performed                                : 2015-03-23 12:06:10.13
              Original Version                              : 6.3.11#6341
    
         6.3.11#6341
              Time Performed                                : 2014-11-28 11:06:22.703

This makes more sense, because Jira 7.0.0 did support a 2008 SQL database. However what I would recommend here would be to switch databases for Jira to a supported platform. I believe that you can do this to both get on a supported platform AND to correct this specific problem. When Jira starts up and connects to your exists database, I believe it is going to trigger an attempt to upgrade your existing data. Please see the supported platforms for Jira 7.8.x in

https://confluence.atlassian.com/adminjiraserver078/supported-platforms-947188411.html

If you want to keep using MS SQL, then you would need to use either a 2012 or 2014 database for that version. Alternatively, you could select any of the supported databases in that document and use that instead. I would recommend following the guide in Switching databases in order to complete this process.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server