Do you have access to the error logs? You may have to look through the logs to see what is happening when you attempt to enable the plugin. Is your instance behind a firewall at all or do you have a proxy? Something could be causing an error with the plugin reaching the marketplace.
Do you have access to the server? If not you could create a custom support zip (https://confluence.atlassian.com/support/create-a-support-zip-790796819.html ) and access the logs that way. You would want the application logs and the plugin information. Once you open the application log, you can scroll towards the bottom and find the last few errors that occurred.
Another option is to use the Support and Troubleshooting plugin. Go to administration -> System -> Troubleshooting and Support tools. You will see a tab for Log Analyzer, if you click on that you should see some errors that Jira has recognized. It's also a good idea to make sure that the Instance Health passed everything (everything has a green check mark next to it).
Can you try uninstalling your current version of Big Gantt plugin, download and install the version that is compatible with your Jira instance here: https://marketplace.atlassian.com/apps/1213016/biggantt-gantt-chart-for-jira/version-history and see if that works?
The End of Life error indicates that your Jira version is outdated, you can see more information here: https://confluence.atlassian.com/support/atlassian-support-end-of-life-policy-201851003.html it is recommending you update your Jira instance to a newer version, your Jira license being renewed is separate.
I am very sorry to hear that you face some difficulties with our BigGantt product, and I would be more than happy if we can solve this for you so that you can start using it as soon as possible.
With this having said, may I please ask you to create a ticket for our Support Team, by using Service Desk form, so that we can start the investigation? Our product specialist and developers will then check this thoroughly.
Thank you. I already submitted a ticket and it is being investigated. It seems we have a JVM memory issue perhaps. I am waiting to hear back to see how we can correct it. We work with sensitive servers so I'd prefer to wait until we get specifics before we go poking about.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event