Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to edit "Licenkey" field under "Manage addons"

bharathkumar A
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 13, 2018

As a consultant, we are raising this request for one of the Jira users. He has 50 users Jira license is running on the server. But the users who have Jira system Administrators/Jira administrators rights are not able to Edit/Update the license key field. Also Jira is not connecting with the "Atlassian Market place". It is throwing an error under "Find new add-ons" page. 

So we requested those users to perform below operation listed in the below link 

https://confluence.atlassian.com/jirakb/unable-to-connect-to-marketplace-860003995.html

But it didn't help. Can you please provide some suggestion which we can try to resolve the issue?


The Affected Jira user(s) SEN number is: [redacted]
Jira server version: v7.2.1
License Type: Commercial 

1 answer

0 votes
Andy Heinzer
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 15, 2018

In my experience you don't need to have your Jira site be able to access our marketplace site in order to be able to activate a license key for a Jira product or a plugin for Jira.

However there was a known bug with the UPM that could have been used with that version of Jira.  Details of this are in https://ecosystem.atlassian.net/browse/UPM-5639

If your Jira site is using the 2.22.1 version of the Universal Plugin manager there was a known bug that will prevent you from being able to edit/update license keys.  Ultimately the fix for that situation is to change the version you are using, either newer or older.

Since this Jira site cannot connect to the marketplace, updating the UPM might be more tricky to do in your case.  So I'd recommend the workaround on that bug ticket:

Workaround
  1. Stop JIRA.
  2. Remove the latest UPM from the installed plugins folder.
  3. Restart JIRA.

The above would force JIRA to install the version of UPM that it came bundled with.

You should be able to find this plugin in the $JIRAHOME/plugins/installed-plugins/ folder and restart Jira in order for the system to revert to a previous UPM version that is not affected by this bug.

Suggest an answer

Log in or Sign up to answer