| 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 developer!
...
You will need 3 pieces of configuration from the Jira Project Administrator
Configuration | Details | Example | ||
|---|---|---|---|---|
Trigger Url (#1) | This is project-specific. The project administrator can provide this to you from the Koppla admin screen. | |||
Event Source Key (#2) | A project can have multiple event sources. | bh-buaaayfasd2a4qbht_mcsdrho | ||
API Token (#3 | There is a single API Token per project.
| hwdhfjshdfjhsd3SDFFasdd |
...
How to send the data
Each connection data needs to provide 5 items:
Item | Description | Status |
|---|---|---|
Title | This is the title of the remote data and will appear bolded in the Jira issue | Required |
Description | The description of the remote data piece. | Required |
Time | A text string of date (example 2020/12/31). If none is provided - the current date is assumed. | Optional |
Lookup Value | The value that this refers to in the field that the project administrator configured. | Required |
URL | Required |
Once you have the information above, you can trigger a HTTP POST to the trigger url.
...