Bill Sheboy Expert

Thanks for the additional details, and I believe you could use two rules to solve this: First rule, to add the clones, and don't worry about the Epic comment yet: * trigger: manual * condition: issue type is epic * action: lookup issues with JQL, to identify the issues which will be cloned; the sole purpose of this action…

I am still unclear why multiple rules are needed for your scenario. Would you please explain that? How is the second rule B using that saved key? If it is using it to create a link, the smart value can be entered for the key value when linking. A final thought: using the comments to pass data this way is generally not a…

Hi @Vishal Thakkur -- Welcome to the Atlassian Community! For scenarios like this, context is important. What would an example Description that contains your values look like? Knowing that may help to improve the parsing expression. Until we see that... Two things about the match() function could be causing challenges with…

Hi @Anton Zubets -- Welcome to the Atlassian Community! For a question like this, I recommend posting an image of the entire rule in one image. A browser addon (or app) for scrolling capture can help do that. Next, based on what your initial post described: I'm trying to implement quite a simple thing using Jira…

One challenge with linking created issues in rules is context: the definition of "most recently created issue" changes as issues are created, including more challenges if branches are used. To do what you describe, you may need to either save the issue keys in variables or use separate rules to add the subtasks. For a…

Hi @Adam Sadowski -- Welcome to the Atlassian Community! If there is a date field set in an idea, an automation rule could be created with a scheduled trigger to evaluate the date and make a status transition. For example: * trigger: scheduled every day at 1 am, with JQL to find issues with the date set, and in a…

Hi @Phil Skade Please review the math expression documentation as your rule appears to have some errors: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/ And also...Your rule's edit action has both selected the field from the dropdown list and is trying to update it with advanced edit…

Hi @George Cadena -- Welcome to the Atlassian Community! That information on assignees is in the issue history; it is just challenging to report on it with the out-of-the-box Jira features. First thing, I recommend chatting with your Jira Site Admin to learn if you have any reporting addons that might help. Next, there are…

Hi, Stefan! Based on my understanding, there are two types of branches... * Branches which are on one-and-only-one-thing. For example, branch on Parent, current issue, etc. These are converted to run in-line, and so the order of rule steps is sequential. * Branches that could be on more-than-one-thing. For example, all…

Hi @Zoe Harris -- Welcome to the Atlassian Community! First thing, this symptom appears to be a defect in the way automation rules handle list fields, like Fix Version, when using functions inside of iterators. There are similar community posts for the Sprint field. If you are on a paid Jira license, I recommend working…

Here is the documentation examples of iterating over lists: https://confluence.atlassian.com/automation/jira-smart-values-lists-993924868.html#Jirasmartvalueslists-examplesExamples For your rule, you would iterate over the field values, adding the necessary JSON to create the issue. Example pseudocode of that would be:…

If you want to update the feature, I believe the trigger / conditions should proceed if: * When the fields change in an Epic, update the Feature. However your condition is checking for a Feature instead. Try changing your condition to check for Epic. * Optional: if a user tampers with the values in the feature, you may…

Hi @Carol Wesolowski -- Welcome to the Atlassian Community! Your rule can be simplified to use the Lookup Issues action with JQL to find the sum. For example: * trigger: when transitioned to done * condition: issue type is Epic * action: lookup issues with JQL to gather the child issues for the epic * action: log, or use…

Hi @Penny Schenkkan What have you tried thus far to solve this need? If you started an automation rule and it is not working as you expect, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain…

Hi @Jake S For epics, the Epic Color field was sunset (even though the field is still there) and now the Issue Color field is used. That is what you are changing for the Epic. It appears the Issue Color field can be modified for other issue types, like Story, Task, etc., but it does not impact the Timeline view for at…

Thanks for clarifying, and... If you review the details of the Issue Linked trigger, it shows the {{issue}} (also referenced as {{triggerIssue}} ) and the {{destinationIssue}} can be accessed. For your scenario, you want your status condition on the trigger issue, and then branch to the destination issue to add the flag.…

Please re-test your rule after the changes which look specifically for the issue type id in the condition.

Hi @Rachel Godina -- Welcome to the Atlassian Community! I am not following your scenario, so perhaps you can clarify a bit. I believe you are asking: GIVEN issue A is in the Backlog status WHEN issue B links to Block issue A THEN issue A which Is Blocked By should be marked as Flagged If you can confirm we can consider…

There is an error indicating an attempt to set the Assignee during the transition to DEV COMPLETE. What is in that rule action in regards to Assignee? Next, I was asking to see the audit log for the rule as it was written before, and it appears you have changed to try to check by issue type's id. Please retest after that…

First thing, what does "percent completed" mean for your Feature issues? That is... If you only want an approximation based on the "percent completed" stored in the Epics, you could just average the values by adjusting your current rule: * gather the Epics with lookup issues and JQL * get the average value with…

Thanks for that information. Would you please post an image of the audit log details showing the rule execution when the condition does not match?

Yes, that is one of the big challenges with that approach and why there is the suggestion to make it more flexible (i.e., adjust the date). The current REST API functions do not support a change to a specific completeDate:…

Hi @Herick Carvalho -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide…

Hi @Endre Szekacs -- Welcome to the Atlassian Community! Context is important for automation rule questions, and there seems to be quite a bit happening in your rules. I recommend first posting an image of your complete automation rule(s), images of any relevant actions / conditions / branches, an image of the audit log…

Hi @Stefan Draber Short answer: I do not believe this is solvable with an automation rule. Other solution approaches are to investigate other planning tools or implement the issue updates outside of Jira, or an approximation rule (see below). More information...(apologies in advance for the long response :^) To do what you…

Hi @Lucas Ferreira That is not possible with current features, and here is a suggestion to add that capability: https://jira.atlassian.com/browse/JSWCLOUD-16331 One possible work-around is to re-open the sprint, and re-close it, although that may cause other reporting / work management issues if there are other sprints in…

Hi @Ruben It appears the integer typing follows through to the end of the calculation after the earlier use of the format() function. Please try using the longer form of the math operations when you want to manage the typing and significant digits: {{#=}}CEILING ( {{now.format("Q")}} / 2 ){{/}} Or... First create a…

Hi @Teja Does your Lookup Issues result contain all of the issues? If so, please try using the size list function, perhaps with a default value of 0: {{lookupIssues.size|0}} https://support.atlassian.com/cloud-automation/docs/jira-smart-values-lists/#list.size Kind regards, Bill

Hi @María Ferreño Serra Yes, and...to Valerie's suggestions: You may want to take this opportunity of the site instance split to improve documentation. For example, for apps which do not have built-in tracking, create your own change management process for apps, features, etc., such as in a Confluence space or Jira project…

Hi @Viresh Kumar Without seeing the audit log details for the rule executions, I hypothesize a couple of possible causes: * Your rules create issues, but do not first check if those issues already exist with conditions. Solution approach: add conditions. * Your rules have the "Allow Rule Trigger" option enabled, perhaps…