Sapling’s Jira integration allows tasks to be sent from Sapling to a specific Jira project, with the task status, description and title then kept in sync between the two systems.
How It Works
Setting up the Integration
Data Flow Overview
Once you have the Jira integration enabled, Admin and Account Owners can confirm which Tasks should be sent to become Jira tickets.
This is done on the Workflows tab in Sapling. When creating a new task (or modifying an existing task) - change the Assigned to Jira. Once assigned to Jira, you will see the Jira icon as the task owner of the task. This means that when we assign the task, it will be sent to Jira. Tasks can be assigned in the onboarding or offboarding flows, or the Tasks Page.
The task sent to Jira contains the following:
Name of the Task with the New Hire Name appended to the Task
Description of the Task
Due Date of the Task.
When Tasks are completed in Jira (as the specified status in the Jira project), the Tasks in Sapling will automatically be updated.
Key Factors to be aware of
Jira Cloud vs On-premise
Sapling only integrates with Jira Cloud.
Changes in Tasks
Updating the name and description in Sapling will update the name of the description o the Jira ticket in Jira.
Due date changes in Sapling, will not update the field in Jira.
Tokens in Tasks
If a token is not filled out when the task is assigned to Jira, it will come over as a blank field.
Updating the token in Sapling, will not update the field in Jira.
Due Dates Management
To manage due dates through Sapling, then you must set due date screens on Jira from Issues/Field Configurations.
Multiple Projects Managements
Sapling can only integrate with one Jira project at this time.
When a ticket is created, it will be unassigned.
Ticket Deletion Management
If a task that is assigned to Jira is deleted in Sapling, then the Jira ticket will also be deleted in Jira.
The audit log will show this as Jira Bot.
Ensure that in the project's permission scheme, you have given the permission Schedule Issues.
Check what Field Configuration Scheme the project is using. Inspect the specific Field Configuration for the issue type in question. See if the field Due Date is currently in a hidden state. If so, click Show to unhide it.
Check which screens your project is using. Ensure that you've placed "Due Date" on the proper screens.
💡 Looking to do more?