Jira User Story Integration

This page explains how to integrate Jira with Revvy, manage connected projects, and configure status mappings between Jira issues and Salesforce environments.

The Settings tab in Revvy allows you to connect external systems for user story management. With Jira integration, you can automatically sync tasks, requirements, and development artifacts across Jira projects and Revvy pipelines.

Once configured, Jira projects and their statuses appear directly in Revvy, allowing for end-to-end visibility and automation.

Adding a Jira Integration

1. Navigate to Settings → User stories integration.

2. Click + Add Integration.

3. In the Add integration modal, provide the following details:

   • Name (e.g., Jira)

   • Service type (select Jira)

   • Authorization (Basic Auth)

   • Username

   • Password/Token

   • Instance URL (e.g., https://yourcompany.atlassian.net)

4. Click Add integration to save.

Once added, the Jira integration will appear in the Integrations list, showing its connection status.

Managing Integrations

When a Jira integration is added, you will see:

• Integration name (e.g., Jira)

• Service type (Jira)

• Instance URL

• Status (e.g., Connected ✅)

Actions available:

• See projects — View Jira projects linked to this integration.

• Delete (recycle bin icon) — Remove the integration.

Managing Jira Projects

1. Click See projects on the Jira integration.

2. A list of Jira projects appears (e.g., Flosum, My Kanban Project).

3. For each project, you can:

   • Configure project — Map statuses and environments.

   • Delete project — Remove the project from Revvy.

4. You can also click + Add Project to connect additional Jira projects.

Configuring Project Status Mapping

When configuring a project, you can map Jira issue statuses to Revvy connections:

1. Select a source connection (e.g., Source Sandbox).

2. Select a target connection (e.g., Target Sandbox).

3. Assign status values such as In Progress, Done, etc.

4. Click Save configuration.

Example: For the Flosum project:

• Source Sandbox → In Progress

• Target Sandbox → Done

This ensures that when Jira issues move across statuses, Revvy updates linked environments accordingly.

Best Practices

• Use distinct names for integrations if connecting multiple Jira instances.

• Always map statuses to reflect your team’s actual development workflow (e.g., In Progress → QA → Done).

• Delete unused projects and integrations to keep the environment clean.

• Validate that credentials have the correct API and project access before saving the integration.