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; } } }

Agile functions (boards, sprints, etc) missing from Jira Server after restart

Jon Halewood

Hi all,

I hope someone here can point me in the right direction with this!

Today we had to restart our Jira server, and when the system came back, all of the functions for boards, sprints and such was gone. Totally missing, with no links or mentions anywhere.

This is on a server we own, running Jira Software v7.3.0#73011-sha1:3c73d0e.

Much of the documentation on this suggests this is either due to the Agile plugin not being loaded, though this is supposedly depreciated with all the functions now being part of Jira Software, or checking the license, which shouldn't be an issue as this is a perpetual license and not a cloud subscription.

Any ideas on how we can restore these features? It's very odd as everything else on the system is working fine!

Thanks in advance!

Comments

Charlie Misonne

Hi Jon

Can you check on the "Versions & licenses page if Jira Software is installed? (not only licensed)
Also check on the "Manage Add-ons" page if the application components are enabled by filtering for "Application Components"
Check your log files for any errors at the time of your startup. Some crucial parts might not have been enabled successfully

2018-01-24 15_00_27-Manage add-ons.png

Jon Halewood

Hi,

Thanks for the reply!

1) On the versions and licenses page the Jira Software entry is listed.

2) In the add-on modules page, we can see both Jira for Software Plugin and Jira Software Application entries. Under each of these the modules are all enabled.

3) We're trying to look at the logs for this, but there is alot of data to sift through. We've ran the standard Jira application log through the analyser and that flagged nothing obvious up. Is there anyware you can reccomend as a good starting point?

Is it possible this could be related to the support being expired, despite being a perpetual on-site iicense?

Thanks,

Jon

Jon Halewood

We finally managed to resolve this!

Turns out there had been a permissions change on /var/atlassian/application-data/jira-42/log/atlassian-greenhopper.log, and that was enough to stop it all from working.

Thanks for the input @charlie Misonn!

Jon

Welcome!

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

Quick Links

Find more posts tagged with

jira-software

agile

board