Overview#
You can integrate Atlassian Jira notifications to automatically create Jira issues for file transfer status changes.
After the integration is complete, an issue is automatically created in the specified Jira project whenever a selected event occurs, such as a transfer being Started, Completed, or Failed.
The entire process consists of two steps: ① Generate a Jira API Token → ② Configure notifications in the product.
Prerequisites#
Before you begin, check the following.
| Item | Description |
|---|---|
| Atlassian Account | An account with permission to create issues in the target project is required. |
| Target Project | Confirm the Jira project and Project Key where issues will be created. |
| Network | Outbound HTTPS (443) communication from the environment where the product is installed to the Jira instance (for example, your-domain.atlassian.net) must be allowed. |
Generate a Jira API Token#
To receive notifications in Jira, generate an API Token from your Atlassian account.
The generated API Token is used together with the account email for Jira authentication.
Step 1. Open the API Token Page#
Go to https://id.atlassian.com/manage-profile/security/api-tokens.
If you signed in with a password or an external account, you may be asked to verify your identity using a one-time code sent by email.

Step 2. Create an API Token#
Click Create API token.
Enter a token name (for example, INNORIX Notifications), select an expiration period (1–365 days), and create the token.
ℹ️ After the expiration date, the token expires and the notification integration stops working. Generate and replace it with a new token before it expires.

Step 3. Copy the API Token#
Click Copy to clipboard to copy the API Token.
ℹ️ An API Token should be treated like a password. Anyone who knows the value can access Jira with that account's permissions, so do not expose it in public repositories or external documents. You cannot view the Token again after closing the creation window, so store it in a secure location. If it is exposed or lost, revoke the existing Token and generate a new one.

Verification#
- ✔ The API Token has been created.
- ✔ The API Token has been copied and stored securely.
Configure Jira Notifications#
Enter the generated API Token and account information in the product's notification settings.
Open the Notifications settings window to display the screen below.

Step 1. Enter the Jira Instance URL#
Enter the Jira site address you use in the Jira Instance URL field.
Example:
https://your-domain.atlassian.netStep 2. Enter Username / Email#
Enter the email address of the Atlassian account that generated the API Token in the Username / Email field.
This account must have permission to create issues in the target project.
Step 3. Enter the API Token#
Paste the copied API Token into the API Token field.
Step 4. Enter the Project Key#
Enter the Project Key of the project where issues will be created in the Project Key field.
Example:
PROJYou can find the Project Key in the project settings or in an existing issue number (for example, PROJ-123).
Step 5. Select Notification Events#
Select the events you want to receive notifications for in the Events field.
You can select multiple events. Jira issues are created only when the selected events occur.
| Event | When It Occurs |
|---|---|
| Started | When a transfer job starts |
| Completed | When a transfer completes successfully |
| Paused | When a transfer is paused |
| Resumed | When a paused transfer resumes |
| Recovered | When a transfer automatically recovers and resumes after an interruption or error |
| Canceled | When a user cancels a transfer |
| Failed | When a transfer fails |
| Skipped | When a specific file is skipped (for example, because it already exists or matches a filter condition) |
Step 6. Save the Settings#
After entering the information, click Add to save the integration.
Verification#
- ✔ The Jira Instance URL has been entered.
- ✔ Username / Email has been entered.
- ✔ The API Token has been entered.
- ✔ The Project Key has been entered.
- ✔ Notification events have been selected.
Verify the Integration#
Verify that the configuration works correctly.
Step 1. Trigger a Test Event#
Run an actual transfer job or trigger one of the selected events.

Step 2. Check the Jira Project#
Verify that a new issue has been created in the specified Jira project.

Verification#
- ✔ An issue has been created in the Jira project.
- ✔ The event that occurred has been recorded correctly.
Setup Complete#
The integration is applied when you save the settings.
Afterward, a new issue is automatically created in the specified Jira project whenever a selected event occurs.
Troubleshooting#
If an issue is not created, check the following.
| Problem | What to Check |
|---|---|
| Issue is not created | Verify that the Jira Instance URL, Username / Email, API Token, and Project Key are entered correctly, including checking for leading/trailing spaces or missing values. |
| Authentication error (401) | Verify that the email matches the account that generated the API Token and that the API Token has not expired. If it has expired, generate a new Token. |
| Permission error (403) | Verify that the account has permission to create issues (Create Issue) in the target project. |
| Project cannot be found | Verify that the Project Key is correct (for example, PROJ). |
| Integration fails in a closed network | Verify that outbound HTTPS (443) communication to the Jira instance is allowed through the firewall or proxy. |