​
Jira Integration

Connect Overcut to your Jira Cloud workspace to seamlessly integrate issue management into your workflows. Once connected, agents can discover your Jira projects and work with issues directly.

​
What You Can Do

With Jira connected, Overcut agents can:
  • View Projects: See all Jira projects you have access to
  • Create Issues: Create new tickets with descriptions, assignees, and labels
  • Update Issues: Modify existing tickets and change their status
  • Add Comments: Leave comments on issues with rich text formatting
  • Track Changes: Receive notifications when issues are updated
  • Search Issues: Find specific tickets using JQL queries

​
Prerequisites

  • An Atlassian Jira Cloud workspace
  • Admin permissions to install apps in your Jira instance
  • An active Overcut workspace

​
Setup

1

Start Jira Connection

In your Overcut workspace, go to Settings → Integrations → Git & Ticket and click Connect Jira.
2

Install the Overcut App in Jira

Click Install Overcut App to be redirected to your Jira instance. Install the app and grant the necessary permissions. If you’ve already installed the app, click I’ve Installed the App to proceed.
3

Complete the Setup

After installing the app, you’ll be prompted to enter your Jira site domain (e.g., my-org.atlassian.net). Enter your domain and click Complete Install to finalize the connection.

​
Using Jira in Your Workflows

Once connected, Jira projects will appear as available sources when you:
  • Add a Source to a workflow
  • Configure a Trigger that monitors projects
  • Set up Actions that work with tickets

​
Example Workflows

  • Bug Triage: Automatically create Jira tickets when bugs are detected in code
  • Feature Requests: Convert GitHub issues to Jira tickets for project tracking
  • Status Updates: Keep Jira tickets updated with latest development progress
  • Release Management: Track all issues related to a specific release
For workflows that need to automatically identify which code repositories are most relevant to Jira tickets, consider using the repo.identify action. This action uses AI-powered analysis and repository correlations to determine the best repositories to work with for each ticket. Learn more in our Repository Mapping guide.

​
Working with Issues

​
Creating Tickets

Agents can create new Jira issues with:
  • Summary and description
  • Assignee (if specified)
  • Labels and priority
  • Project and issue type

​
Updating Tickets

Agents can modify existing issues by:
  • Updating fields like summary or description
  • Changing assignees or labels
  • Transitioning between statuses (e.g., “In Progress” → “Done”)
  • Adding comments with context

​
Finding Issues

Search for specific tickets using:
  • Project key (e.g., “PROJ-123”)
  • JQL queries for complex searches
  • Status filters (open, closed, in progress)
  • Assignee or label filters

​
Permissions

The Overcut app requests the following permissions in Jira:
  • Read access to projects, issues, and comments
  • Write access to create and update issues
  • Permission to add comments to existing issues
These permissions allow Overcut to fully integrate with your Jira workflow while maintaining security.

​
Troubleshooting

​
Connection Issues

  • Ensure you have admin permissions in your Jira workspace
  • Try disconnecting and reconnecting the integration
  • Check that your Jira instance is accessible

​
Permission Errors

  • Verify the Overcut app has the necessary permissions in Jira
  • Check that you’re trying to access projects you have access to
  • Ensure your Jira user account has appropriate permissions

​
Missing Projects

  • The integration only shows projects you have access to
  • Check your Jira user permissions for specific projects
  • Verify the project keys are correctly configured

​
Getting Help

If you encounter issues with the Jira integration:
  1. Check the troubleshooting section above
  2. Review your Jira permissions and project access
  3. Contact Overcut support with specific error messages
  4. Ensure your Jira instance is running and accessible