Skip to main content
Connect your team’s Jira Cloud site using an Atlassian service account. Corelayer uses organization-managed OAuth credentials rather than an employee’s personal API token or email address.

​
Prerequisites

  • A Jira Cloud site, such as https://your-team.atlassian.net
  • An Atlassian organization administrator who can manage service accounts
  • A service account with Jira access
  • Browse Projects and Create Issues permissions in each destination project
  • Permission to manage integrations in the selected Corelayer group

​
Create the OAuth Credentials

In Atlassian Administration, select your organization and open Directory → Service accounts. Select your service account, choose Create credentials → OAuth 2.0, and grant these scopes:
  • read:jira-work
  • read:jira-user
  • write:jira-work
Save the generated client ID and client secret in your password manager. See Atlassian’s service-account OAuth guide for account requirements and credential creation. The scopes and project permissions are both required. Adding a scope does not give the service account access to a project.

​
Connect Jira

  1. Select the Corelayer group that should own the connection.
  2. Open Integrations, click Add Integration, and select Jira.
  3. Enter the Site URL, Client ID, and Client secret.
  4. Click Verify and connect.
Verification checks the Jira service account. It does not create a test ticket or verify Create Issues access in every project.

​
File a Corelayer Issue to Jira

Ticket filing requires a Corelayer runtime version with Jira ticket creation enabled. Connecting Jira alone does not enable ticket filing on an older customer runtime.
  1. Open the Corelayer issue and choose File to Jira from its actions menu.
  2. Choose a Jira connection if the group has more than one.
  3. Select a project and a standard issue type. Subtasks are not supported.
  4. Complete the required fields shown for that project and issue type.
  5. Click Create Issue after the project requirements finish loading.
Corelayer creates a Jira issue with the investigation title, summary, root cause, next steps, and a link back to the Corelayer issue. The Corelayer issue stays open. The linked Jira key replaces the filing action, so you can open the existing ticket. The form supports common text, number, date, and option fields. If Jira requires a field the form cannot handle, Corelayer names that field and provides Open Jira; creation from Corelayer stays disabled. Groups with Linear see File to Linear; groups with Jira see File to Jira. Both actions are available when both providers are connected, and the same Corelayer issue can retain a link to each provider.

​
If Creation Is Interrupted

If Jira may have received the request, use Check status first. If a ticket exists but was not linked, enter its key and select Verify and link. Corelayer checks that the ticket belongs to the original creation request before linking it. An unrelated ticket cannot be attached through this recovery flow. Do not create a second ticket to resolve an uncertain result. Contact Corelayer support if verification cannot resolve it. A request confirmed not to have been sent can resume through the normal creation form.

​
Manage the Connection

Open the Jira integration’s Settings tab.
  • Test connection: Choose Test connection from the three-dot menu to verify the saved credentials.
  • Rotate credentials: Create a new Atlassian OAuth credential, then choose Edit credentials from the three-dot menu and save the new client ID and secret. Verify the replacement before revoking the previous credential in Atlassian.
  • Change sites: Add a separate Jira integration; credential editing keeps the existing site.
  • Disconnect: Click Disconnect and confirm. Revoke the credential in Atlassian separately if it is no longer needed.
If a concurrent administrator update causes a conflict, reload the connection, review your preserved draft, and save again.

​
BYOC Deployments

The same setup is supported on AWS and GCP customer runtimes. The deployment needs Atlassian credential-storage permissions and outbound HTTPS access to auth.atlassian.com, api.atlassian.com, and your site’s *.atlassian.net hostname. Jira ticket filing also requires a runtime version that supports the feature. Ask your deployment administrator or Corelayer support to check these prerequisites if setup or ticket filing is unavailable.

​
Troubleshooting

  • Connected, but no projects appear: Confirm Jira access and Browse Projects/Create Issues permissions for the service account.
  • Creation reports missing permissions: Check write:jira-work and the destination project’s permission scheme. Connection testing alone does not prove ticket-creation access.
  • Required fields fail validation: Review the highlighted fields. Jira requirements are checked again when you submit.
  • Reconnect required: Replace the saved credential through Edit credentials.
To connect Confluence as well, follow the Confluence integration guide.