Jira Integration
'Connect Jira to Supervity, authorize access, and use Jira data and actions in operators and workflows.'
This guide explains how to connect Jira to Supervity, what data is available after connection, how operators can use Jira data and actions within workflows, and how to remove the integration when needed.
Overview
The Supervity Jira integration allows your workspace to securely connect Jira as a governed platform capability.
Once connected, operators and workflows can use Jira data and actions to automate software development lifecycles, manage issues and tasks, organize projects and sprints, track work hours, and coordinate collaboration across systems.
With the Jira integration, Supervity can:
- Search for issues using JQL (Jira Query Language)
- Create, retrieve, update, delete, assign, and transition issues
- Add, update, retrieve, and delete issue comments
- Create, list, update, and delete projects
- Create, list, update, and delete sprints for Scrum boards
- Create, list, retrieve, and delete agile boards
- Add, list, and delete issue attachments
- Retrieve user profiles and search for workspace users
- Create, list, update, and delete issue worklogs for tracking time
- Use Jira issues, sprints, and project data as context for operators
- Trigger workflows based on Jira events and project activity
All Jira access is governed through Supervity's security, permissions, and audit controls.
Prerequisites
Before connecting Jira, ensure you have:
- An active Supervity workspace
- An Atlassian account with access to Jira Cloud
- Permission to authorize applications on your Atlassian account
- Access to the Jira site, projects, boards, and sprints you want to manage
Depending on your organization's Jira settings, some operations (such as creating projects, deleting projects, or managing global configurations) may require project administrator or site administrator-level permissions.
Adding the Jira Integration
Follow these steps to connect Jira to Supervity. If you encounter any issues during setup, refer to the Troubleshooting section of this guide.
Step 1: Open Integrations
- Log in to Supervity.
- From the left navigation bar, click the Integrations icon.
This opens the Integrations page, where all available integrations are listed. Connected integrations and available integrations can both be managed from this page.
Step 2: Select Jira
- Locate Jira in the available integrations list.
- Click Connect.
Step 3: Authorize Access
You will be redirected to Atlassian's secure authorization page.
Review the requested permissions and click Accept to grant Supervity access to your Jira account.
- Supervity uses Atlassian's standard OAuth 2.0 authorization flow.
- Your Atlassian password is never shared with or stored by Supervity.
Step 4: Complete Connection
After authorization, you will be redirected back to Supervity.
The Jira integration will appear as Connected on the Integrations page. Your workspace can now securely access Jira capabilities according to the permissions granted.
Having trouble? See the Troubleshooting section for step-by-step help with common setup issues.
How Jira Works in Supervity
After connection, Jira becomes available as a governed platform tool.
Operators can use Jira capabilities when planning and executing tasks, while workflows can automate actions using Jira data.
Common use cases include:
- Creating bug reports and task tickets automatically
- Syncing issue updates and comments with support desks or CRM systems
- Managing project backlogs, boards, and sprints programmatically
- Extracting insights and progress reports from sprint history and JQL searches
- Logging developer work hours automatically in Jira worklogs
- Handling file attachments linked to development tickets
Using Jira in Operators
Connected Jira capabilities become available to operators automatically. Operators determine when Jira data or actions are required to complete a task and execute accordingly, while remaining governed by workspace permissions, security controls, and approval policies.
What Operators Can Do with Jira
Operators can perform the following actions using Jira:
- Search for issues using JQL queries
- Create, update, transition, assign, and delete issues
- Create, retrieve, update, and delete issue comments
- Create, list, update, and delete projects
- Create, list, update, and delete sprints on boards
- Create, list, and delete boards
- Upload, list, and delete issue attachments
- Retrieve user profiles and search for users
- Create, list, update, and delete worklogs on issues
- Combine Jira actions with other connected applications for end-to-end automation
Typical Operator Use Cases
| Use Case | Example |
|---|---|
| Issue Management | Create and assign task or bug tickets automatically |
| Comment Synchronization | Sync conversation history between Jira comments and external tools |
| Project Administration | Set up new projects, templates, and lead settings |
| Sprint Management | Schedule and update sprints for agile development planning |
| Agile Boards | Create dedicated boards to track project phases |
| Attachment Processing | Upload reports or screenshots directly to development issues |
| Time Tracking | Log and update work time spent on task execution |
| Progress Reporting | Query and summarize sprint progress using JQL searches |
Features & Prerequisites
For each Jira capability available in Supervity, the following describes the use case and the prerequisites required before use.
List Issues
Use Case: Search for issues in Jira using Jira Query Language (JQL). Useful for retrieving list views, tracking sprint backlogs, and auditing ticket statuses.
Prerequisites:
- Jira account connected to Supervity
- Valid JQL query string
Get Issue
Use Case: Retrieve details for a specific issue, including summary, description, assignee, status, and custom fields.
Prerequisites:
- Jira account connected to Supervity
- Ticket ID or issue key (e.g., "PROJ-123") must exist and be accessible
Create Issue
Use Case: Automate the creation of a new issue (such as a bug, task, story, or epic) in a specified project.
Prerequisites:
- Jira account connected to Supervity
- Target project key and valid issue type name (e.g., "Bug", "Task") must exist
- Project write permissions enabled on the account
Update Issue
Use Case: Programmatically modify fields (such as summary, description, priority, or custom fields) on an existing issue.
Prerequisites:
- Jira account connected to Supervity
- Issue must exist and account must have edit permissions for the target issue
Delete Issue
Use Case: Remove an issue from Jira when it is no longer required or was created in error.
Prerequisites:
- Jira account connected to Supervity
- Issue must exist and account must have delete permissions in the target project
Assign Issue
Use Case: Assign a specific issue to a user by providing their account identifier.
Prerequisites:
- Jira account connected to Supervity
- Issue must exist and assignee's Atlassian account ID must be valid
- Permission to assign issues within the project
Transition Issue
Use Case: Transition an issue through workflow statuses (e.g., moving from "To Do" to "In Progress" or "Done").
Prerequisites:
- Jira account connected to Supervity
- Target transition ID or name must be valid for the current issue status
- Permission to transition issues in the workflow
List Comments
Use Case: Retrieve comments associated with a specific Jira issue to audit activity or sync conversations.
Prerequisites:
- Jira account connected to Supervity
- Issue must exist and be accessible
Get Comment
Use Case: Retrieve the details of a specific comment on a Jira issue.
Prerequisites:
- Jira account connected to Supervity
- Comment ID and associated issue must exist
Create Comment
Use Case: Add a new comment to an issue to update team members or log updates.
Prerequisites:
- Jira account connected to Supervity
- Target issue must exist and comment body content must be provided
- Add-comment permissions enabled on the project
Update Comment
Use Case: Edit the body text of a previously submitted comment.
Prerequisites:
- Jira account connected to Supervity
- Target comment must exist and have been authored by (or editable by) the connected account
Delete Comment
Use Case: Delete a comment from a Jira issue.
Prerequisites:
- Jira account connected to Supervity
- Comment must exist and the account must have delete-comment permissions
List Projects
Use Case: Retrieve list details about all projects available on the authorized Jira site.
Prerequisites:
- Jira account connected to Supervity
Get Project
Use Case: Retrieve detailed information (such as project lead, categories, components, and key) for a specific project.
Prerequisites:
- Jira account connected to Supervity
- Target project ID or project key must exist
Create Project
Use Case: Automate the setup of a new classic or next-gen project with templates, keys, and assignees.
Prerequisites:
- Jira account connected to Supervity
- Unique project key, project name, project type, and lead account ID must be valid
- Administrator-level permissions on the Jira site
Update Project
Use Case: Modify project metadata such as project name, description, category, or lead.
Prerequisites:
- Jira account connected to Supervity
- Project must exist and account must have project administration rights
Delete Project
Use Case: Remove a project and all its issues from the Jira site.
Prerequisites:
- Jira account connected to Supervity
- Project must exist
- Site administrator permissions on Jira Cloud
List Sprints
Use Case: Get all sprints configured for a specific Agile board. Useful for planning cycles and milestone auditing.
Prerequisites:
- Jira account connected to Supervity
- Board ID must exist
Get Sprint
Use Case: Retrieve details of a specific sprint including name, status, start date, and end date.
Prerequisites:
- Jira account connected to Supervity
- Sprint ID must exist
Create Sprint
Use Case: Programmatically schedule a new sprint under a specific board.
Prerequisites:
- Jira account connected to Supervity
- Target board ID must exist and sprint name must be provided
- Project manage-sprints permissions enabled
Update Sprint
Use Case: Modify sprint details or change its state (e.g., starting a sprint or marking it complete).
Prerequisites:
- Jira account connected to Supervity
- Sprint must exist and have valid date formats or state updates
- Project manage-sprints permissions enabled
Delete Sprint
Use Case: Delete a scheduled sprint that is no longer required.
Prerequisites:
- Jira account connected to Supervity
- Sprint must exist and be in a deletable state (e.g., not completed)
- Project manage-sprints permissions enabled
List Boards
Use Case: Retrieve a list of all Scrum and Kanban boards configured on the Jira site.
Prerequisites:
- Jira account connected to Supervity
Get Board
Use Case: Retrieve configuration, location, type, and filter details for a specific board.
Prerequisites:
- Jira account connected to Supervity
- Board ID must exist
Create Board
Use Case: Programmatically set up a new Scrum or Kanban board mapped to specific project keys.
Prerequisites:
- Jira account connected to Supervity
- Board name, type, and valid project filter ID must be provided
- Permission to create boards on the site
Delete Board
Use Case: Remove an Agile board from the site.
Prerequisites:
- Jira account connected to Supervity
- Board must exist and account must have board deletion rights
List Attachments
Use Case: Retrieve information about all files attached to a specific issue.
Prerequisites:
- Jira account connected to Supervity
- Target issue must exist
Add Attachment
Use Case: Upload and link a file attachment directly to a Jira issue.
Prerequisites:
- Jira account connected to Supervity
- Target issue must exist and file payload must be provided
- Project permissions must allow attachment uploads
Delete Attachment
Use Case: Delete an attached file from a Jira issue.
Prerequisites:
- Jira account connected to Supervity
- Attachment ID must exist and account must have permission to delete attachments
Get Current User
Use Case: Retrieve details about the authenticated user's account for auditing or identification.
Prerequisites:
- Jira account connected to Supervity
Search Users
Use Case: Find Atlassian users by query strings matching their name or email. Useful for ticket assignment routing.
Prerequisites:
- Jira account connected to Supervity
- Query string must be provided
List Worklogs
Use Case: Retrieve work logs submitted for a specific issue. Useful for resource auditing and billing workflows.
Prerequisites:
- Jira account connected to Supervity
- Target issue must exist
Add Worklog
Use Case: Log work time (in seconds or hours) spent on a specific Jira issue along with description notes.
Prerequisites:
- Jira account connected to Supervity
- Target issue must exist and worklog duration/comment must be provided
- Project permissions must allow work logging
Update Worklog
Use Case: Edit the logged time or comment details of an existing work log.
Prerequisites:
- Jira account connected to Supervity
- Worklog ID must exist and be editable by the connected account
Delete Worklog
Use Case: Delete a work log from an issue.
Prerequisites:
- Jira account connected to Supervity
- Worklog ID must exist and account must have delete-worklog permissions
Permissions Requested
Supervity only requests the permissions required for enabled Jira capabilities.
Depending on the features used in your workspace, permissions may include:
| Permission Type | Purpose |
|---|---|
| User Information | Associate Jira data with the authorized Atlassian account |
| Read Access | Search issues, list comments, and retrieve project details |
| Write Access | Create and edit issues, transition workflows, and add comments |
| Project Administration | Create, manage, and delete projects |
| Board & Sprint Management | Manage boards and configure sprints for Scrum boards |
| Attachments | Upload and delete files linked to issues |
| Worklogs | Log and manage work log times on tickets |
Supervity follows least-privilege principles and only accesses data necessary to provide requested functionality.
Authentication & Security
The Jira integration uses OAuth 2.0 authentication.
Security controls include:
- Encrypted credential storage (AES-256)
- Scoped access policies
- Token refresh and rotation support
- Immediate revocation capabilities
- Workspace-level governance controls
- Complete audit logging
- TLS 1.3 for all connection pipelines
All Jira access remains subject to Supervity security policies and role-based permissions.
Managing the Integration
View Connection Status
From the left navigation bar, click the Integrations icon.
For Jira you can view:
- Connection status
- Granted permission categories
- Last usage information
- Associated workflows and operators
Reconnect Jira
If Jira authorization expires or security policies change:
- Open the Integrations page from the left navigation bar.
- Select Jira.
- Click Reconnect.
- Complete authorization again.
Existing workflows and operators do not need to be recreated.
Removing the Jira Integration
You can remove the Jira connection from your Supervity workspace at any time directly from within the Supervity platform.
Steps to Remove
- Log in to Supervity.
- From the left navigation bar, click the Integrations icon.
- Locate and select Jira from the integrations list.
- Click Disconnect.
- Confirm the action when prompted.
Implications of Removal
Once removed:
- Supervity immediately loses all access to your Jira account and associated data
- No new Jira data will be retrieved or modified after removal
- All active Jira connections within your Supervity workspace are terminated
- Scheduled or active workflows that depend on Jira will stop executing
- Jira-dependent workflow steps will fail safely with clear error messages
- Existing workflow definitions within Supervity are not deleted — only the active connection is terminated
- Historical execution logs remain available for auditing purposes
Disconnecting Jira does not delete workflow definitions, operators, or previously generated outputs.
How Your Data Is Handled After Removal
Data Handling on Removal:
- Supervity immediately loses access to your Jira account upon removal
- No new Jira files or data will be collected or processed after disconnection
- Temporary files processed during workflow execution are deleted after execution completes
- Jira access tokens and all account-related data are permanently deleted from Supervity's platform within 15 minutes of disconnection — no background access continues after removal
Auditing & Observability
All Jira activity performed through Supervity is logged.
Audit records include:
- Which operator requested access
- Which workflow executed the action
- Timestamp of execution
- Success or failure status
- Relevant inputs and outputs (sensitive values are redacted)
This supports compliance, troubleshooting, governance, and operational visibility.
Troubleshooting
If you encounter issues at any stage, refer to the steps below. For issues not covered here, contact the Supervity support team.
Authorization Failed During Setup
Likely Cause: Incorrect Atlassian account used, or corporate tenant policies restricting third-party applications.
Resolution:
- Ensure you are signed in to the correct Atlassian/Jira account.
- Verify with your organization's IT administrator that your account is allowed to authorize third-party applications.
- Return to Supervity → Integrations → Jira and click Connect to retry.
- If the issue persists, contact your IT administrator.
Jira Shows Connected but Data Is Missing
Likely Cause: Project permissions are restricted, or you are trying to access resources from a site/project where the connected account lacks permissions.
Resolution:
- Verify that the projects or issues exist in the connected Jira instance.
- Confirm the account connected to Supervity has read/write permissions for the requested projects or boards.
- Reconnect the integration via Integrations → Jira → Reconnect to refresh permissions.
Connection Expired or Token Invalid
Likely Cause: Atlassian security policies may force token expiration or revocation.
Resolution:
- Go to Integrations → Jira → Reconnect.
- Complete the Atlassian authorization flow again.
- Existing workflows do not need to be reconfigured after reconnection.
Workflow Cannot Access Jira
Likely Cause: Jira may have been disconnected, or workspace governance policies restrict access.
Resolution:
- Confirm Jira is still connected under the Integrations page.
- Verify the workflow has permission to use Jira within your workspace governance settings.
- Check that workspace policies allow Jira execution for the relevant operators or workflows.
Creating Sprints or Boards Fails
Likely Cause: Target board ID is invalid, or the project filter is missing, or the user is not a project manager.
Resolution:
- Verify the project or board ID exists on the site.
- Ensure you have the 'Manage Sprints' or 'Administer Projects' permission in Jira.
- Check if the project is a Scrum project (Sprint operations do not apply to Kanban projects).
Attachment Upload Fails
Likely Cause: Invalid file type, file size exceeding Jira instance limits, or missing upload permissions.
Resolution:
- Ensure that files do not exceed the file upload limits set by your Jira administrator.
- Verify that your Atlassian account has permission to attach files to issues in the target project.
Frequently Asked Questions
Q: Is my Atlassian password shared with or stored by Supervity?
No. Supervity uses Atlassian's standard OAuth 2.0 authorization flow. Your Atlassian password is never shared with or stored by Supervity. Only scoped access tokens are stored, and these are encrypted at rest using AES-256.
Q: Can I use this integration with Jira Server or Data Center?
No. This integration is designed specifically for Jira Cloud. Self-hosted Jira Server or Jira Data Center deployments are not supported by this integration.
Q: Will I need to reconfigure my workflows after reconnecting Jira?
No. If you reconnect Jira due to token expiry or permission updates, existing workflow definitions and operators do not need to be recreated or reconfigured.
Q: What happens to my workflows if I disconnect or remove Jira?
Workflow definitions are not deleted when Jira is disconnected or removed. However, any workflow steps that depend on Jira will fail safely with clear error messages until Jira is reconnected.
Q: How do I authorize the Supervity Jira integration?
Log in to Supervity at Supervity, navigate to the Integrations page from the left navigation bar, locate Jira, and click Connect. You will be redirected to Atlassian's authorization page where you can review and approve the requested permissions. After authorization, you will be redirected back to Supervity automatically. See the Adding the Jira Integration section above for full step-by-step instructions.
Q: Can I limit which projects Supervity can access?
Supervity requests only the permissions required for enabled capabilities, following least-privilege principles. You can review all requested access types during the Atlassian OAuth authorization step before approving.
Q: Who do I contact if I have an issue with the integration?
Contact the Supervity support team. See the Support section below for full contact details, support hours, and SLA information.
Support
If you need assistance with the Jira integration, visit the Support page.
Support Hours
- Monday to Friday, 9:00 AM – 6:00 PM IST
- Requests submitted outside business hours will be addressed on the next business day
First Response SLA
- All support requests receive an initial response within 24 business hours
Contact Information
| Contact Type | Details |
|---|---|
| Support | Support & Contact |
| Sales Inquiries | sales@supervity.ai |
| Contact Form | https://www.supervity.ai/contact-us |
| Website | https://www.supervity.ai |
| Privacy Policy | https://supervity.ai/privacy-policy |
| Terms of Service | https://www.supervity.ai/terms-of-service |
| Acceptable Use Policy | https://supervity.ai/acceptable-use-policy |
When Contacting Support, Please Provide
- Workspace name
- Atlassian account email used for authorization
- Relevant workflow or operator information
- Error messages or screenshots when available
This helps the support team investigate and resolve issues more quickly.