Bill Sheboy Expert

Ray, please try to stick to one thread when responding. That will help others in the future know if there are multiple answers to a question. Thanks! Would you please explain what problem you are trying to solve? I suggested a method to format numbers stored in fields/smart values as text with left-padding. However if you…

Hi @John Young Did you supply JQL when you called it in your first example, as those results seem to be from another endpoint? Please look here to learn what is possible with the issue search using JQL one: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-get Kind…

Hi @Sean Aguilar -- Welcome to the Atlassian Community! I assume your team is using Kanban practices and a Jira Kanban board. What you describe is often called Queue Replenishment, and I suggest learning more about the manual / people steps involved in that practice before automating it as doing so may remove some of the…

Ah, I just noticed the rule trigger is Issue Created... That trigger can fire so fast that the issue data is not yet available. This can cause conditions, actions, and other things to work unexpectedly due to missing data. The work-around for this is to always add a Re-fetch Issue action immediately after that type of…

Hi @Bartlomiej Bukowski Until a sort option/function is added to lists, we cannot rely upon first and last for a scenario like yours. (The exception is when you do have a sort, ORDER BY, for things like lookup issues with JQL.) For your scenario, let's assume your newest sprint is the one which ends the latest. If that is…

Certainly, that is possible. When the rule triggers on sprint created, you can use JQL to find the relevant issues...and that could be filtered by the status. * trigger: sprint completed * action: lookup issues with JQL to get the issues not completed and in that sprint * action: send emails, to others as needed, with all…

Hi @ray Are you asking about text fields (or output) or number fields? I text fields, that is possible, but it is not possible to store a number field as the leading digits would drop when saved. Let's assume your output is either a text field or output to the log, email, or a text field... I believe if you use the inline…

Hi @Cyril James There is no "canned report" for that, although you have a few options... * If all of the recipients are Jira users, you could create a saved JQL filter, and allow people to subscribe to it, on the schedule of their choosing. To learn more about subscriptions, please look…

Hi @Mandar Bhome -- Welcome to the Atlassian Community! Does your team/Jira site already have some form of integration (e.g., from the Atlassian Marketplace) with Salesforce or ServiceNow? If so, please investigate that for supplying information to the Jira issues. If not, how do you know what data should be selected and…

Hi @Rasneet Kanwar Yes, and...to Trudy's suggestions: I just tried this with a team-managed project and {{issue.parent.summary}} works as expected for the parent epic of a story/task/bug issue. Please also post images of what you have in your Edit Issue actions to confirm your smart values. Thanks! Kind regards, Bill

Hi @Gregory Tampagaris I believe the Story point estimate field is a number field, as the error message indicates. Please remove the quotation marks from the number value in your JSON for the advanced edit. { "fields": { "Story point estimate": {{lookupIssues.Story point estimate.sum|0}} } } Kind regards, Bill

Hi @Ayush Ghuliani The fix version field is a list of values, and the rule needs to handle that accordingly. And to use the membership IN operator the list of values needs to be in parentheses. Finally, do any of your fix versions' names contain spaces or special characters? If so, the names need to be wrapped with…

It appears you have already marked the responses/threads as "answered".

Hi @Mark Segall I believe if the Fix Version names have any spaces or special characters, that will not work unless they are wrapped in quotation marks. Perhaps something like this instead: fixVersion IN ( {{#issue.fixVersions}}"{{name}}"{{^last}}, {{/}}{{/}} ) Kind regards, Bill

The date/time functions like startOfWeek() are for JQL only, and not smart values in a rule. In a rule, you could instead try one of these to find the Monday for the current week. * {{now.withNextDayOfWeek("MON").minusDays(7)}} * {{now.withDayOfWeek(1)}} Next, when you note the nesting of {{#worklog}} ... {{/}} did not…

Hi @Arto Kovalainen Thanks, and...Advanced branches, as you are showing, were added after this question was originally posted. As more features are added to automation rules I expect many questions' solutions / work-arounds will be superseded by newer approaches. Kind regards, Bill

My mistake, as I thought you had another path/case for when tasks were created without an epic. I updated the rule I suggested to simplify it, removing that extra part. Please compare and update your rule accordingly and re-test it. Thanks!

Awesome; I am glad that part is working for you! To detect an issue (i.e., child) being removed from an epic, you can try the generic Issue Updated trigger, and then check the if the changelog is different for the epic link field with and advanced compare condition: * first value: {{#changelog.Epic link}}{fromString}}{{/}}…

I do not believe you can do that in the scheduled trigger's JQL; specifically, I do not believe that JQL can be dynamic. Instead I was suggesting to allow the rule to fire more often than needed and then use an advanced compare condition to limit what gets processed, such as by your timeframe/week information in the issue…

Well done; I am glad to learn you have something working. You could use that same length test technique for assignee and reporter if you want to be consistent. And...sorry about that as I copied from the incorrect version that still used exists() when I fixed the watcher issue; I updated the above post to the one I know…

Hi @Ylan Muller As you can read in that documentation page, the custom field formulas are helpful and a bit limited in the math operations supported. I expect other capabilities will be added over time for those operations. If what you want to calculate cannot be done with custom formulas it is likely it can be done with…

Let's add some Log actions to write things to the audit log in the middle of the rule. Hopefully that will pin things down: * trigger: your trigger (no change) * action: log for this value...This should write the selected value. Here is the Business Value selection: {{customfield_10298.value}} * action: log for this…

Awesome; I am glad to learn that helped! Please consider marking this question as "answered" as that will help others with similar needs find solutions faster. Thanks!

Gotcha; that cannot be done inside of that branch, as an edit would try changing the linked, epic the rule is branching-to. Instead, you can do this after the branch: * action: lookup issues with JQL to find that same epic* component = "{{Shop}}" AND issueType = Epic * advanced compare condition: to ensure the lookup found…

Hi @lucie.x.mcfarlane -- Welcome to the Atlassian Community! No, because an automation rule cannot stop processing to wait for user input/issue selection. As an alternative, you could create a filter on the labels, have the user select the one they want to view it, and then run a manually triggered rule to create the…

Hi @Shirley He -- Welcome to the Atlassian Community! You can get close to both of those types of queries with JQL, and you may learn more about JQL here: https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-939938733.html For example, you can check if someone was mentioned in comments, but checking the…

Thanks for the rule images. I do not believe you need those Re-fetch Issue actions as the rule is not changing anything...and I do not see anything else in this rule that could produce timing problems. Would you please post an image of the audit log details showing the rule execution, and explain for that case what is not…

To get the name, please try adding the displayName attribute. The default attribute for user fields is the accountId, as that is needed for most operations. So your value for the email, inside the lookup iterator, would be this: - Author: {{worklog.Author.displayName}} That would be the list of worklog author, names. And…

Thanks for that information...and I am fairly confident your conditions may be the problem. If you post images of your condition details I can confirm that. What you show leads me to believe you have this in a condition: {{pullRequest.title.toLowerCase().indexOf("draft")>0}} That is invalid, as the greater-than sign is not…

Hi @Jack Brickey Interestingly that branch type is available in rules even when JSM is not available, like in my free Jira Cloud instance. I wonder if there is some crawling process that needs to happen (once similar is enabled) before the results are returned. Kind regards, Bill