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.
This article outlines how described functionality appears and operates in the old layout. If you are using Dashboard 2.0, please refer to the corresponding article in the Help Center.
Available on: Pro & Enterprise editions.
Follow the instructions on how to:
Please note that before setting up the integration between Ziflow and any third-party tool, it is necessary to connect Ziflow with the external application first. The process of connecting Ziflow to external applications can be found below.
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.
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.
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.
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.
You will be presented with the event details page, which will vary depending on which event you selected. There are nine different types of events:
New proof/version
Triggered by - select the type of request that will trigger the Zibot.
Created in - select the Ziflow folder that will be monitored by this flow.
Created by - select the user who will be responsible for this flow activation.
Proof updated
Triggered by - select the type of request that will trigger the Zibot.
Modified in - select the Ziflow folder that will be monitored by this flow.
Decision made
Triggered by decision made - select what level decision needs to be made to activate the flow.
Type of decision - choose the type of decision that needs to be made to activate the flow.
Created in - select the Ziflow folder that will be monitored by this flow.
New comment/reply
Triggered by new comment / new reply - choose which option should activate the flow.
Made by - choose if a Zibot should be activated by a specific reviewer or by anyone that adds a comment/reply.
Created in - select the Ziflow folder that will be monitored by this flow.
Comment resolved
Created in - select the Ziflow folder that will be monitored by this flow.
Comment labeled
Comment is labelled as - select which label(s) should trigger a Zibot.
Created in - select the Ziflow folder that will be monitored by this flow.
Stage updated
Triggered by - select which type of the stage updated event should trigger the Zibot. There are three types of stage update events: reviewer added, reviewer removed, stage locked, and deadline changed.
Modified in - choose the Ziflow folder that this flow will monitor.
Stage started
Triggered by - select which type of the stage updated event should trigger the Zibot.
Modified in - choose the Ziflow folder that will be monitored by this flow.
Comment reaction
Triggered by - choose if you want to trigger a flow based on reactions added to comments or replies.
Comment reacted with - select what type of reaction should trigger a flow.
Created in - select the Ziflow folder that is going to be monitored by this flow.
Setting up Jira Zibot action
After saving the event flow triggers, choose a Jira Zibot action that will pass the information set in the previous step directly to Jira:
Use following Zibots
Search Jira Project - with this, Zibot users can search for Jira projects with their project key or name:
Search Jira Issue - with this, Zibot users can search for Jira issues with their key or name:
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.
Transition a Jira Issue - helps with transitioning Jira Issue from one issue type to another.
Add comment to Jira Issue - lets adding comments to selected Jira issues.
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.
2. Choose Create Jira issue from the Zibot list:
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).
4. Create a proof that will trigger the automation and check if the Task, along with the description, was added correctly in Jira.
