Bill Sheboy Expert

Hi @Ilia Mamontov You could try a rule triggered on Sprint Completed, branch to the issues in the sprint, and then edit the issue Flagged field, leaving the value empty. That will clear it. If instead you are performing some type of clean-up activity, have you tried searching for the specific issues with JQL and using the…

Please check the Rule Details section to see if the "Allow Rule Trigger" option is enabled. If it is, disable that. This option is normally used when one rule does some action that you want to trigger another rule. It is disabled by default to prevent errors and run-away rule execution / looping.

Hi @Ron Aisen Have you tried this AQL documentation: https://support.atlassian.com/jira-service-management-cloud/docs/use-assets-query-language-aql/ And perhaps using the Lookup Objects action in rules with that: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-objects Kind regards, Bill

Hi @Andrei Morozov -- Welcome to the Atlassian Community! This is a known defect which appears to have been introduced with the feature to set an issue status during the create: https://jira.atlassian.com/browse/AUTO-916 I just confirmed it still happens for my test project. The work-around is to disable this permission to…

Thanks for clarifying that! When the approvers change for a version, that does not appear to raise an event that can trigger an automation rule. As a work-around, a scheduled trigger could be used to check a specific version, using a REST API function, as that can see the approvers and their status of approval:…

I am glad to learn that helped! Regarding field visibility, that is an unfortunate need for custom fields to be editable by rules. An alternative is using an entity property as that would not need to be visible for rules to access it. How are you using that field such as in reporting? That may impact if using entity…

Please consider meeting with that manager and your team agile coach (or Jira admin) to understand why they want an issue on the board to manage this. That may reveal another approach, such as a dashboard or quick filter for the board. The reason I suggest this is: * This situation indicates a training opportunity for the…

Hi @Tomislav Tobijas This is a known limitation of automation rule, list iterators: they can only access data from the scope of the iterator, and lower. They cannot "see" other issue fields, created variables, branch variables, etc. In a few different posts, I have read Atlassian engineers tried to fix this limitation but…

I am glad to learn you have something that is working! (And yet Bill continues... :^) To me this symptom is a defect...changelogs have lots of problems in automation rules, often due to timing. However I have a couple of other hypotheses, based on no actual knowledge of the Jira automation engine implementation: * Unlikely…

As noted earlier, to log work with JSON use the timeSpent smart value. This is different than when just reading the information as a number. https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Time-tracking-and-logging-work And there appear to be extra curly brackets in your JSON…

Thanks for that information. It appears you are using a Team-managed project, and are trying to sum the Story Point Estimate to the parent Epic. Is that correct?

Hi @Mourad Siala For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas.…

Hi @Giulia Carletto You could use the JQL operator CHANGED to see if the status changed from / to particular status values at least one time. Counting the number of changes is more difficult with out-of-the-box Jira features. For example, let's assume your workflow is: To Do > In Progress > In Review > Done You may find…

Hi @Ste Wright What is the purpose of the Re-fetch Issue action in your rule example? Thanks! Kind regards, Bill

Hi @N Holm -- Welcome to the Atlassian Community! Do you care about any of the embedded newline characters in your search results? If not, you can help the match() function by first splitting on newline. For example: {{issue.description.split("\n").match(your search expression)}} Kind regards, Bill

Hi @Lisa Zanini Adding to Sebastian's answer... Integration with Azure DevOps is not natively supported with Jira Cloud. Please see this suggestion to add that, with a search link to the marketplace for addons: https://jira.atlassian.com/browse/JSWCLOUD-20460 And even with the addons, there appear to be some limitations,…

Hi @Ratih Ebtania It is not possible to log work as if you were another user (e.g., by impersonation). What problem are you trying to solve by doing this: why and what? Knowing that may help the community to offer better suggestions. Thanks! Kind regards, Bill

Hi @Steven Copp -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide…

I did see the screen shots, and wondered if that was a long rule with an if/else condition or was multiple rule executions. It appears to be different rule executions...with different Description values. I also tested your #5 version, which essentially just drops the final replacement of ~~ back to newlines, and that…

Hi @Don Hames Adding to Trudy's advice about checking for service limits... If you really want to update thousands of issues this way, I recommend pausing and reading this notice about the change to the automation packaging model and limits for rule…

Hi @Anastasiia Tsvetkova I am following up to learn if your question has been solved. If so, please consider marking this one as "answered" to help others find solutions faster. If not, let us know what additional help you need. Thanks!

Hi @Hannah Levick -- Welcome to the Atlassian Community! I am following up to check if Stefan's answer solved your question. If so, please consider marking this one as answered...and if not, please let us know if you need more help. Thanks! Kind regards, Bill

In your rule triggered on Issue Created, add the Re-Fetch action just after that, and before the Edit Issue fields to set the custom field. Back to your original question: have you tested enabling the option for "Allow Rule Trigger" to see if that helped?

Hi @Sven Just following up to learn if you solved this question yet. If not...a mentioned user cannot be directly checked for group membership, but a couple of work-arounds are: * Temporarily assign the user to the issue, use the User Condition with "user is in group" and specify the group, and then re-assign the issue…

Hi @Tom Yan Just following up to check if this solved your question or if there is more to do. Thanks!

Well done!

Hi @Stephan Grubbe Adding to Trudy's answer... I saw this symptom earlier this week helping with a related question. There are definitely problems with the changelog in automation rules when changing a sub-task's parent. And apparently the triggers do not consistently fire for changing the parent. (For example, "convert to…

In that case you may want to contact Atlassian Support to see if they have other options: https://support.atlassian.com/contact/#/ Please add a link to this thread in your support ticket so they can see what you tried. When you hear back from them, please post what you learn to benefit the community. Thanks!

This one, to re-load an issue during the rule execution: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Re-fetch-issue-data

Hi @danielle This may be possible with an automation rule...depending upon your assumptions / conditions. The rule would be triggered on issues transitioned to done, then checking their links for dependencies, it would walk those issues...checking their dependencies before sending the notification. One challenge is scale:…