Skip to main content

Who is this article for?

Incydr Professional, Enterprise, Horizon, and Gov F2
Incydr Basic, Advanced, and Gov F1

Find your product plan in the Code42 console on the Account menu.

Instructor, no.

Incydr Professional, Enterprise, Horizon, and Gov F2, yes.

Incydr Basic, Advanced, and Gov F1, yes.

HOME
GETTING STARTED
RELEASE NOTES
FAQs
APIs
SYSTEM STATUS
Code42 Support

Jira configuration for Incydr Flows

Overview

The Incydr Context Flow for Jira automates tasks in Incydr based on information in your Atlassian Jira system. When you add tickets to Jira for offboarding tasks that need to be completed when an employee is about to leave (or has left) the company, the Context Flow automatically adds that employee to the Departing watchlist in Incydr for additional monitoring. This article describes how to configure Jira in preparation for integration with Incydr Flows.

Considerations

Incydr Flows:

  • Are a paid service on some product plans.
  • Are not available in the Code42 federal environment.
  • Require assistance and setup from Code42 Professional Services. Contact your Customer Success Manager (CSM) to engage the Code42 Professional Services team.

Configure Jira

Work with your Jira administrator to complete these configuration tasks in preparation for integration with an Incydr Context Flow:

  1. If you don't already have a dedicated project, use the HR service management template in Jira to create a new project for onboarding and offboarding employees and assign it a 3-character key or identifier.
  2. In that project, verify the following:
    • A field exists in the project for the departing employee's email address. Provide this field's ID to Code42 Professional Services.
      This field can be a new custom field or any existing field that captures the email address for this employee.
    • The Offboarding issue type is associated with the project.
    • The Offboarding issue type includes fields to capture the employee's departure date and email address.
  3. Create a new service account user in Jira for the Context Flow, and create an API token for it.
    Incydr Flows uses this service account and API token to log in to your Jira environment, authenticate the Context Flow, and access information about departing employees. You or your Jira administrator enter this API key into Incydr during your kickoff meeting with Code42 Professional Services.
  4. In the Code42 console, create an API client to use for the Context Flow.
    Incydr Flows uses this client to pass information from Jira to Incydr when an employee offboarding ticket is created in your Jira project.
  5. Provide an email address to use for the workflow to Code42 Professional Services.
    Incydr Flows sends information about any errors that occur to this address.

Jira Context Flow processing

After you configure Jira and integrate it with an Incydr Context Flow, users in Incydr are automatically added to the Departing watchlist based on the offboarding tickets your Human Resources team creates in Jira. Processing completes based on this information flow as follows:

  1. You create a new offboarding ticket in your HR project in Jira.
  2. Incydr Flows accesses that project and its new tickets in Jira. From that information, Incydr Flows:
    • Identifies which employees are involved in the offboarding tasks.
    • Determines if there is a departure date associated with those employees. If not, Incydr emails you to request one.
    • Determines whether those employees have usernames in Incydr. If not, Incydr emails you to add the employees as Incydr users.
  3. If the employee has a username in Incydr, Incydr Flows then completes these tasks:
    • Adds them to the Departing watchlist in Incydr, if not already present.
    • Updates the departure date in their Incydr user profile, if needed.
  • Was this article helpful?