This article will cover the topics:

This integration between Pipeliner Cloud and Jira allows you to:

This allows you to create a task for issue investigation by your development team right from Pipeliner!

In order to use this integration, you will need to have a Pipeliner Cloud subscription and a Jira for Cloud version (not Jira on-premise) account (www.Jira.com).

From the Admin Module, click on the "Automation Hub" Menu Item.

Find the "Jira" integration ⤵

Click on the "Jira" card and then “Add” ⤵

Once you’ve entered the "Jira URL", the instructions and values that you need are shown on the next screen. Work through setting up a new application link and copy and paste the values from the Pipeliner screen below into Jira ⤵

In Jira, go to "Settings" and choose "Products" ⤵

Under "Application Links", click on "Create" new link and paste in the "URL" from "Step #2" in the Pipeliner set up screen ⤵

If prompted, select “Use this URL” and then click on "Continue" ⤵

Copy the values from the Pipeliner set up "Step #3" to your Jira new application link fields ⤵

When all fields are filled in, click on "Continue" ⤵

Copy & Paste the values from "Step #4" ⤵

Finally, click on "Continue" to save your new Application Link in Jira ⤵

Click on "Authorize Access" to finish the set up of the connection ⤵

You’ll need to "Allow access" when prompted ⤵

Once authorized, you will need to complete the Configuration Settings.

First, you need to select the Jira project that the integration will work with ⤵

Next, choose one of your "Jira Issue Types" to create a mapping to ⤵

Now choose the corresponding "Pipeliner Task Type" ⤵

Now it’s time to set up your field mappings, the system fields will already be shown (and these cannot be changed) ⤵

NOTE: Remember that you can create custom Task Types in Pipeliner and add custom fields to the form for your custom Task just like you can for other types of the main record. For more information, please review this article.

When you enable the integration, a new custom Pipeliner field “Jira Issue Link”, of type URL, will be automatically added to Pipeliner and, once the task has been saved and the issue has been created in Jira, the link to that issue will display the link to the Jira issue so your users will be able to click through from the Task.

In order to map successfully from the Pipeliner Task Owner to the Jira Issue Assigned User, all users must use the exact same email address for both their Pipeliner and Jira logins. Additionally, in Jira, the user must make their email address visible to Anyone (do this from Jira Account Settings at the bottom of the Profile and Visibility tab) ⤵

If there is no match (user exists in Pipeliner but does not exist in Jira, for example) the Jira ticket will be unassigned. The Owner is only synchronized once when the Task is first created.

If you add a Watcher to the task in Pipeliner using "Watchers › Custom" as shown below, the user will also be added as a Watcher to the Jira issue subject to the same requirements as the Owner (i.e. an exact match on email login and a “public” Jira account). Like Owner, this value is synchronized once only, when the task is initially created.

The subject line of the Task is automatically synchronized to (and from) "Jira Summary".

All Comments added to the Task in Pipeliner are synchronized to Jira as comments and all comments from Jira are synchronized to Pipeliner as Comments.

Click on “Add Mapping” to select from your Jira issue fields and then select the matching field in Pipeliner ⤵

If you select a field from Jira and there is no corresponding field of that type to map to in Pipeliner, you’ll receive a warning and a prompt to add a new custom field of the right type to your Task.

For example, below I’m trying to map the “Time Spent” numerical field from Jira but I have no number type fields to map to in Pipeliner ⤵

The message tells me I need to create a new custom field to add to my custom Task using one of the number types in Pipeliner (either float — which has decimal places — or integer — which does not) ⤵

If you map a dropdown field, you need to ensure that the values are identical in both Jira and Pipeliner to ensure the synchronization works. If the values don’t match exactly, they won’t sync and you could lose that data.

Jira Labels fields — the Labels type field in Jira is very useful for tagging/categorising tickets, for example. You can map to it from your Pipeliner Task by creating a Text field (single-line text or long text). When you enter values into the field in Pipeliner, make sure to separate them only with a comma to ensure that they sync correctly.

This table confirms the field types that map to each other in Pipeliner and Jira ⤵

When you’ve finished your field mappings, scroll down to set up your "Status Mappings". Click to enable each one that you need. You can use the same Pipeliner status for multiple mappings if you want to ⤵

Finally, do the same for your Priority mappings and then click on "Save" ⤵

NOTE: All mapped fields are synchronized bi-directionally (when something is updated in Pipeliner, it will be updated also in Jira and vice versa).

Once your configuration is completed, one of our team will approve the integration for your organisation. Once it’s running you can begin creating your tasks in Pipeliner and have them create the issue in Jira.

I’ve created a Task here in Pipeliner, choosing my custom Task type “Support Ticket” which I chose when doing my mappings. I’m going to fill in the fields and also add a colleague as a Watcher ⤵

Here are my Activities in "List View" showing my saved “Support Ticket” Task ⤵

And here’s the Issue in Jira created by the integration. I’ve added a "Comment" to the Jira issue which will also sync back to the Task in Pipeliner ⤵