Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

BigGannt Addon wont enable after license purchase

I upgraded the BigGannt add-on to purchase the $10 license, but now the app wont enable. What can I do?

1 answer

1 accepted

0 votes
Answer accepted

Are you receiving an error when you attempt to enable it?  Did you add the license to the plugin?

Yes, I added the license to the plugin. When I went to enable it, the error said to check the logs. It also looks like it is suddenly no longer compatible with my instance of JIRA. It was working just fine yesterday.

Which version of Jira are you on and which version of the plugin is installed?  Does it give you an option to update it?  You may have to uninstall it and re-install it.

I'm not sure of the versions at the moment and I did not see an option to update. I've tried uninstalling and reinstalling but I keep having the same issue.

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.

I don't know how to access them.

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).

According to the Log Analyzer, it said that our instance of JIRA has reached End of Life, but our license auto-renews every year. It is showing an update to JIRA CORE, but I'm not sure if that would fix the problem or not with our license type....

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.

Hello Jessica,

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.

Best regards,

Adam

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.

Thanks for the update, glad to hear you have a better idea of why the error is occurring!

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

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

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you