Bill Sheboy Expert

Well done; please remember to fully test your rule to confirm it works as expected. Regarding the challenges you encountered... For the first concern, one approach is saving data which is needed later and using the correct smart values. For example, by saving the newly cloned Epic's key in a variable for later use from…

Please post the expression you have in that edit for Status_Elapsed_WrkDays, as it is not fully visible in the image. Also reviewing your log again, I see your diff() call is trying to use a units of measure of "wrkdays". That is not a valid unit for the function; you could use businessDays instead to count weekdays.

First thing, please try to stay with one thread when responding. That will help others reading this question in the future know if there are multiple solution approaches. Thanks! You describe the QA User(s) field is multiple-select, but there can only be one Assignee user for an issue. How do you know to whom the new issue…

Hi @Alexandra Wilson Rather than using advanced edit with JSON, you may select the Assignee field from the dropdown list in the Create Issue action, and then type in the smart value for the field. For your source field, is it a single-select user field? If so, you may enter this:…

Hi, John! Would you please post an image of the edit issue action, and the text of the smart value expression, which lead to that error? As it shows in the audit log, it seems there are literal values in the expression rather than valid smart values, and that does not work for date functions in rules. Thanks!

Hi @Jenny Luther What problem are you trying to solve by doing those things? That is, "why do that"? Knowing that may help the community to offer some alternatives. Until we know that... I believe both of those actions are possible, and I respectfully recommend not doing either one of them with automation rules when there…

Hi @Claudine Warren -- Welcome to the Atlassian Community! Either of those syntaxes look correct, assuming they are included with the rest of an issue update call and the field can be edited: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-put Have you checked…

Hi @Jenny Luther Not in the way you describe: those reports show any issues in the sprint. In my earlier post, I was suggesting an alternative to use the CFD report as it allows use of quick filters to change what is displayed for the time range...although that is for issue count and not the estimation measure (time or…

Awesome; I am glad you have it working! There are other open defects for Jira Data Center's use of created variables in functions, but not this specific case with minusDays(). You may want to ask your Jira Site Admin to submit a defect so Atlassian knows about it.

I wonder...please try setting vicDateDay to 4 explicitly with no calculation. If that does not work, it suggests that the minusDays() function for Jira Data Center cannot take a variable as a parameter. I looked and did not find this listed as a defect in the public backlog A longer version to try would be putting it all…

Where you write the smart value expressions to the audit log, try writing the variables instead: {{vicDay}}, {{vicDateDay}}, and {{vicDayFinal}} That will help confirm the variables contain what you expect. Also, smart values are case-sensitive, and I believe the attribute DayOfWeek should be…

Hi @Celina Kincaid What have you tried thus far to solve this? If you have a rule that is not working, please post images of the complete rule, the audit log details, and explain what is not working as expected. If you have not yet started a rule, some suggestions to get you started are: * Here is an overview of how rules…

No, I do not believe that is possible with Jira Cloud. Only archiving a version / release removes it from the dropdown lists, JQL suggestions, etc.

Hi @Rao Tripuraneni If you are asking about the built-in Fix Version or Affects Versions fields, I suspect the answer is: no. Those fields show all versions which are not archived, and I am not aware of other ways to impact the values shown. Kind regards, Bill

Hi @Janakiraman S 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 context for the community to offer ideas.…

Hi @Tilman Ulshoefer Yes, and...to Kalyan's suggestions: Branches which could be on more-than-one-thing are run in parallel and asynchronously, with no guarantee of when the branch will finish...up until the last step of the rule. This design helps quite a bit with rule performance, and requires us to think differently…

Hi @Jira Admin -- Welcome to the Atlassian Community! Short answer: no. That date field display on boards is a feature of business projects. I did not find any open suggestions to add it for software projects, so perhaps add one with "Give Feedback about Jira" under the ? / Help button at the top-right of the page views.…

Please post an image of your complete rule (in one image) and an image of the audit log details showing the rule execution. Those will provide context to help explain what you are observing. Thanks!

Awesome; I am glad to learn that helped!

Regarding the level of string manipulation, that depends on context. Outside of list iterators, the built-in functions offer quite a few options: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/ Inside of an iterator, some things appear not to work, which I hypothesize is due to scoping…

Hi @Felipe Perez _ServiceRocket_ That appears to be a known defect, which you may watch / vote for to see progress: https://jira.atlassian.com/browse/JRASERVER-72862 You do not describe how you are making that call to the REST API function: a custom app, automation rule, etc. One possible workaround (depending on your…

Thanks, and to have those two tables handled by a single rule, it could: * use a Send Web Request action to call the REST API issue search for the first table * preformat the HTML and save the results with a Create Variable action * use a second Send Web Request to get the results for the second table * send the email,…

Hi @Anna What problem are you trying to solve by doing this? Knowing that may help the community to offer alternative solutions. Until we know that... Created Variables are text. When you want to use them in a function such as minusDays() they must be converted with asNumber:…

From your response I am guessing you are using Jira Data Center, correct? Are your two different tables over the same issue set or different sets?

Hi @Jecynta Ogeto -- Welcome to the Atlassian Community! What version of Jira are you using: Cloud, Server, or Data Center? With Jira Cloud, you may split the values in the field and loop over them with an advanced branch. Please look here to learn more about that approach: *…

Hi @Bobby Williams -- 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…

Thank you for that information. First, the syntax for that type of JSON edit uses "update" and not "fields": https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Linking-issues Next, you describe the custom field contains a URL to the issue which is the target for linking. Thus you may…

Hi @Melissa C Unfortunately, the Lookup Issues action for Jira Data Center version does not support most fields yet, including custom fields: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 If it is of any consolation, when Lookup Issues was first added for Jira Cloud, it also only had about a dozen fields, and a year…

To confirm, have you solved your question by fixing one of the conditions? Thanks!

The rule editor does not always make it easy to see what is possible :^) In the Create Issue action for the parent field: * type in the smart value for your variable: {{subtaskvariable}} * it will appear below the field as you type * select it, and that will use it in the action for the parent