Bill Sheboy Expert

Short version: it appears your scenario has uncovered an apparent defect in automation rules with JPD idea / issue edits and multiple-project scope rules. There are known limitations with JPD and automation rules, but this one is not listed. I recommend working with your Jira Site Admin to submit a defect here to learn…

Hi @Miro Noordzij -- Welcome to the Atlassian Community! Some additional information if you try the automation rule suggestion from Charlie: You appear to be on a Free license level for Jira Cloud. If that is correct, there is a limit of 100 emails / 24 hours for the entire site for that license level. That includes all…

If there is no audit log entry, the rule did not trigger and run...making it challenging to diagnose this further. I recommend working with your Jira Site Admin to submit a ticket to Atlassian Support. They may see something we are missing. https://support.atlassian.com/contact/#/ When you hear back from them, please post…

Hi @Daniel Capps You appear to be using Jira Server or Data Center version. The symptom you see is because the rule trigger has the bulk-handling option selected: "Process all issues produced by this trigger in bulk": https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html But...your…

Which project is JPD and which is JSP? Knowing that will confirm if the triggers and link directions are correct. Why did you change the branch on linking from "implements" to "relates to"?

@caglad please try to stay in one thread when responding. That will help others reading this question in the future know if there are multiple solution approaches. Thanks! Please post your complete automation rule, in one single image. That will provide context for where the Create Issue action is happening within the…

It appears someone linked together two JPD ideas with the "implements" link type: PORT-37 and PORT-300. Thus PORT-300 is also found by the branch, and JPD ideas do not have the JSP field, Business Value Outcome, leading to the rule error. Ways to address this are... * As the "implements" and "is implemented by" links are…

For your question about custom field visibility in the admin functions... JPD appears to be built upon the same technology as team-managed projects (TMP) and so their custom field configuration is distinct for each project and does not appear in the global settings. As an aside... This behavior sometimes causes confusion…

Thank you for that information! As the JSP field customfield_10138 is a radio button, it will return the text of the selected option with either of these: {{issue.customfield_10138}} or {{issue.customfield_10138.value}} Does your JPD custom field customfield_10565 have exactly the same options as the JSP one? If not,…

Hi @McKenna Hogan What you describe is not possible with out-of-the-box JQL features. That is, querying an issue's parent's fields which meet certain criteria to find the child issues. You will need a marketplace addon for JQL to do this with a query. The parentEpic() function returns the child issues associated to an Epic…

Hi @Selena Peri First thing, I note Edit Issue action appears to have the "Business Value Outcome" field selected from the dropdown list and updated using JSON (using its custom field id). Only one of those methods may be used for a specific field at a time in a single edit. Please try removing the JSON and pasting the…

Hi @MR -- Welcome to the Atlassian Community! Is this question regarding the new AI feature for rules which is in Beta: https://community.atlassian.com/t5/Automation-articles/New-AI-feature-in-Beta-Natural-Language-for-Jira-Automation/ba-p/2651640 If so, I recommend contacting Atlassian support for assistance through your…

Hi @caglad Please post an image of your complete rule and the Create Issue action. These will provide context to compare to the audit log details you show. And, which version of Jira are you using: Cloud, Server, or Data Center? Until we know that information... I wonder: does the Create Issue action select the project and…

Smart values are name, spacing, and case-sensitive. I note several in your actions, rule image, and the email that appear not to match. For example: the images show both Sprintchurn and SprintChurn. Those are not the same thing in the rule. Please review all of your variables to confirm they exactly match. Next, please…

My mistake as I repeatedly thought "approvers" and kept typing "watchers"! I updated my earlier posts to correct them. I just tried what I suggested and it worked for me to paste that expression into the Approvers field. Would you please post an image of the audit log details to show what did not work as expected? Is your…

Hi @Rania Haddadin Adding to Trudy's suggestions: The errors you describe indicate your created variables are empty (or incorrectly defined) in the rule. Please also include images of the actions where you define those variables. Kind regards, Bill

Hi @caglad Yes, that is possible. You will want to use the {{triggerIssue}} smart value as a start: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--triggerIssue-- Then you need to identify the correct smart value (or custom field id) for your…

The key here is it is a multiple-select, user field. And so the specifics of how you want to use the information will determine how to proceed: * iterate over the selected values; or * select one specific, selected value, and then parse the name into first and last.

Hi @anne.gerten What have you tried thus far to solve this need? If you have a rule that is not working, please post images of the rule and audit log details, and explain what does not work as expected. If you have not started a rule, I encourage you to try to do so. Successfully using rules requires learning and…

Hi @Marc -Devoteam- I am guessing a bit here as I cannot see your entire rule in one image, and... The problem is likely because you are using two branches in the rule and assuming the first completes before the second one. Branches which could be on more-than-one-thing are run in parallel and asynchronously, and there is…

If you want to assign the new issues to a user after creating them, the rule needs to branch to the issues: * action: create issue * branch: to most recently created issue* action: assign issue * ... Instead I recommend assigning the issues as each one is created by selecting the Assignee field in the Issue Create action.

Before anything else, I recommend pausing to identify the type of field in the global custom field list, and its scope (i.e., JSM, Jira, both). That will clarify how to access its attributes in the rule.

Hi @Eran Roiter 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 @Cedric Ahrend -- Welcome to the Atlassian Community! There appears to be both some leftover JSON, from the field template, and incorrect syntax for label updates. Please look here for the correct syntax to add / remove labels: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Labels…

Hi @Martin Dellagiacoma -- Welcome to the Atlassian Community! With the out-of-the-box JQL features, you may search for the mentions by finding your user account ID value and searching on that. When a user is mentioned with Jira Cloud, that is encoded in the field as: [~accountId:your account ID] To find your account ID,…

Hi @Glenn Ruysschaert For a question like this, please post images of the complete rule (in one image) and the complete audit log details showing the rule execution (in one image). Those will provide context for the observations / symptoms. Thanks! Kind regards, Bill

There is a Log Action which allows writing information to the audit log for debugging / informational purposes: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Log-action If you add that action in your rule, you may paste in the expression, run the rule, and review the audit log details to see…

When a rule edits an issue it uses the current data as the starting point. And so if a rule edits and issue twice in succession, it continues to use the data from the time of rule triggering. Adding a Re-fetch Issue after the first edit reloads the data before proceeding. But your changes have the re-fetch inside the…

If you select Reports, do you see the velocity report?

Hi @Tyler Giles First, and guessing the field type is user select, perhaps try writing this to the audit log to observe what it returns: display name for selection: {{issue.customfield_10173.value.displayName}} first name for selection: {{issue.customfield_10173.value.displayName.split(" ").get(0)}} If that does not help,…