Bill Sheboy Expert

Good to know, and a temporary work-around could be: create an automation rule triggered on creation of an epic, and set the needed fields, such as copying the summary to the epic name.

Hi @Richard Martin -- Welcome to the Atlassian Community! How your team normally refines requests may guide your answer. For example, I have worked with product owners who were exceptional in the product space and did not know what to look for in application code. Others have been quite knowledgeable in all areas of their…

Hi @Kit Friend No, I had not tried that scenario...and it failed for me also. I had to explicitly delete the space after the first mention to create this condition. One work-around is to always ensure there is a space before the mention text and then split: {{issue.comments.last.body.replace("[~accountid","…

Hi @JulianaLTanaka -- Welcome to the Atlassian Community! You describe wanting to send reminders for "stalled" issues and to only send one email per assignee. Is that correct? If so, consider splitting this into two steps: gather the assignees, and then notify them. Perhaps like this: * trigger: scheduled with no JQL *…

Hi @Vamsi Krishna Panthulu Please look at an example issue and view the history. That may show what/who is adding the watcher. Kind regards, Bill

Hi @Artattack Group Srl Yes, and...to John's suggestion: specifically split that into 2 conditions, where one tests the trigger issue is in an open sprint and later test test subtasks' status values in the branch (or outside with JQL). Kind regards, Bill

HI @Yatish Madhav Yes, and...to Mark's ideas about using a global/multiple-project scope rule: You appear to be on a Standard Jira cloud license. Is that correct? If so, there is a limit of 500 executions per month with global/multiple-project scope rules for Standard license. If you expect that you will need more consider…

Hi @Hellen Braun -- Welcome to the Atlassian Community! Due to the GDPR changes for privacy, you can no longer use just the name to set a user field. Instead you need the accountId value: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Single-user-picker-custom-field Two possible…

Hi @Andrea_Lawrence In your first scenario, how are you selecting/creating the first 4 subtasks? Knowing that may help provide ideas on alternatives. Thanks! Kind regards, Bill

You may want to submit a ticket to Atlassian support to learn if this is a known issue, perhaps with a work-around: https://support.atlassian.com/contact/#/

Thanks for clarifying. Two approaches to try are: * to iterate over the watchers in a branch and use a condition to skip the initiator (when found) before sending the email, or * iterate over the watchers and use smart value, list filtering to skip the initiator. This would create a list of just the email addresses to use

Correct, as I was noting this creates the project and the key generation would be independent of that. Please see the other response for generation of a key.

Nope. I believe the limit is 100 items and then paging must be used with repeated calls. And when processing many items it is possible the rule would run into one of the service processing limits for automation rules, and so halt. When you are trying to make a bulk change like this with an automation rules, one approach is…

Was the problem which issue was the source (current vs parent) or something else?

Hi @roberto -- Welcome to the Atlassian Community! Yes, and...that option did not exist originally for rule actions. Instead the changelog was needed to address this. Kind regards, Bill

Hi @Ste404 The REST API documentation says this can only search within the first 1000 users, and I believe the default is to return 50 users: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-user-search/#api-group-user-search Have you tried using the maxResults parameter to pull back more? Kind…

Hmm...Would you please post images of your complete rule (including the edit action details) and audit log details? Context is important for a symptom like this and so perhaps I am missing something obvious. Thanks!

Hi @Dr. Steve Whittle My hypothesis is this symptom is from the epic changes in Jira, where the Epic Name is sunsetting and the Summary is used instead. You could confirm that by contacting the Easy Agile vendor to learn what they display in the "title" field: the Epic Name or the Summary. Here is their contact information…

Hi @sgover Yes, and...to what Trudy suggests and asks: For your team, it seems that "build" and "deploy" are two different work-item types, with different definitions of done, based on what you describe. Some additional things to consider: * are releases just-in-time or cadenced on a schedule, and * who does the work of…

Hi @Tim van Boeschoten Please try adjusting your syntax to this one: { "fields": { "customfield_10095": { "value": "{{triggerIssue.customfield_10095.value}}", "child": { "value": "{{triggerIssue.customfield_10095.child.value}}" } } } } And also, note that smart values are name, spacing, and case-sensitive. I adjusted the…

Hi @Illia Ivanou -- Welcome to the Atlassian Community! As a reminder, this community forum is not a free labor pool to implement solutions. Instead it is a place for people to seek and offer help...And using automation rules often requires learning and experimenting to solve one's needs. That being noted: what have you…

Hi @Phil Bustin I believe to set a user field you need either the entire user object or the accountId attribute in the edit. For example: {{issue.reporter}} or {{issue.reporter.accountId}} Kind regards, Bill

Certainly, and...using automation rules is often about experimentation and learning. There really isn't anything in documentation that covers every scenario. Let's try Lookup Issues...In your rule, it appears to be triggered on one of your Defect-tasks. And so you could find all siblings with JQL such as this: project =…

Hi @Richard Romero You can do that either using Lookup Issues with a JQL filter or with smart value, list filtering and a math operation. Here are some references to help you try those methods: * https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues *…

Hi @Cesar Amores -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this, as summing two date fields does not make sense to me? Instead is one of the fields a date/time field and one of them a number field of time units? If so, you can add the number to the date/time field by using the…

Hi @Carolina Fumarola -- Welcome to the Atlassian Community! What do you want the rule to do when the current date is... * before the 20th of the month * equal to the 20th of the month * after the 20th of the month As you appear to want to set the Due Date field, setting the date in the past (or without enough lead time),…

Hi @Samuel Smiles P Please review the documentation for that REST API function as it describes what is needed for the key attribute: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-projects/#api-rest-api-3-project-post If instead you are asking how to make the new key unique when you create the…

Hi @jiraadmin There was a problem earlier with user management, and you may want to try again and watch the status pages for progress: https://jira-software.status.atlassian.com/ Kind regards, Bill

Hi @Darren Mason and @John Funk Another approach for your scheduled trigger rule to flag the earlier issues is... * trigger: scheduled with JQL to find any issues left to update (i.e., meet your criteria and are not yet flagged) * action: lookup issues on more JQL to find any of the predecessors creating blocks * advanced…

Without the log I am unclear what to try next. You could either wait to see if other community members have suggestions, or work with your site admin to submit a support ticket to Atlassian to take a look: https://support.atlassian.com/contact/#/