| Note |
|---|
Important update: Koppla will no longer operate after April 15, 2024.After this date, Atlassian will delete your stored Koppla data from their Forge storage platform. You may uninstall and delete the application from your instance at any time before this date. We have loved developing and working on Koppla and supporting users in bringing their external data into their Jira issues. After three years of journey, we decided to sunset Koppla and focus on improving our growing products. Thank you for choosing Koppla and being a loyal customer. If you have any questions or concerns, we are always here to help. Please feel free to reach out to us. |
This page is a guide for your project administrator!
A project administrator is required to configure event sources for a Jira project. Each project has its own separate configuration.
...
The trigger url is used to send data to Koppla. For more information about this - please see Submitting data to Koppla Submit Event Source Data.
The API token
The api token is the credential to submit data to Koppla. It is project specific and once generated it is not visible in the ui again (copy the token and store it in a safe place). Anyone that has this token is able to submit data to your project.
...
From here you’re able to:
Set the event source name
Set the base url for the event source.
Select an icon for the event source
Select the field that the value will be looked up against. Note: Changing the field does not change any of the data that has been submitted.
Restrict access to the event source by Jira user groups. The event source (and the associated data) will only be shown for the users that are listed here.
Sample code
To assist in sending data to Koppla, you can click on the “code” button and see a sample set of code that will allow you to submit data to this particular event source.
...