Jira Integration: Tickets from Recommendations

Overview

Spotto can create Jira issues for recommendations and automatically link them to the right epics. Use this guide to collect the required Jira values and share them securely so the Spotto team can enable the connection on your behalf.

Other ticketing integrations

Spotto also supports creating tickets in Halo and ConnectWise Manage. Each company can have one active ticketing provider at a time.

When the integration is configured, Spotto will:

• Raise Jira issues that match the recommendation category (Cost, Performance, Reliability, Security, Compliance, Operational Excellence).
• Apply the correct project and epic mapping for each category.
• Authenticate using a designated Jira user with an API token that remains encrypted within Spotto.

Collecting the correct identifiers up front ensures we can turn on the integration without additional back-and-forth.

Prerequisites

• Jira administrator or project administrator permissions to view project settings and epics.
• Access to the Atlassian account that will authenticate the integration.

Information to Collect

Step 1: Record the Jira Site URL

• Format: https://your-company.atlassian.net
• Confirm by opening Jira in your browser and copying the base domain (no trailing slash).

Step 2: Identify the Project Key Mapping

• Provide the default Jira project key for new Spotto tasks.
• If you use separate projects per recommendation category, list each override (for example, projectKeyCost = COST, projectKeySecurity = SEC).
• Where to find: in Jira, go to Project settings → Details → Key.

Step 3: Identify the Epic Key Mapping

• Supply the default epic issue key that Spotto should link recommendations to.
• Optional: include category-specific epic overrides, such as epicKeyCost = COST-21.
• Where to find: open the epic in Jira—copy the issue key from the header (for example, COST-42).

Step 4: Confirm the Jira User Email

• Share the Atlassian account email that will authenticate API calls (must have access to the target projects/epics).

Step 5: Generate an API Token

• Visit https://id.atlassian.com/manage-profile/security/api-tokens.
• Click Create API token, name it Spotto Integration, and copy the generated token.
• Store the token securely; Spotto encrypts it before saving.

Protect the API Token

Jira API tokens grant the same access as the user account. Treat the token like a password and send it only through the secure channel agreed with Spotto.

Step 6: Decide on useSameProjectKeyForAllCategories

• Set to true when the default project key covers every category.
• Set to false when you provide category-specific project keys.

Need multiple projects or epics?

List every override explicitly. Spotto applies the mappings automatically per recommendation category, reducing triage work for your engineering teams.

Integration Properties Spotto Will Configure

When you submit the details, Spotto populates these fields:

• siteUrl
• email
• projectKey
• epicKey
• projectKey{Category} and epicKey{Category} overrides (Cost, Performance, Reliability, Security, Compliance, OperationalExcellence)
• useSameProjectKeyForAllCategories
• API token (encrypted at rest)

Category	Project Key	Epic Key
Default (all categories)	projectKey	epicKey
Cost	projectKeyCost (optional)	epicKeyCost (optional)
Performance	projectKeyPerformance (optional)	epicKeyPerformance (optional)
Reliability	projectKeyReliability (optional)	epicKeyReliability (optional)
Security	projectKeySecurity (optional)	epicKeySecurity (optional)
Compliance	projectKeyCompliance (optional)	epicKeyCompliance (optional)
Operational Excellence	projectKeyOperationalExcellence (optional)	epicKeyOperationalExcellence (optional)

Sharing the Information

Send the collected values through the secure channel designated by Spotto (encrypted email, shared vault, or ticket). Avoid pasting secrets into chat platforms without encryption.

Validation

Once Spotto confirms the Jira integration is enabled, validate it with a single end-to-end test:

1. Ask the Spotto team to create a test issue in your default projectKey.
2. Confirm the issue is linked to the expected epic (epicKey) and appears in the correct project.
3. If you use category-specific overrides, repeat the test for at least one overridden category to confirm mapping works as intended.

Troubleshooting

Jira issue creation isn’t working after setup

What you're seeing: Spotto can’t create issues or issues don’t appear in the expected project/epic. Likely causes:

• API token belongs to a user without permission to create issues in the target project.
• Incorrect projectKey and/or epicKey mapping (including category overrides).
• The Jira Site URL includes the wrong domain or an extra path segment. How to fix:

1. Re-check the Site URL is exactly https://<company>.atlassian.net (no trailing paths).
2. Confirm the Jira user can create issues in the target project and can view/link to the target epic.
3. Validate the projectKey and epicKey values by opening the Jira project/epic and copying the keys from the UI.

Spotto reports an authentication error

What you're seeing: The integration fails to authenticate with Jira. Likely causes:

• API token was copied incorrectly or has been revoked.
• The email address doesn’t match the Atlassian account that owns the token. How to fix:

1. Generate a new token and resend it through the secure channel.
2. Confirm the email address is the same Atlassian account used to create the token.

Need Help?

If you are unsure where to find a field or want a walkthrough of the Jira UI, contact the Spotto team via your Customer Success Manager or Contact Us. We can screen-share to confirm the configuration before you transmit any credentials.