Corma
Corma
Docs
  • Docs
  • Changelog
  • Feature requests
    • General information about integrations
    • Identity Providers
    • Finance and Accounting
    • Human Resources
    • SaaS tools
    • ITSM tools
      • Siit
      • Jira

Jira

Corma can automatically create Jira tickets whenever a manual task is created in Corma so that all your tickets still live in your main ticketing system. This document presents how to configure this feature and how it works.

How to set up the Jira ticket creation

Step 1 - Connect Atlassian

First you'll need to make sure the Atlassian integration is connected in your Corma workspace. For this go to Data sources > Atlassian.

You can follow this tutorial to see how to connect Atlassian to Corma.

Step 2 - Configure the Atlassian integration settings

Once the integration is connected, you should automatically see a popup asking whether you'd like Corma to create Jira tickets when a manual task is created in Corma.

You just need to check the Create ticket checkbox and then you can choose:

  • Jira Project in which tickets should be created

  • Issue type (for instance "Corma")

Don't worry if you had already connected Atlassian and left that unchecked; you just need to click on Manage > Settings on the Atlassian integration card.

Step 3 - Validate

Validate your settings and you're all set! Corma will now create a ticket in the selected Jira project every time a manual task was logged in Corma.

How does it work?

Whenever a manual task in Corma is created, for instance when a license (de)provisioning cannot be performed via API or Agent, or when an automated action fails, in addition to the Task in Corma, a Jira ticket will also be created.

The following information will be added to the ticket for context:

  • Title = {Task type} - {App Name} - User {Username}

  • Description = more context about the user targeted and the license targeted by the task

  • Assignee = Task assignee in Corma (either App or Access owner)

  • Labels = based on the context (e.g. Offboarding)

Known limitations:

  • Tickets in Corma and Jira tickets are not synced bi-directionally. If a ticket in Corma is marked as completed, the Jira ticket will not be automatically completed. Same thing the other way around

  • Fields inserted in the Jira ticket cannot be customized

  • Jira tickets are either created systematically or not. You cannot configure in Corma that tickets are created only for specific apps

  • You cannot configure Corma to create tickets in more than 1 project in Jira

Create Jira tickets from the Workflow Builder

In addition to this automatic ticket creation for manual tasks, you can also add a "Create a Jira ticket" action to any custom workflow in the Workflow Builder.

A common example is a pre-offboarding reminder: trigger the workflow 7 days before a user's contract end date, and have it create a Jira ticket listing all the tools that user has access to that do not have automated provisioning/SCIM support, so IT knows exactly which accounts still need to be manually deprovisioned before the employee leaves.

Was this helpful?