Hello @Ivan Andrieiev
Please show us the details of the Rule Trigger.
The message states that no related issues have changed since the last time the rule was run. That indicates that the Rule Trigger is running a JQL and has the option secondary option enabled to "Only include issues that have changed..."
Either the JQL has been changed, or that "Only include" option has been newly checked. Or whatever activity would normally be created the issues that are retrieved in the JQL has changed.
Hello @Ivan Andrieiev
The rule has been updated recently, which could have led to the situation where it is no longer working.
Kindly share the expectations from this automation rule, enabling us to help you further.
--GG
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Validate your expertise in managing Jira Service Projects for Cloud. Master configuration, optimize workflows, and manage users seamlessly. Earn global 🗺️ recognition and advance your career as a trusted Jira Service management expert.
Get Certified! ✍️Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.