Bill Sheboy Expert

Hi @Aleksey Midenkov -- Welcome to the Atlassian Community! You are correct that the asJsonObject() function must have the context of some object to work: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-json-functions/#asJsonObject-keyName- And...once the rule is inside of an iterator, only the…

Well done!

Hi @Jason There is currently no way in automation rules to solve the out-of-order issue. The reason is that solution uses branching, and branches on more than one thing are run in parallel and asynchronously. In fact, there is no guarantee of when the branch will complete, up to the very last step of the rule. To learn…

Hi @Martina You are missing the minus sign in that JQL that Brandon suggested, and so you are instead checking 21 days in the future. :^) Please try adding it. Kind regards, Bill

Hi @Max Boerma When using the Issue Created trigger, that can fire very quickly...much faster than the rule has access to the issue's data. This effect can cause conditions and other actions in a rule to later fail / not work as expected. The work-around for this is to *always* add a Re-fetch Issue action immediately after…

Hi @Oleksandr Tymofyeyev Two things could be happening... * In your description field, are those field labels in fact bolded? If so, the markup needs to be accounted for in your regular expression, with escaping for the asterisk:* match(".*\*Effective date:\* ([0-9]{4})-([0-9]{2})-([0-9]{2}).*") * Please adjust accordingly…

To use that action, you must enter something. The original question for this thread was to add watchers based on mentions in the comments. And all of the rule logic suggested up to this point was so the smart value can be entered in the Add Watcher action. If you now want something else, I suggest creating a new question,…

Hi @Dmitry Alabyan Rule actions like log work are based on the "current issue", at a specific point in a rule. Have you tried branching to the issue to which you want to log time? Kind regards, Bill

Hi @Martin Lopez Here are some questions to help narrow this down a bit: * What type of project is it: company-managed or team-managed? * What type of board is it: Scrum or Kanban? * What is the board's filter? * Please show the board configuration, with the mapping of status values to the board. Is your missing issue in a…

Hi @Emilia Mehr -- Welcome to the Atlassian Community! How many is a "large number of employees" and how many Jira issues are there in the project backlog? If you have fewer than 100 Jira issues, you could create a notification using an automation for Jira rule. If you have more than 100 issues, a rule cannot handle that…

Hi @Kim Barry First thing, I am using Jira Cloud and not Server/Data Center and so my suggestion is based on general knowledge of automation rules. For the comment information, I believe you can use {{issues.comments.last.author.displayName}} https://confluence.atlassian.com/automation/smart-values-993924860.html If you…

Hi @Quang Bui Nhat Within a Jira project, a board is a view of issues based on a saved JQL filter. And so you likely have 3 different JQL filters for your three different boards. To make your rule work, when creating the issue in the rule ensure the field values make it visible to target board's filter for Sourcing. To…

Do you see the red exclamation mark in your action to Add Watchers? There is something wrong with that action. Please review that to find the problem, and if you are unable to find it, post an image of your Add Watcher action so the community can try to help. Based upon your rule, you should be using the Variable Name…

There is a rule action to Create Variable, which may be used to temporarily store a value for later use in the rule: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-variable For your scenario, it could be used to save the created issue keys in a known manner, and the referenced later. To…

Awesome; I am glad to learn that helped!

Please describe how it is not working as you expect. To provide more context, please post an image of the audit log details showing the rule execution when it does not work as you expect. And did you see my comment about the condition test on Issue Type is epic? As that is only in the first condition, it is possible…

Hi @jan.ambroz The answer depends upon how many linked issues you expect: More than 100 issues total: try the multiple rule approach suggested by @David Blank Fewer than 100 issues... * Using JQL to find the children of the Epic, call Lookup Issues * Using a created variable, you iterate over the results of the lookup to…

Hi @Mayuresh Athalekar That is not possible with the out-of-the-box JQL features. Your work-arounds for this scenario depend upon your frequency of use and willingness to purchase addons: * Need this one time: export your issues to a spreadsheet and join on the parent field in that tool * Need this often: investigate the…

That second image's version will not work without the iterator as it provides the list...leading to {{index}} working. The original example from the post will work... * Please copy the smart value expression you are using to create varLoopValues and post that complete expression as text. * Then please show the smart value…

Yes, I think I got that, and...context is key. Instead, I was noting having 2 dashboards: * If you build a report dashboard which always shows "last week" relative to now, it would be from whatever last Tuesday was until this current week's Monday: 22 August -- 28 August, inclusive. * When you want a report for "this week"…

Are there line breaks / newlines in your source text, or multiple possible matches per line? The match() function does not handle those well, particularly when there are multiple results in a single search row. One work-around is to first force line breaks (or list item breaks) at possible match boundaries, and then use…

Hi @Chris Nemarich -- Welcome to the Atlassian Community! Yes, and...to the suggestions from Dave and Jack: What does the team plan to do with that information in the label field? Hopefully it is to use this info as part of retrospective conversations, helping to create experiments to improve how the team works together.…

Hi @Mourad Siala This seems to be a duplicate of your other question, linked below. Please close out this one to help the community focus on one thread. Thanks! https://community.atlassian.com/t5/Automation-questions/How-can-I-automate-the-creation-of-Sub-tasks-with-a-list-of/qaq-p/2461720 Kind regards, Bill

Hi @Mario Palacios Fernández Yes, that is possible, and...what do you mean by child issues? If you mean the subtasks of a parent issue, they are already in a list in the parent, and so min can be used directly on that list: {{issue.subtasks.someField.min}} If instead you mean another parent/child relationship, like epics…

Hi @Sanjivani Wayal Adding to Stefan's answer: If you can write a JQL expression to find the issues, you can use the Lookup Issues action in an automation rule...and then easily find the maximum value for a field: {{lookupIssues.someField.max}} Please note this only works for numeric and date values. To get the last…

Hi @Moriarty Chiu There is a certain way to do this, and a "I wonder if this will work..." way. Certain to work: * After you create each task, immediately save its key in a created variable, such as varFirstTaskKey set to {{createdIssue.key}} * Use those later in your issue linking updates as {{varFirstTaskKey}}, and so…

My mistake: the rule is trying to "help" by using the precision from the left-most value in the expression. We can force this like this: {{#=}}ROUND({{issue.created.diff(now).minutes}}/1440,3){{/}} Please adjust the 3 in the ROUND() call to your desired precision.

Hi @Justin Princehorn JQL is not a SQL, and so is quite limited and specific in its syntax. JQL's purpose is to find Jira issues, and so (in general) all the left-side things need to be an issue field. Like this: someField someOperator someValue And, startOfWeek() already accounts for "now"...or it could not know which…

Hi @Ayush Ghuliani If you provide images of your automation rule and audit log details showing the rule execution, the community may be able to suggest improvements to send one versus the many emails you note. Kind regards, Bill

Hi Chelsie, Would you please show the automation rule details, including the action where you are using the match() call? That context will help the community to offer suggestions. Thanks! Until we see that...my understanding is the regular expression parsing for automation rules is based on Java's Pattern class but they…