Issue Summary

Enabling enterprise product via Admin hub fails with 400 error

Steps to Reproduce

Method #1
Find an existing site and try to add an Enterprise product

Method #2
Spin up a new Enterprise site under the Enterprise organization

• Go to admin hub > Apps
• Click on Add App
• Choose any enterprise product
• Choose to start a new site

Expected Results

The new Enterprise app should be allowed to be created.

Actual Results

The new Enterprise app cannot be activated. The following error is returned by the activation endpoint

  "statusCode": 400,
  "message": "Request failed with status code 400",
  "cause": {
    "statusCode": 400,
    "method": "post",
    "url": "http://.............s",
    "data": {
      "title": "License coupling validation failed for order items",
      "code": "E9000",
      "detail": "License coupling validation failed for order items.",
      "status": "400 BAD_REQUEST",

The site name used when the failure was encountered is not available for use for the next 7 days.

Workaround

Method #1
Enable the standard or premium version of the product first on the existing site.

• Request Atlassian licensing support team to enable the Enterprise license for the product.

Method #2
Enable the standard or premium version of the product first.

• Go to admin hub > Apps
• Click on Add App
• Choose Confluence or Jira Service Management product (Jira will not work)
• Click on "Start a free 7-day Standard trial instead"
• Create the new site. Set any temporary name
• On the newly created site. Enable other necessary products (ie. Jira) as standard
• Cancel the products that are not needed in the new site
• Request Atlassian licensing support team to enable the Enterprise license for the product. \
• After 7 days of the initial error, Go to Admin hub > Apps > Apps URL : Change the site's URL to the intended site name.