Bill Sheboy Expert

If you compare the log to the rule steps, you will see the Task issue create is failing. And so the created variable is empty as there was no issue created. Please review the image of that action as I suspect it is trying to set the parent, but it should not for your scenario. Setting the parent should only happen for the…

Thanks for the additional information, Ivan. If I miss responding to one of your questions / ideas, please let me know... First thing, I would not assume when an automation rule action does something that it is identical to the Jira UX features. This is certainly true for issue create, clone, move, etc. Next, automation…

Interesting...based on what you describe, and again without seeing your rule, I suspect the branch's parallel processing was causing the symptom. Regarding detecting the trigger type, you may try the {{eventType}} smart value to infer…

No, I do not; I have not used any marketplace apps for calculated fields. You may search here to learn what is available: https://marketplace.atlassian.com/

Hi @Ivan Guillermo Seligmann -- 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…

Yes, that is correct: remove the branch to make the rule look like this: * trigger: issue created * action: re-fetch issue * action: edit issue, copying Intake Category from parent issue. But based on your original question, do you only want to do this when the parent's value is "OP" or copy whatever is in the parent?

The create variable action looks correct. There is a log action which allows writing text to the log: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Log-action If you write that variable to the log after it is created that may help. Perhaps something like: the clone key is: {{varCloneKey}} If…

Hi @Saili First thing, how are you linking Epics to their child issues: using the built-in mechanism with the parent field in the child issues or some other way (e.g., with issue links)? The two rules you show indicate both methods, and so I hypothesize your existing rules do not work as you explain. Back to your original…

Hi, Casey. Have you tried using the "Copy from parent" option for the field in the edit action?

I just tried again and creating a subtask with a parent specified by a variable still works. Two things to check: * Before you try to create the issue, write that created variable to the audit log to confirm in contains what you expect * If it does not, please post an image of the Create Variable action where you create it…

Ah...this is one of those cases where the automation's parsing order seems to be preventing getting the value before the function call to get()...and so the value passed to the function was null. The same thing can happen for dynamic fields, such as those from marketplace addons, linked issues, etc. What you did is a…

It appears the entire array is being interpreted as one item. You could make the text parsing a little easier by initially splitting on a known attribute, such as "author", and then using match() and split again to get at the reviewers as a list. Regarding the conversion function, that is not available yet. I recall seeing…

Hi @Casey Meyer You could use the date-type fields to format them back into the JPD-date-type fields. That format looks like this, as an example: "customfield_10107": "{\"start\":\"2023-10-18\",\"end\":\"2023-10-18\"}" Thus you could substitute in your date fields, formatted with jiraDate, perhaps like this:…

Hi @Tomas Franco What are you observing in the audit log details that appears to be inconsistent? If you write the branch variable, {{DigitalProducts}} to the log, does it contain what you expected? Have you noticed any patterns to the inconsistency? For example, the issue edits work as expected but the issue creates do…

Hi @Alison Paddock Yes, and...to the answers from Trudy and Aaron: Once you navigate to the global list of automation rules, you may sort the list by Enabled to find those. Kind regards, Bill

Hi @Noah Müller Adding to John's suggestions... If this is the Category field for a Business Project, there is an open defect for this limitation in automation rules. You may watch / vote for it to see progress: https://jira.atlassian.com/browse/AUTO-803 The workaround to use advanced edit with JSON to set the Category…

Based on your experiment with just the author element, it appears this call's webresponse is returning arrays of values (with some as plain text) rather than nested lists. Or...that is how the rule is getting them in the Send Web Request action's response. You may be stuck doing the text handling, as you tried earlier. I…

When cloning the subtask, please set the Parent field, not the Epic Link field, to that created variable for the newly cloned Task.

Hi @Victor - Modus Create As a reminder...when recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Community online guidelines | Marketplace + Solution Partners | App Central…

Hi @Victor - Modus Create As a reminder...when recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Community online guidelines | Marketplace + Solution Partners | App Central…

Hi @Sidharth verma I believe the answer is "maybe" as it is not clear what does (or does not) work once the formatting starts getting nested. For example, formatting within table cells. One thing I have observed is some of the macros defined in the Description field editor cannot be implemented with automation rules and…

@Rees, Ian please see my earlier example. Once inside of the double-curly brackets, there is no need to add additional ones.

Hi @Fede B. -- Welcome to the Atlassian Community! I see a typo in your outermost iterator, with a parenthesis instead of a curly bracket. Substituting that bracket, and adding the comma handling for the reviewer delimiting, is below. I added extra spacing to see it better, so remove that after you have it tested and…

Thanks for that information. I am not using the dev automation features of rules currently. From what you show, I believe you will need to extract the key(s) and then use a branch on JQL to access them. To do this, you will need to use the text functions to produce a list of keys, and then use JQL like this: key IN (…

It appears someone has created another Parent field, which will definitely cause problems. Please discuss this with your Jira Site Admin to learn why it was added because there should only be one. To use the system field in the edit, the dropdown makes it appear no value can be smart value entered. You may type in your…

FYI for @Tanguy Crusson in case this one has not been seen yet.

Hi @Steven Connolly -- Welcome to the Atlassian Community! I just reproduced that same symptom. When I checked the CSV file, Jira had already shifted the dates before export...so this is not an interpretation issue by the spreadsheet app. Specifically, it appears to be subtracting 1 from the "start" value in the stored…

What are the types of issues involved? Specifically, is the trigger issue a Story and the "parent" issue an Epic? What is the type of project: company-managed or team-managed? What is in the Create Variable action: * Is it a valid, Jira issue key? * Is it for an issue in the same project? * If it is not in the same…

Hi @Gokul Sukesan -- Welcome to the Atlassian Community! First thing, I recommend discussing this need with your team and coaches to learn how this type of work was managed in the past. That will provide insights into how this might be handled going forward. Ultimately, this may be based on what problem(s) your team is…

Hi @Majken Longlade First thing, as this is an older thread I recommend creating a new question, and perhaps linking back to this one for context. That will ensure the maximum number of community members see it to offer suggestions. Thanks! Back to your question... Yes, that is still possible. A rule which needs to update…