Integrate Ziflow online proofing workflows into Jira Cloud to automatically create to-do items and update Jira tasks based on new proofs, comments, and decisions to keep your team in sync.
Available on: Pro & Enterprise editions.
-
Connect with Ziflow and Jira
Before setting up the integration between Ziflow and any third-party tool, you must connect Ziflow with the external application.
- Log into Ziflow and go to Connect > Applications.
- Find the Jira tile and select Connect.
- In the Authorize app dialog box, review the information and select Accept. Once you authenticate in Jira and authorize Ziflow to connect with Jira, you can set up automated actions between Ziflow and Jira.
Select the Jira tile again, choose the Settings tab, and select Show next to the Application fields on a proof to enable Jira fields at the proof level.
Set up Jira automated flows
Once Ziflow and Jira are connected, you can set up automated flows to send information to Jira.
- Choose Connect and select Create Flow in the upper-right corner of the window.
- 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.
Ziflow events
Depending on the event you selected, the events on the event details page will vary:
New proof/version
An event is triggered by creation of a new proof or a new proof version.
Field Description Triggered by Select the type of request that will trigger the Zibot. Created in Select the Ziflow folder that this flow will monitor. Created by Select the user responsible for this flow activation. Created from Select a source event from which the flow will be triggered. Proof updated
An event is triggered by a proof update.
Field Description Triggered by Select the type of request that will trigger the Zibot. Use various events that might trigger the flow: folder change, proof settings updated, custom property edited, integration properties changed. Modified in Select the Ziflow folder that this flow will monitor. Decision made
An event is triggered by a decision.
Field Description Triggered by decision made Select which level a decision needs to be made to activate the flow. For example, you might distinguish three different levels of decision: on proof, on stage, and by reviewer. Type of decision Choose the type of decision that needs to be made to activate the flow. Created in Select the Ziflow folder that this flow will monitor. New comment/reply
An event is triggered by a new comment or a reply.
Field Description Triggered by new comment / new reply Select whether a comment or a new reply should trigger the flow. Made by Choose if a Zibot should be activated by a specific reviewer or anyone who adds a comment/reply. Created in Select the Ziflow folder that this flow will monitor. Comment resolved
An event is triggered by a resolved comment.
Field Description Created in Select the Ziflow folder that this flow will monitor. Comment labelled
An event is triggered by a comment label.
Field Description Trigger by label made Select whether this event should prompt action based on adding labels to comments, replies, or both. Comment is labeled as Select which label(s) should trigger a Zibot. Created in Select the Ziflow folder that this flow will monitor. Stage updated
An event is triggered by updating a stage.
Field Description 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 Select the Ziflow folder that this flow will monitor. Stage started
An event is triggered by starting a stage.
Field Description Triggered by Select which type of the stage updated event should trigger the Zibot. Modified in Select the Ziflow folder that this flow will monitor. Comment reaction
An event is triggered by a comment reaction.
Field Description Trigger by Select whether to start a flow based on reactions added to comments, replies, or both. Comment reacted with Select what type of reaction should trigger a flow. Created in Select the Ziflow folder that this flow will monitor. Set up a Jira Zibot action
After saving the event flow triggers, choose a Jira Zibot action to pass the information set in the previous step directly to Jira. Once your actions are set up, Ziflow will send or update data in your designated Jira account.
Search Jira Project
Use to search for Jira projects with their project key or name:
Search Jira Issue
Use to search for Jira issues with their key or name:
Create Jira Issue
Use to add a new issue inside the selected workspace and project. The issue title and description can be filled in using our built-in token selector.
Create Jira Subtask
Use to add a new subtask to a Jira issue.Transition a Jira Issue
Use to help with transitioning Jira Issue from one issue type to another.
Add comment to Jira Issue
Use to add comments to selected Jira issues.
Connect Ziflow proofs with Jira issues
Once you've connected Jira to Ziflow, you can start manually linking proofs with the Jira issues from the Integrations tab while creating proofs or editing proof details.
Note: Integration fields must be enabled in the application settings to be used while configuring or editing proofs.
To connect proofs manually with Jira issues during the proof configuration, open an integrations tab and select the Jira issue details (workspace, project, and issue).
Jira flow examples
Add a new Jira issue and populate application fields upon new proof creation in Ziflow
Before you start configuring the flow, please make sure to read the Ziflow internal Zibots article. This step is necessary because you need to connect Ziflow as an internal application in order to use it to update proofs.
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. Next, you must add three internal Ziflow Zibots (Update proof integration property). They aim to populate the application fields (Workspace ID, Project ID & Issue ID) of a newly created proof with information sourced from Jira.
5. Fill out the Update proof integration property Zibots configuration.
7. Save and turn on the flow as a last step of flow configuration.
8. Create a proof to trigger the automation and check if the issue was added correctly in Jira.
Supporting Material
-
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.
Supporting Material:
Related to
Comments
0 comments
Please sign in to leave a comment.