Link existing comments to checklist items

We’ve expanded the functionality of Checklists (currently in Public Preview) by adding the ability to associate existing comments with checklist items. Previously, comments could only be linked to a checklist item at the moment of creation.

Now, when editing an existing comment, an association [+] icon will appear upon hover within the checklist item. Clicking this icon will link the existing comment to the checklist item once the edited comment has been saved, streamlining the process of connecting all relevant feedback.

This enhancement covers the scenario where stakeholders leave a general comment and later realize it pertains to a specific checklist requirement. You can now easily connect that existing feedback to the correct item, ensuring all criteria are addressed and tracked clearly.

For more information, see Add a checklist item to an existing comment.

Maximum number of checklists per review stage increased from 3 to 10

When Ziflow’s Checklist feature was initially released in public preview, a ceiling was set on the number of checklists that could be associated to a given review stage. Enterprise teams who have been using Checklists have found a need for more individualized lists of objective review criteria than the initial maximum of 3 checklists per stage.

With this release, based on feedback from our customers, we’ve increased the maximum number of checklists per stage to 10. Checklists are in public preview, and we welcome your comments and suggestions as we look to refine this feature before it becomes generally available.

monday.com integration 

Support for the monday.com desktop app

When Ziflow first debuted our seamless integration with monday.com, users were restricted to using it within a web browser, due to technical limitations regarding the Ziflow authentication process in the desktop app environment. 

With this release, we have worked closely with the team at monday.com to enable the exact same sign-in flow and full functionality within the monday.com desktop app. Whether you are using the browser or the dedicated application, you can now manage your creative review and approval process with Ziflow’s seamless integration.

Our goal is to meet users wherever they choose to work, providing a consistent experience across multiple contexts. This update was a top request from several of our customers and ensures that your proofing workflow remains centralized, regardless of your preferred monday.com environment.

Create a new version of a proof in a single click

We’ve added a new “+” button to the monday.com in-item widget, allowing users to create a new version of an existing proof with a single click. While the ability to create a new version previously existed within the widget's "three dots" context menu, this update makes the action more prominent and easier to access for novice users. 

It’s important to note that users must be signed in to Ziflow and have the necessary permissions to create new versions for this button to appear. For those users, this frequently used function is now easier to find, reducing clicks and ensuring their collaborative review process stays within monday.com.

Jira integration: Enhanced transition configuration for non-administrators

We have introduced new configuration options for the “Transition a Jira issue” Zibot, making it easier for users without Jira system administrator privileges to automate their project workflows.

In Jira, an item’s Status represents its current state (e.g., "In Progress"), while a Transition is the specific action that moves an item from one status to another. Previously, configuring these transitions within Ziflow required Jira administrative access to view the full set of available transition IDs.

With this release, we have added three Transition Source radio buttons within the Zibot configuration to provide more flexibility:

• Select transition from Jira configuration: This remains the standard option for Jira system administrators, allowing them to select from the full list of transitions.
• Select from an example project issue: Users can now copy and paste a specific Issue ID. Ziflow will then automatically fetch the Transition IDs associated with that specific issue, allowing non-admins to configure the Zibot accurately.
• Provide transition ID: For users who already have the specific ID, this option allows for a direct copy/paste of the Transition ID into the configuration field.

This update removes an administrative bottleneck. By allowing users to pull transition data from example issues or provide IDs directly, Ziflow enables project managers and contributors to build and maintain their own Jira automations without requiring assistance from IT or Jira System Admins. 

For more information, see Transition a Jira issue.

Proof Viewer: Improved pixel comparison for high-resolution assets

We’ve enhanced the precision of pixel comparison within Compare Mode, specifically when reviewing large-format assets at high zoom levels. Previously, performing a pixel-level comparison on very large files could occasionally result in minor visual artifacts, which could make it difficult to distinguish between subtle design changes and processing inconsistencies.

With this release, Ziflow utilizes higher-resolution data during the comparison process to ensure that differences remain sharp and accurate. This update eliminates visual noise and provides a much clearer view of changes, even when you are zoomed in to inspect the finest details of a high-resolution file.

These improvements apply to static images that have been converted to proof tiles. 

ReviewAI (in public preview) 

Asset metadata now used alongside Checklist AI-prompt descriptions

Building upon our recent updates that incorporated Proof Brief text and Custom Property information, Ziflow has now enabled specific asset metadata to be referenced directly by ReviewAI prompt descriptions.

With this release, ReviewAI can analyze a file's technical attributes to provide more informed and accurate results. The supportive data now available for reference includes:

• Type (e.g., STATIC)
• File Name and File Extension
• File Size
• Resolution and Dimensions (including pixel density/DPI)
• Aspect Ratio

This update is part of our continued effort to expand the contextual framework for your automated checks, helping the AI frame what it should be looking for as it pertains to specific file properties. By allowing Checklist items to reference this supportive data—such as verifying that an asset meets specific dimension requirements or matches naming conventions—ReviewAI can more precisely evaluate your content and ensure it aligns with your technical specifications.

ReviewAI remains in public preview, and is available to Enterprise customers as a paid add-on. To learn more about this add-on and how it can benefit your team, please reach out to your Customer Success Manager.

Checklists (in public preview)

Opt-out individual checks from ReviewAI evaluation

When a checklist template is enabled for ReviewAI, the AI typically evaluates every item within that checklist. However, certain checks may not be suitable for AI analysis or may still be in a testing phase where automated evaluation isn't yet required.

With this release, we’ve added a checkbox that allows you to opt-out individual checklist items from ReviewAI analysis. When an item is excluded, it will no longer show that ReviewAI is suggesting (or has suggested) an outcome, and the check results will explicitly state, "This check was excluded from ReviewAI evaluation."

This update, driven by feedback from our public preview customers, provides greater granular control over your automated workflows. By allowing you to bypass specific items that are better suited for manual review or are still being fine-tuned, you can ensure your ReviewAI resources are focused only on the most relevant and effective automated checks.

For more information, see Exclude checklist item.