The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →The available CogniRunner 3.3.0 documentation does not provide a verified procedure for pausing an in-progress rule until a Jira issue reaches a chosen state, then resuming it. CogniRunner documents event listeners and scheduled jobs, but neither source describes a durable “wait for state” action or how it would continue a paused rule.
What CogniRunner 3.3.0 documents
Atlassian Marketplace lists CogniRunner 3.3.0 as a Jira Cloud app by LeanZero SRL. Its listing describes event listeners, cron-based scheduled jobs, and a Rules REST API for provisioning those two rule types. The listing gives the version’s release date as September 7, 2026. Atlassian Marketplace listing.
As an Amazon Associate I earn from qualifying purchases.
LeanZero’s September 9, 2026 release article says, “A listener reacts to a Jira event.” It describes listener filters for project, issue type, JQL, changed fields, and comment regular expressions, plus an optional plain-language AI condition. Scheduled jobs are described separately as cron-based. LeanZero release article.
Those descriptions explain how listeners and scheduled jobs are triggered or filtered; they do not specify a step that suspends an already-running rule, watches for a state change, and resumes that same execution. The reviewed sources also do not give fields, timeout behavior, or a supported resume mechanism for such a step.
#1 Best Overall
Can you configure a state wait from these instructions?
No verified configuration recipe is available in the reviewed CogniRunner sources. They do not show where to add a wait action, how to select a target state, or how to continue the paused rule when the issue enters that state. This is a documentation limit, not proof that no such capability exists elsewhere in CogniRunner’s full documentation or app.
Listeners are the closest documented event-driven feature: they react to Jira events and can use the listed filters. However, configuring a listener is not documented as equivalent to a durable wait inside an existing rule. The sources do not establish that a listener can preserve execution context or resume a prior rule, so do not treat it as a drop-in substitute.
Do not apply another product’s “Wait for Condition” steps
ServiceNow documents a separate “Wait For Condition” action with a record condition and optional timeout. That documentation concerns ServiceNow, not CogniRunner or Jira, and does not establish CogniRunner fields or behavior. ServiceNow Wait For Condition documentation.
What to verify before building the workflow
Consult CogniRunner’s current app documentation or LeanZero support for an explicit state-wait action and its behavior. To confirm it meets the need, get documentation for the configuration fields, what event releases the wait, whether the original execution resumes, and any timeout or failure handling. The Marketplace listing and release article cited above do not answer those implementation questions.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
