Bill Sheboy Expert

What is the type of the custom field you are trying to copy? And if it is a multiple-select option field, are you trying to add a value or replace all existing values during the "copy"?

Hi @Shreya Jadhav -- Welcome to the Atlassian Community! Jira Automation rules trigger after some event has happened, not before. Your rule would run after the issue is created...and so replace the field value. You seem to want template text in the Description field as a default. Please investigate other options to add…

You would either need to use the and() function to combine values or concatenate them, as I noted with the lookup tables. (One advantage of the lookup table is ease of maintenance for this scenario's complexity.) To use the lookup table approach, list each of the combinations needed, and then test the result with get() on…

Sometimes Data Center works differently than Cloud, and that is where I created those expressions. Let's try the simpler expression in the condition instead: {{now.diff(issues.first.sprint.endDate.max).days}} Also, please write the value of that expression to the audit log before the condition so we can confirm what it…

Hi @Vikrant Yadav First thing, as you appear to have multiple values to test, I recommend using a Lookup Table where the row keys are the concatenated values of the three fields and the row values are the desired value of field D. For example, a row could be key= YesYesNo with a value= 2. Or better still, the key could be…

Hi @Bharathi First, in your edit issue action, you are updating the same field twice: once with the field selection (from the dropdown list) and once with JSON. Only one of those may be used at a time. Next, your JSON update is referencing the smart value {{webhookData}} but the rule makes no calls with Send Web Request.…

Hi @Berit Pearcy -- Welcome to the Atlassian Community! That appears to be the rule list, and that column is the rule owners. Have you imported /migrated those rules from another site / instance where the original owners are different from your current site? Kind regards, Bill

Hi @VAlesbury -- Welcome to the Atlassian Community! Short answer: probably that can be done with Jira Automation. The key for a scenario like this is identifying the correct issues. If you only need to find the one Task with the latest Due Date, and have a way to identify the "first Task", the rule could use the Lookup…

Hi @Ayesha -- Welcome to the Atlassian Community! There is nothing built-in which would do that behavior. I recommend looking at some example issues with this symptom, and review their issue history to learn what / who is moving them to the backlog, and when that is happening. If that does not help identify the cause,…

Hi @Casey Gould The symbol Y is for the week-based-year and the y symbol is for the year-of-era. https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html Some usages need the year to be based on the whole weeks, Monday-Sunday, while others need the calendar year. And so the two could vary by -1 to…

Hi @Sateesh Dara This may be done with a Jira Automation rule. At this time, there is no smart value for the approvers in the Fix Version or Affects Versions smart values. As a workaround the rule may call the REST API with the Send Web Request action to get the version and its…

Hi @Malic Meyer -- 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…

Tania, I recommend pausing to identify the correct smart value (or custom field id) for your field using this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ Then, add a write to audit log before the branch to confirm what the field contains, and re-test. That may help…

First thing, when using the Issue Created trigger, it can fire so quickly that some data may not yet be available to the rule...potentially causing unexpected behaviors. The fix for that is to always add the Re-fetch Issue action immediately after the trigger, to slow down the rule and re-load the data: * trigger: issue…

Thanks for that reminder, and this edge case is a known problem. You may watch / vote for this defect to see progress on resolution: https://jira.atlassian.com/browse/AUTO-361 One possible workaround for your scenario is to call the REST API endpoint using the Send Web Request action. That will eliminate the need for the…

Greetings! For the JQL with the Lookup Issues action, I recommend using the exact phrase syntax for the CONTAINS ~ operator: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#CONTAINS---- project = yourProjectName AND summary ~ "\"{{issue.summary}}\"" AND key !={{issue.key}} ORDER BY created ASC…

I have limited experience with eazyBI, and so... I recommend you update your question to include that detail, and to check the documentation of eazyBI to help you.

Hi @Aftab_Akhtar When you want to increment multiple parts of the version number, you will need to implement the math using if / else conditions on the separate parts. For example, assuming your format of 24.1 as part of the version name: * action: create a variable for the left part (e.g., 24) using text functions* let's…

Hi @Bobby Moyini I believe that is possible for round-robin but not balanced assignment. (Balanced would attempt to re-assign to the same person.) The rule could make the assignment, check if it assigned to same person as the parent, and then re-assign. Perhaps like this: * trigger: ... * action: create issue (a subtask…

Hi @Ilya -- Welcome to the Atlassian Community! Assuming the trigger issue is your Story and the rule creates the Epic, you may connect them after the Epic is created: * trigger: issue created * action: re-fetch issue (I recommend always adding this action after the issue created trigger to prevent timing / racetrack…

Hi @Tania Schmittou You may do that by iterating over the selected values in the field. Please change the smart value expression for your branch to this: {{issue.customfield_16927.value}} Also, are you trying to create new issues and immediately transition them to a specific status? If so, I believe you will need to either…

That looks like a marketplace app to me, and not a built-in feature. Perhaps a replacement / addon for time keeping. I recommend working with your Jira Site Admin to identify the app, and then contact the vendor to learn what automation options are available.

Hi @Lori Surapaneni There appears to be an open incident for this now: https://jira-software.status.atlassian.com/incidents/lb04yjdct854 Kind regards, Bill

Hi @prasanna Subramaniam -- Welcome to the Atlassian Community! Yes, that sounds possible, and you will need to consider your scenario details to make this work... * You note tasks "AA", "AB", and "AC". How do you identify those tasks? That will be needed to find them. * You note wanting to assign both the parent feature…

Hi @suzanne_deasley -- Welcome to the Atlassian Community! What do you mean by "start timer for an issue"? What problem are you trying to solve? If this is a feature added by a marketplace addon / app, I recommend checking the vendor's documentation to learn if the timers can be started with automation rules, such as by…

Hi @Hannah Sorrell -- Welcome to the Atlassian Community! You could use text functions to extract the issue key from the URL in the custom field, and then use that in the Link Issues action: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/ For example, the issue link URL probably looks…

Hi @Dag Atle Stentad First thing, I recommend not deleting issues from Jira Cloud. There is no built-in "undo" or trash bin capability, and so mistakes are possible. Instead consider using a resolution value or custom field to indicate "abandoned" issues, and update filters / reporting accordingly. Then the "delete issue"…

Hi @PARISATO Marie-Hélène Adding to John's suggestions... Only some timing problems in automation rules may be solved using the Delay action (for premium licenses level) or the Re-fetch Issue action (for all license levels). Instead a change of rule design or approach may be needed. If you have a specific need to delay…

Successfully using automation rules requires learning and experimentation. I encourage you to try to create the rule (as you did for the first one), and if you run into challenges to ask for further help. You already have a rule which uses the Issue Created trigger. That could be copied and the trigger changed to Scheduled…

Hi @Carina Gungner -- 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…