Bill Sheboy Expert

Hi @Herick Carvalho -- Welcome to the Atlassian Community! Your rule uses a scheduled trigger without JQL, but then the rule steps attempt to access issues. That is what the error is describing. One solution would be to move the JQL to the trigger, and remove any unneeded steps in the rule. Then each issue would process,…

Hi @Eugenia Fernandez Fariña -- Welcome to the Atlassian Community! I do not believe that is possible with JQL. According to this documentation, comma is a restricted character, which can be wrapped in quotation marks or preceded with a double-backslash to search.…

Hi @chm 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. Thanks!…

As you want to find a specific, unreleased version and then assign it to the issue, your rule could do this: Using the Send Web Request action, call the REST API function to search for the version, and then use both the id and release date values. An example search would be this: <your Jira…

Hi @Jatin Jalwan For dashboard gadgets, it can help to post images of the gadgets and of their configuration settings. That will confirm if you are using the built-in gadgets or marketplace addons. Until we see those... For the burndown gadget, the trend line could be flat if the issues were not sized before the sprint…

Hi @Luis Villamizar Yes, and...as a variation to the first method Trudy suggests: You could add a condition to check for your Description text being present.. For example, let's assume your rule was adding this text to the start of the Description: Business Problem: <add your problem> {{issue.description}} Your rule could…

Thanks for the updates, @Janice and team!! Yes, and...I wish the documentation pages had the last-updated timestamp too :^) Kind regards, Bill Update: Janice, I am seeing the original timestamp with a full, date / time expression and only a relative value for the edits (e.g., 2 hours ago). Is that intended? Thanks, again!

Hi @Peter Bosse This seems related to your other post here: https://community.atlassian.com/t5/Automation-questions/Re-Re-How-do-you-sum-up-story-points-to-the-epic-using/qaq-p/2646010/comment-id/9764#M9764 If your epic does have more than 100 child issues, the limit cannot be changed; it is part of the REST API functions,…

Hi @Rudy Holtkamp A math expression wraps the original question's use of join() and so that will work...unless there are other problems. And, when using the sum function the math expression wrapper is not needed. Instead that would be just {{issue.subtasks.Story points.sum}} Kind regards, Bill

Hi @Tamir Melamed Context is important for automation rule questions... 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…

Hi @Johnny Wong Has the team considered using a Jira Kanban board, a daily standup, and a team working agreement that includes at least: * all in-progress work is reflected on the board, * finish what is started before pulling more work, * ask for help when you need it, * offer help when you can, and * speak up if you…

Hi @Dave Furlani What is in the variable teamSprintsTESTbigbus when they did not contribute to the specific epic: an empty string, just a trailing @ symbol, something else? Knowing that may help to use conditional logic to handle the 0 and non-zero cases. Kind regards, Bill

Hi @Muriel Assmann Yes, and...to Laurie's answer: Why not set those fields at the same time as issue creation rather than using the separate edit...including the change to the summary? They could copy from the Trigger Issue, or use the smart values from: {{triggerIssue}} Also, do you ever expect issues to be in multiple…

Awesome; I am glad to learn that helped!

If you did not want the rule to release a version why did your rule use the Release Version action? That does not seem to match what you are now describing as the need, or the original question. The latest rule you show appears to have a specific version selected, "SLM 9.34.0", and to select the "Next unreleased version".…

As a reminder, it is not possible to change the board filter for a team-managed project, and so I am unclear what you tried for your item #5 above. I just tested with a company-managed project to change the board filter's sort order with ORDER BY Priority DESC and it worked for me. It took a few seconds to take effect and…

I recommend reviewing the ScriptRunner documentation to learn how to use smart values in a script.

Hi @E R The error message is suggesting how to fix that: put quotation marks around the value. In your rule, that would be this: issuetype = "Test Case" AND "Test Category" = "{{triggerIssue.Test Category}}" Kind regards, Bill

Thanks for that information, Richard. That is a marketplace addon gadget, and not built-in. I recommend identifying the vendor and checking with their support team in the marketplace: https://marketplace.atlassian.com/ If you do not see the vendor's information on the gadget settings, your Jira site admin will be able to…

Hi @Massimo Briceno -- welcome to the Atlassian Community! Yes, and...to Laurie's answer: The filter for a company-managed project can be updated to change the issue sort order for the board and backlog. However, please note well: when the filter is anything other than ORDER BY Rank ASC the drag-and-drop feature to…

Hi @Richard W Beemer -- Welcome to the Atlassian Community! Which specific dashboard gadget are you trying to use? Is that from a marketplace vendor? Please post an image of the gadget configuration to help provide context. Kind regards, Bill

Hi @khenson With the pull request merged trigger, please see these smart values to learn the name of the branch: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/#--Pull-request-- Kind regards, Bill

With the Release Version action, an exact name must be given. It cannot search for a name using the CONTAINS ~ operator, like with JQL. Based on what you described, you are trying to release the version assigned to the issue which has a name start containing the text SLM, and which is not yet released. As the fix version…

If the text field contains exactly this: 400h Then the error may be caused because your edit appears to add a unit of measure of minutes with "m" after the value. Perhaps try removing that from the edit. Also please note: smart values are name, spacing, and case-sensitive. The smart value for issue should be in lower case.

Hi @Joe Sherman -- 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…

Context is important for automation rules, so please show images of: * your complete rule, in one image * the audit log details showing the rule execution Where have you tried to filter the version value before setting it?

Hi @abraham -- Welcome to the Atlassian Community! Adding to Jack's answer... Are you using a team-managed or a company-managed project? (You may find this information at the bottom-left side of the page expanding area.) When using a team-managed project, transitioning an issue does not move it to the board. An extra rule…

Hi @Núria Rull Bassols 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…

Argh, indeed! I am out of ideas on this one. I suggest submitting a ticket to Atlassian Support at this link, providing them a link to this question thread for context: https://support.atlassian.com/contact/#/ You're the site admin for a paid license and so you will permitted to do that. When you hear back from them,…

Hi @Jeevan Kumar K G You seem to be repeatedly creating questions like this, which are just requests for a completed automation rule. It also appears you have not first tried to solve the problems yourself. This is a community of people with similar interests, sharing ideas, learning from each other, and asking for help…