Bill Sheboy Expert

Hi @Carina Lora -- Welcome to the Atlassian Community! I am a bit confused by your use case, as your description seems different from your example rule. It seems like you want to: * once a month, create a user story; * linked to a specific epic; * copy the following fields to the story from the epic: description, assignee,…

Hi @PATRICIA MURPHY You appear to be on a Premium Jira Cloud license; is that correct? If so, it is less unlikely you are hitting usage limits for global/multi-project rules, as you get 1000 per user, per month! https://www.atlassian.com/software/jira/pricing Instead I suggest there is something specific about the rule(s)…

Hi @Mark Nosworthy -- Welcome to the Atlassian Community! That suggestion link which @Pramodh M provided is for an idea that is over 16 years old. Given that, you may want to investigate how your systems consuming the Jira data can parse/clean it. Kind regards, Bill

Hi @Rafet Karaoglu -- Welcome to the Atlassian Community! First thing, I agree with John's suggestion to use a branch with the JQL in your Lookup Issues instead of the lookup. The lookup probably doesn't help for this use case. And...I am surprised that the Link Issues action works (worked?) with {{lookupIssues}} as the…

Hi @Idan Shteinberg -- Welcome to the Atlassian Community! The only built-in dashboard gadget that might meet your need is the pie chart gadget. Please look here for more information: https://support.atlassian.com/jira-cloud-administration/docs/use-dashboard-gadgets/ IMHO, Jira has limited out-of-the-box reporting…

Hi @Tom Jones [Appsvio] When recommending a marketplace vendor product, please ensure that you disclose your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Community online guidelines for Marketplace and Solution Partners…

Hi @Johan Havner At this time, I believe the only way to do that is to call the REST API from a web request within the rule. If you want to try that, here are some references to help: * https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828 *…

Hi @Elyashiv Grosser Have you tried using the JSON array function first, and then performing the replacement of text on the result, and finally use that to set the field in the advanced edit? If that does not work, you could also try to construct the JSON string using a list iterator over the source field, replacing the…

Mykenna, did you try to actually send the emails? I just tested and it failed for me too: * Can write the values to the audit log, but they collapse to null in the email TO field * Tried saving the Lookup Issue values to a single created variable first, and got the same result * Tried a separate branch to send to one…

Yes, and...smart values are usually case-sensitive. So please check if you are using {{lookupIssues}} in your log entries and the email TO address list. Thanks!

Hi @Tim Foster Did you note you have some square brackets, not curly ones in your smart values in the image? The smart values should only use curly brackets. Thanks, Bill

I believe the article you note on created variables and branching is this one: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Create-variable-New-component/ba-p/1448118 If you read the article and comments carefully, you will note that technique only works when the branch is for one-and-only-one…

Hi @Jeff Whitehead Yes, and...to what Mikael notes: If you read through that thread you will also see that automation rules' smart values are impacted. Atlassian notes they will attempt to automagically update what they can, and other rules may require manual updates; Atlassian noted a plan to send out more information on…

Hi! I am guessing that your JQL is trying to use a smart value, correct? If so, please remember to wrap that in quotation marks to help JQL interpret the value. For example...depending on what you are matching to: "Start date[Date]" = "{{lookupIssues.first.Start date}}" or "Start date[Date]" = "{{lookupIssues.Start…

Hi @Mark Davies I just tried this for my own filter and it worked for me. Some things to check are: * Run the JQL manually in advanced search and confirm it works, and confirm the returned issues actually have fixVersion values * Run that same REST API call in a browser to confirm it works, and look for the fixVersions. If…

That depends upon the issuetypes and parent/child relationships. For your rule, the trigger issue is a subtask and you want all of the "sibling" subtasks for the same parent. Thus your starting JQL would be this, substituting in your project name: project = myProjectName AND parent = {{triggerIssue.parent}}

Hi @Tim Foster -- Welcome to the Atlassian Community! Yes, and...to the other responses: You may be getting an issue from any trailing delimiters, so you can selectively add the delimiter like this: {{#lookupIssues}}{{reporter.emailAddress}}{{^last}};{{/}}{{/}} This will add a semicolon between all the addresses, and leave…

Yup...Maybe divide and conquer this one by splitting to lines to isolate the searching. This worked for me when I tried your example description: {{issue.description.split("\n").match(".*Organization:\*(.*)")}}

Also...you may want to check your display scaling, as I recall a ticket about zoom/screen control display issues (i.e. buttons) when using high resolution monitors and setting to any recommended scaling above 100%. Several of the board reports have this symptom, with the only work-around of "try a lower zoom".

Hi @Alex Borges da Silva Thanks for the image of your rule, as that may explain this error... Your branch is referencing a Lookup Issues result but you do not have a Lookup Issues action. Please add that action before the branch with whatever JQL you need. Kind regards, Bill

Thanks, @Christine P. Dela Rosa as this thread may lead to some "spirited conversation" :^) Underrated: Pragmatic Thinking & Learning: Refactor Your Wetware. This is a good one to learn about learning, and how to get better at getting better. Overrated (and often quite damaging): The Five Dysfunctions of Teams. I find many…

Hey @Sam Harding Would you expect created variables to work in these types of conditional tests, within list iterators? It seems like they do not. Thanks, Bill

Hi @Neil B -- Welcome the Atlassian Community! Have you tried a simpler match expression to return the value, perhaps to the audit log before trying the field edit? In my experience thus far, the regular expression handling for automation rules does not consistently implement the references in the documentation. And, even…

Hi @Randy O'Neal You note that your rule occasionally erroring. Would you please show an image of the audit log details and describe the symptom/error you observe is happening? Thanks! Regarding your rule structure question, you could merge most of your tests on the parent into a single JQL statement, and use a JQL branch…

Hi @Dylan Davenport -- Welcome to the Atlassian Community! Would you please clarify what you mean by your statement: "When viewing my board, the content seems to shrink or zoom out randomly"? For example do you mean: * when I do nothing and observe the browser tab view, things randomly shrink/zoom in size of their own…

Hi @[deleted] Adding on to Jack's answer, I have a question: where are these tests in your Jira instance? If a Story is being worked on during a sprint, wouldn't the associated/linked Test also be worked on during that sprint...using the ideas of Scrum? And if so: why not just put the Tests in the same sprint, in the same…

Hi @Diane Fahr The labels field is a list of values, so perhaps trying converting it into a JSON array first, like this: { "fields": { "customfield_12501": {{triggerIssue.labels.asJsonStringArray}} } } Kind regards, Bill

Hi @Tina.Henry Short answer: no, there is no out-of-the-box way to preserve the ordering of subtasks. Longer answer: The subtasks are ordered by create date, unless you drag them to a new order within the parent story. I am guessing during the asynchronous processing of some Jira Cloud operations clone leads to this…

Hi @eibokette I believe create (and clone) issue actions are exceptions to the multi-project requirement noted, so no problem there. Would you please post an image of your audit log details for the execution showing the error? That may provide more context for what is happening. Thanks! Kind regards, Bill

Hi @Mkurama Adding to what Manon suggests: Once you store the values in created variables, you may need to convert them from text with asNumber before performing the math operation you show to set your "progress" field: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#asNumber Kind…