-
Bug
-
Resolution: Fixed
-
Highest
-
Severity 3 - Minor
-
10
Issue Summary
When customers migrate from server to cloud, one of the steps is to review groups in the product access page and set the default access group (Use Jira site import from server to cloud - Step 8)
However, in cases where default access group is not set, the add-on installation in jira cloud will fail with the following error:
We ran into a little trouble. it might just be a hiccup. Try again in a bit.
Steps to Reproduce
- Scenario: Customer has migrated from Server to cloud and default access group is not set in the product access
- Try to install a marketplace add-on in the instance
Expected Results
The add-on installation fails with UI error message stating:
There is no default group in Jira cloud product access. Please review groups imported from server and set a default access group for each product
Actual Results
The add-on installation fails with the following error message which is not helpful:
We ran into a little trouble. it might just be a hiccup. Try again in a bit.
Workaround
See the KB: Unable to Install any Cloud Add-ons
- is related to
-
ECO-85 It should be documented how the connect app user and groups work and how changing default product access groups can break apps
- Gathering Interest
- relates to
-
-
- Closed
-
-
- Gathering Interest
-
AC-2320 Loading...
- followed by
-
ONECLOUD-1081 Failed to load
- is resolved by
-
- links to
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
[MP-53] Add-on installation fails when there is no default access group set in the product access
Workaround
In some cases, this problem can appear for instances that don't have a default group, even though they have not recently migrated. For such instances the following steps should be actioned in order to create a default group:
Creating a new group and then making it a default group
- Log in to admin.atlassian.com and select your site
- From your User Management page, select Groups from the left side of the page
- Select the Create group button to create a new group
- Enter the Group’s name — for example, new-default-group-for-Jira-Software
A group’s name cannot be changed after being created. - Select Create
- You’ll be redirected to the Groups details page where you can add products to the group and give group members product access
- Select Edit group's access and under Jira Software hit Add Group and select the new group you've just created then hit Add Groups
- Now click on … right next to the new group name under Jira Software and click on Make this group default
I have authenticated and the Issue Links on the current page shows "Authenticate to see additional information" for the four pages attached to this issue.
Closing this ticket, the fix has been deployed to production on JIRA.
For the scenario (Server to Cloud Migration) which requires default groups to be created, the failure of app installation will now show an appropriate message guiding the users on how to do that.
A message to the support team: ** Since this is a really tricky issue to reproduce, we couldn't verify it on production. I would suggest re-opening this issue if you see a similar ticket raised in the future.