Jira Integration Setup

Spotto can create Jira issues for every recommendation 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.

Overview

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.

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.