Summary: With our Jira (Cloud) integration, users can extend their Ziflow online proofing operations to Jira. Users can automatically create, complete to-do's/lists, and update tasks in Jira for new proofs, comments, decisions, and more to keep their team up to date in the tools they're already using.

Follow instructions on how to:

How to connect with Jira

To integrate Jira with Ziflow, open the Connect tab in the Ziflow account and then click on the Applications tab on the left. Once inside the Applications menu click on the Connect Application button and select Jira from the list.

Connecting Ziflow with Jira application

Once you authenticate in Jira and authorize Ziflow to connect with the Jira account, you can start setting up automated actions between Ziflow and Jira.

Jira application on a connections list

Setting up Jira automated flows

Once Ziflow and Jira are connected, you can begin setting up automated flows to send information to Jira. Start by going to the Connect tab and by clicking on the Create Flow button in the upper right corner of the screen.

Create flow button in Ziflow

Select Ziflow as the Application and choose which Event (new proof/version, decision made, new comment/reply, comment resolved, comment labeled) you want to trigger the integration.

Create a flow with Ziflow as application and then select an event trigger

You will be presented with the event details page, which will vary depending on which event you selected. There are 8 different types of events:

New proof/version

New proof/version event settings
  1. Triggered by - select the type of request that will trigger the Zibot.

  2. Created in - select the Ziflow folder that will be monitored by this flow.

  3. Created by - select the user that will be responsible for this flow activation.


Proof updated

Proof updated event settings in Ziflow
  1. Triggered by - select the type of request that will trigger the Zibot

  2. Modified in - select the Ziflow folder that will be monitored by this flow


Decision made

Decision made event settings in Ziflow
  1. Triggered by decision made - select what level decision needs to be made to activate the flow.

  2. Type of decision - choose the type of decision that needs to be made to activate the flow.

  3. Created in - select the Ziflow folder that will be monitored by this flow.


New comment/reply

New comment/reply event settings in Ziflow
  1. Triggered by new comment / new reply - choose which option should activate the flow.

  2. Made by - choose if a Zibot should be activated by a specific reviewer or by anyone that adds a comment/reply.

  3. Created in - select the Ziflow folder that will be monitored by this flow.


Comment resolved

Comment resolved event settings in Ziflow
  1. Created in - select the Ziflow folder that will be monitored by this flow.


Comment labeled

Comment labeled event settings in Ziflow
  1. Comment is labelled as - select which label(s) should trigger a Zibot.

  2. Created in - select the Ziflow folder that will be monitored by this flow.


Stage updated

Stage updated event settings in Ziflow
  1. Triggered by - select which type of the stage updated event should trigger the Zibot

  2. Modified in - choose the Ziflow folder that will be monitored by this flow.


Stage started

Stage started event settings in Ziflow
  1. Triggered by - select which type of the stage updated event should trigger the Zibot

  2. Modified in - choose the Ziflow folder that will be monitored by this flow.


Setting up Jira Zibot action

After saving the event flow triggers, choose a Jira Zibot action that will pass information set in the previous step directly to Jira:

Setting up Jira Zibot actions in Ziflow

Use following Zibots

  1. Search Jira Project - with this Zibot users can search for Jira projects with their project key or name:

    Search Jira Project Zibot configuration
  2. Search Jira Issue - with this Zibot users can search for Jira issues with their key or name:

    Search Jira Issue Zibot configuration

  3. Create Jira Issue - adds a new issue inside the selected workspace and project. Issue title and description can be filled in using our built-in token selector

    Create Jira Issue Zibot configuration
  4. Transition a Jira Issue - helps with transitioning Jira Issue from one issue type to another

    Transition a Jira Issue Zibot configuration

  5. Add comment to Jira Issue - lets adding comments to selected Jira issues

    Add comment to Jira Issue Zibot configuration

And you're done! Ziflow will now send or update data in your designated Jira account.

Jira flow examples

Add a new item and update the column

1. Select the needed event trigger. In most cases, it will be a New Proof/Version event. This event will trigger once the new proof is created.

Create a new flow with Ziflow as application and a New Proof/Version as an event trigger

2. Choose Create Jira issue from Zibot list:

Adding Create Jira issue Zibot as a first flow action

3. Fill out all necessary data in the Zibot configuration. In my example, I want to add a new issue (I've selected Task as in issue type) to the Ziflow Review project at the ziflow workspace whenever a new proof is created on the Ziflow side. Please note that you can use a variety of different tokens from the list (I went with a PROOF.NAME as a Task name and PROPERTIES.[PROOF.DETAILS].[DESCRIPTION] as a task description).

Create Jira issue Zibot configuration

4. Create a proof that will trigger the automation and check if the Task along with the description was added correctly in Jira

Test if flow is triggered when you upload a new proof

Supporting Material:

Did this answer your question?