Bill Sheboy Expert

Hi @testJira seb -- Welcome to the Atlassian Community! Just to confirm, are you noting that you have an automation rule and it works once and then produces incorrect results on later executions? If so, please post an image of your complete rule, including the details of the field action, and the audit log details showing…

Hi @Nigel Thurston-Smith Reading through your question and the community responses, I wondered if this was a one-time need for cleanup or an on-going need: * One-time need for cleanup: Perhaps run a single query to find all closed epics in the project. grab their keys to convert to a comma-separated values list, and then…

Hi @nicolas lembeye Let's disregard any concerns around assigning story points to subtasks for now... One safer way to do this summation with an automation rule is to always sum the total completely, ignoring any plus/minus changes over time. To do this, branch to the parent and use the sum function: {{issue.subtasks.Story…

Hi @Agnieszka Cichocka 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 @Chris Carpenter For more than 100 issues, you are going to want to use the REST API rather than Lookup Issues, perhaps calling the search function with JQL and only look at the "total" count in the response to get the number you need. Here is a how-to article for calling the REST API from an automation…

Try using the lookup for the source for the issues and then put the result in the created variable. For example: * trigger: some trigger... * action: lookup issues with JQL to find Todo issues * action: create variable* name: issuesTodo * smart value: {{#lookupIssues}}*{{key}}{{/}} * action: lookup issues with JQL to find…

Hi, Colin. Thanks for that information! When I asked about "stability" I wondered if you had a consistent list of symptom/impact areas you wanted to measure...or...if that list evolves over time. From your description it seems to evolve, and so perhaps labels are better than components. One challenge with labels that could…

That information helps; thanks! Please also post an image of the audit log details for when the rule runs and does not work as you expect.

Would you please expand to show the details of the audit log for that rule execution, and post that image? And...please note because this is a multi-project rule, creating versions in either project could trigger the rule. Please consider if that is what you want, and what "stopping condition" you need to help prevent rule…

Hi @Ignacio Vera -- Welcome to the Atlassian Community! What do you observe happening? And, please post an image of the audit log details as that may provide context for an problems. Kind regards, Bill

Hi @Dhoni Yes, and...to what Nic suggests: you may want to take this free JQL training from Atlassian on how to form queries and answer questions with JQL. https://university.atlassian.com/student/path/849533-gain-project-insights-through-jql Kind regards, Bill

Hi @Anastassia Ignatova -- Welcome to the Atlassian Community! The ANDs get processed before the ORs in JQL, so use parentheses to force the order of operation you want. For example, please try this: project = MYPROJECT AND parent = "Story number" AND ( summary ~ "Text one" OR summary ~ "Text two" ) Next, the CONTAINS…

Hi @Isma LABBOUR Here is the suggestion to make the "Story point estimate" field available in automation actions and conditions. You may watch or vote for it to see progress: https://jira.atlassian.com/browse/JSWCLOUD-22778 And, here is the Jira Cloud version of documentation to edit that field using a JSON…

Hi @Colin Fong How does the team know and how stable is the list of "what problems happen the most"? And when does the team associate a specific problem to an incident? Knowing that information may help the community to offer you additional suggestions for your reporting need. Kind regards, Bill

Hi @Diemunsch Jean-Baptiste To improve visibility of your question, I recommend creating a new question and then linking to this one. For your rule, I am not aware of team-managed project problems when you use the built-in branch like that. If instead you branch on JQL the smart values used are different. What do you…

Thanks for explaining, Willy. Perhaps give what Mark suggested a try and if you run into problems parsing the summary to set the sprint ID post images of your rule and audit log so the community can help further.

Hi! What I meant was to use the Create Variable action to store your formatted output, and then use that in the email. Please look here for information about that action: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-variable

Whew; that is good learn it wasn't a chart side-effect! Perhaps check your automation rule to see if a condition is missing/needs improving to prevent this...or how to deal with it on the chart (e.g. quick filter to exclude some issues).

Yup, as I helped with another question using ...split("\n")

Hi @Sean Elliot -- Welcome to the Atlassian Community! I have not observed that symptom before and I didn't see that as a defect in the public backlog for Jira Cloud. Have you checked the issue history for those items to confirm that they were not in status values covered during the timeframe/filter criteria for the…

Hi @Leonid Danilenko First thing, I am just another customer and not with the support team... There appears to be a larger scale outage for several hours, and you can follow the status/get alerts on it here: https://jira-software.status.atlassian.com/ Kind regards, Bill

Hi @Charles Cain What have you tried thus far to implement this, as this may be implemented using the Issue Transition trigger, some conditions (if needed), and an action to edit the field? And, is "End Date" a custom field you have added as there is no built-in field with that name? To help you get started please review…

Hi, @Darryl Lee Well done! You note this only works for the first red-markup found. I wonder if you could nest the iterators to handle any multiples...assuming the comment has at least line breaks between the to-do items. Basically add another iterator which splits the comment on line breaks, inside of the comment…

Hi @Willy Picard -- Welcome to the Atlassian Community! To clarify a bit, what problem are you trying to solve by doing this type of sprint assignment to the Jira issues? And, how would you see this approach impacting the team when they later use sprint planning prior to sprint start? Thanks and kind regards, Bill

Hi @Juliette Lallement _Elements Apps_ 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, Emma. As your team is using Scrum you may have that information already: consider the requests as the team has received them and look at all of the work to complete items, and how that is managed and split today. Then compare that to what your velocity and sizing instead indicate is happening. Such conversations may…

Yes, and there are at least two ways to do this with automation rules: 1) Use Lookup Issues and change the JQL to filter on the desired status, and store the pre-formatted results in a created variable...including line breaks. Repeat that, making multiple Lookup Issues calls to store the results in different variables.…

Yes, it is the third thing I noted: smart values... When using Lookup Issues, the scope is the lookup, and so you do not use the {{issue... or {{triggerIssue... prefix. Instead just reference the attributes like this: {{#lookupIssues}} * {{url}} {{/}} Please adjust that to the format/markup you wish.

Thanks for clarifying your use case, @Liron Bdolach If the rule is not triggering and it is initiated by all manual/user actions, something else is happening. Would you please post an image of the audit log for this rule, showing any details/errors? And would you please confirm: Are all of the issues for this rule (epic,…

Thanks for that information. In your JQL the closest you may get is using the CONTAINS operator ~ and not necessarily finding an exact match. For your rule, your JQL should compare to the trigger issue's summary: project = NFME AND summary ~ "{{triggerIssue.summary}}" Please also note: this rule is trying to reference…