Bill Sheboy Expert

Thanks for the additional information, and please review the article again as it does not match your scenario. What that article does is: GIVEN there are Epics with child issues (e.g., Story, Task, or Bug) WHEN a schedule occurs (e.g., once per week) THEN for each Epic, update the Epic's Start Date to the minimum value for…

Hi @wiwan -- Welcome to the Atlassian Community! First things first: I estimate this question / scenario is asked about 2-3 times per week in the community, with many responses over the years. And that article you note covers a very narrow scenario to update a parent issue for changes to a child issue. It does not cover…

Hi @Zsigmond Molnar Short answer: a created variable is plain text and cannot be parsed as JSON. Here is a suggestion to add that feature: https://jira.atlassian.com/browse/AUTO-138 If you want to store the information you show in a created variable, text and list functions would be needed to parse it, and possibly use the…

The workaround is to create the Jira Automation rule from its global rule management area, not from GitHub.

Hi @Daniel Nagornov -- Welcome to the Atlassian Community! This appears to be an intermittent defect, as described in the report below, and which is closed as "won't fix". The suggested workaround is to have your Jira Site Admin create the rule from the global rule area in Jira. https://jira.atlassian.com/browse/AUTO-643…

Awesome; I am glad to learn that helped! Earlier I noted either iterating or summarizing the results of the lookup. And so outside of the iterator, the summarizing could be done. For example: {{#lookupIssues}} * {{key}} - {{summary}}: {{#=}}ROUND({{Story points|0}} * {{customfield_11965|0}} / 100, 2){{/}} {{/}} Total Story…

Hi @Matthias Schulz -- Welcome to the Atlassian Community! Another possible approach would be to use the REST API to get all the components, and then create a CSV import file to create the issues. That has a limit of up to 1500 issues and Atlassian will manage the throttling behind the scenes (over about an hour, according…

Please try removing the quotation marks around the email address in the Second Value condition. When the First Value in the condition is this {{issue.watchers.emailAddress}} that will produce a comma-separated values list like this, without any quotation marks around the entries: firstEmailAddress, secondEmailAddress,…

Reminding you of my first post about the parallel and asynchronous processing nature of branching, I recommend not trying this scenario with the Scheduled Trigger you show. The documentation does not state if the processing of issues from a Scheduled Trigger also executes in parallel, and I hypothesize it does. Which takes…

Sorry, I just noticed you are using Jira Data Center. I believe Epics can only display on a Kanban board for that version.

Awesome, and well done!

Hi @Test That -- Welcome to the Atlassian Community! Is the Sprint field set for the Epics? If not, they will not display on the board as issues. Instead, they may show as indicators on each of their child issues which are in the sprint. Does the Components field for each Epic contain "Backend" as that is part of your…

FYI...with the Scheduled Trigger approach, if you need the updates sooner you may open the rule in the editor and select to run it now rather than waiting for the next scheduled run.

Using the Advanced Branch over the distinct values, it would send one message to each team using their URL. I believe you already have the rule outline. If it is not working as expected, please post the following to help identify the cause: * an image of the current, complete rule in one single image * an image of the…

Hi @Vincent Parenti -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule, * images of any relevant actions / conditions / branches, * an image of the audit log details showing the rule…

Hi @Urmo I believe you want the internal attribute for the comment: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--comment-- Kind regards, Bill

Hi @Rosalind Bird -- Welcome to the Atlassian Community! First thing, smart values are name, spacing, and case-sensitive. When an incorrect one is used, that evaluates to null, often failing to work as expected. The smart value for the display name of a user is displayName, as in {{issue.myCustomPeopleField.displayName}}…

Hi @Vasilis Kokotakis Are you trying to use this one where groups is plural? It is singular in your URL. https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-groups/#api-rest-api-3-groups-picker-get Also, if you are querying for all of them, consider removing the query to do that. Kind regards, Bill

Hi @Maurice B. First, smart values are name, spacing, and case-sensitive. When an incorrect one is used, it evaluates to null, often leading to expressions failing to work as expected. The smart value for the lookup issues results is {{lookupIssues}} Next, the result of a Lookup Issues action is a list of issues, with…

Hi @Gabriel Aklin -- Welcome to the Atlassian Community! This is a known limitation for rules, and here is a suggestion to allow Project Admins to see the security levels for the rule action: https://jira.atlassian.com/browse/AUTO-1055 Kind regards, Bill

Hi @Bernhard Mostrey -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule, * images of any relevant actions / conditions / branches, * an image of the audit log details showing the rule…

Hi @Abdur Rehman -- Welcome to the Atlassian Community! When using the Lookup Objects action, that loads the results in this smart value: {{lookupObjects}} Followed by the attributes needed. Did you intend to use the results of the lookup in one of the later rule steps, such as the plusYears() function call? Kind regards,…

Hi @nora.demeter -- Welcome to the Atlassian Community! Do you mean the Summary field cannot be removed from most of the view types (e.g., list, board, etc.) in a Jira Product Discovery (JPD) project? If so, that is likely by-design as it is the one piece of information to summarize / identify Ideas in a human-readable…

Hi, Tim -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in one single image * an image of the full audit log details showing the rule execution Until we see those... Some rule actions can…

It seems you want to send one message per team with their issues. Is that correct? If so, I recommend changing the Advanced Branch to use this smart value. Please replace customfield_12345 with your field ID. {{lookupIssues.customfield_12345.value.distinct}} This will find each unique team value, once per team, using…

As written, I am unclear what this rule is trying to accomplish as it only ever tries to update the trigger issue. Regardless of that... The get() function for the {{lookupIssues}} smart value only takes an integer as a parameter. I recall there are open defects about several automation functions not accepting variables as…

First thing, to get you started on creating your rule, please refer to these documentation and example sources: * https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation *…

FYI regarding others asking about this scenario, here is a post from yesterday showing more details of the expressions involved. Turned out it did not take two searches to work. https://community.atlassian.com/t5/Jira-questions/Re-Combine-multiple-values-selected-in-LookupTable-into/qaq-p/2923876/comment-id/1083366#M1083366

Glad to learn it worked, and thanks for catching the typo! I updated my post so it is corrected.

Thanks for filling in the details I left off, @Dick Teamwork makes the community work! And, I have not tried with Atlassian's interpretation of JSON for automation ;^) if sending that type of update as an array will work with either the "add" or "remove" actions. I have always assumed it would not work (same as I do for…