Installing Released

Released is available for Jira Cloud via the Atlassian Marketplace.

You must have Administer Jira global permission to enable Released in your Jira site.

Learn more about managing global permissions.

Installation via the Marketplace

To install Released via the Atlassian Marketplace, follow these steps:

1. Head over to the Atlassian Marketplace.

2. Click Try it free to initiate the app installation process. Please note that Jira might take a moment to process this request.

Installation from Jira Cloud

To install Released on your Jira Cloud site, follow these steps:

1. Sign in to your Jira Cloud site.

2. Open the Apps menu located in the navigation header bar.

3. Choose Find new apps from the menu options.

4. Search for Released and click on the app item in the results list.

5. Click Try it free to initiate the app installation process. Please note that Jira might take a moment to process this request.

The global Administer Jira permission is required to install Released. See the Jira documentation for details on how to setup the Administer Jira permission.

Accessing Released

Once installed, Released can be accessed via the global Apps menu in the Jira navigation.

Access Released via the Apps menu

Troubleshooting

Error during installation: "We ran into a little trouble. It might just be a hiccup"

If you encounter a prolonged installation process or receive an indefinite error message in Jira, such as "We ran into a little trouble. It might just be a hiccup," there are a few common causes for this issue.

It is typically related to either a missing or invalid payment method or an open quote (account in arrears). It's important to note that even though the Released trial, as well as your Jira trial or plan, may be free, Atlassian requires a valid payment method on file to initiate trials of third-party apps.

If you find yourself stuck in this situation, please don't hesitate to contact us for assistance.

Error loading the app: "Something went wrong"

When loading the app takes a long time and finally results in the above error, a couple of reasons could be the culprit.

1. You access token as expired – In that case simply reloading the page should fix the error.

2. Your firewall might block our domain "released.so" – Although .so is a quite popular top level domain for startups, we've had a couple of customers who had to allow the domain.

If none of the above works for you, please don't hesitate to contact us for assistance.