Bill Sheboy Expert

Hi, Brandon -- Welcome to the Atlassian Community! There are two batch handling options for Jira Server automations rules: bulk issue handling with branches / scheduled triggers, or using the Send Web Request action to call the REST API issue search with JQL. Which one to use depends on what you want to do with the…

Hi @Greg Mihailides First, you describe wanting to create the new issue in a different project, but the rule action shows creating in the same project. Is that an error? If you did want to create the issue in a different project...What is the scope of your rule: project, global, or multiple-project? All three scopes can…

Hi @Salli El Ramadi -- 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 @Nicola Adding to the other answers...Here is a how-to article for calling a REST API function with the Send Web Request action in a rule: https://community.atlassian.com/t5/Jira-Software-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828 Kind regards, Bill

Hi @Николай The images you provided are not features of Jira Cloud. Perhaps they are from another tool or from a marketplace app / addon. Please contact the vendor of those tools for support. Thanks! Kind regards, Bill

Hi @Antony Smith For a question like this, please post an image of your complete automation rules, 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 @Pierre Arizolli Just to confirm... As written the rule should work for the hierarchy by enabling "Allow Rule Trigger", looping to trigger itself...with no need for an additional rule. Is that what you ended up doing? If so, please note if there are many levels in the hierarchy, a single rule approach could fail due to…

Thanks, Chris!

Hi @Phil Bustin I have only seen that when the rule is not valid, based on the last attempted publish. Please open your rule in the editor, try publishing again, and observe what errors are shown. If that does not help, please post images of your complete rule, the error icon indicator, and the audit log summary showing…

Thanks for clarifying...putting together what Mikael and I suggested, these changes could help: * trigger: manual * condition: label contains Feature * action: edit the Description field, entering this in the field {{issue.description}} {{issue.parent.description.substringAfter("HAPPY").substringBeforeLast("HAPPY")}} This…

Hi @Rodolfo So This is a very old question / thread. I recommend creating a new question and linking back to older threads for context. That will ensure more members of the community see the question to offer help. Until you post your new question... The capabilities of rules have changed quite a bit since November 2021...…

Please consider...I recommend listing out your test cases (i.e., before / after values, expected results, etc.) Once you have these, then create a rule in a test project and exercise all of the cases. This will reduce the churn on your "production" project for the team. When the rule is finished, it can be copied over to…

I do see a value in projectTypeKey for the JPD projects when I search for all of them: "projectTypeKey": "product_discovery" And, because JPD is relatively new, that may be why this type is not yet shown (or accepted) as a parameter value for that order-results expression.

Thanks for confirming the fields. As I and other posters are successful with this type of rule, without changing the rule actor, I suspect there is a permissions issue or something amiss with your JPD project or the user configurations. At this point I recommend working with your Jira Site Admin to submit a ticket to…

Hi @Andrew Have you tried a test rule, hard-coding a Slack ID value such as your own, to confirm the connection is working as expected? Kind regards, Bill

Awesome; I am glad to learn that helped!

Hi @Jason Francia -- Welcome to the Atlassian Community! To clarify a bit... Are you using a marketplace addon app for checklists? * If so, which one? * If not, what do you mean by "checklist"? Please post an image showing an example of what you are calling a "checklist". If you are using a marketplace app for checklists,…

Hi @Pavol Sočuvka Perhaps...it is the same concept, except using the "value.emailAddress" attribute rather than "value" as shown above. The reason is the user picker fields returns user objects, and that will include all the needed attributes. To confirm this the community would need to see your rule and know your project…

The description field is not a list: it is a text field, and so that is the incorrect syntax for the JSON. Regardless, that JSON is not needed as the text and smart values can be entered directly when editing the description field. You originally noted copying information from the trigger issue's parent: an epic. Your rule…

If you are trying to set that to a specific key in a rule, I believe you will need to first save the key in a Created Variable, and then reference that. For example: * trigger: issue created * action: re-fetch issue (This is always good to add after the issue created trigger to prevent timing / racetrack problems.) *…

Thanks, Josh. What is the scope of this rule: one single project, multiple-project, or global? I suspect it is single project, and even though your sprint board apparently spans multiple projects, the rule cannot "see" the other issues. If you look at the audit log for the rule I expect it is not triggered for issue…

Hi @Brandon Are these company-managed or team-managed projects? I am guessing they are team-managed, as you have the same field with two different custom field ids. Out-of-the-box JQL cannot compare two different fields in this way. (It is not a SQL...) Instead you would need to test for the specific value (not the ids of…

Hi @Josh Goedert 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 @Antony Smith The features of automation rules are different for the different Jira versions (Cloud, Server, Data / Center), and for the version of automation installed when using Jira Server. Additionally the fields and smart values available differ by Jira version and the Atlassian products installed. Please look here…

Hi @Tamara MacPherson Yes, and...to Mikael's answer: Context is important for automation rules, and all of the parent epic's fields are not directly accessible to their child issues. Instead they may be found with branching, the lookup issue action, etc. Please post an image of your complete rule and the audit log details.…

Hi @Rowan B -- Welcome to the Atlassian Community! What happens when you try to retrieve them with the REST API function? When I tried it just now the JPD projects were returned. Kind regards, Bill

Hi @Kawtar Amajoud -- Welcome to the Atlassian Community! What problem are you trying to solve by merging the results of the two REST API calls? Knowing that may help the community to offer better suggestions. Until we know that... Created variables are text, and when the web response is stored it loses all name attributes…

Hi @van den Bergh, Marius, Vodacom (External) There are field change, smart values for the additions and removals: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--fieldChange-- Please try this, based on the trigger you show in the rule: {{deletedFieldChange.values}} Kind regards, Bill

Hi @Trudy P Claspill I added a comment about email usage to the suggestion for improving features for automation usage management: https://jira.atlassian.com/browse/AUTO-922 Kind regards, Bill

Hi @Phil Bustin I numbered my questions to try to help... (1) What is the purpose of the first Re-fetch Issue action in your rule? Is that needed due to some workflow transition stuff happening (outside the scope of the rule)? (2) What type of project is this: company-managed or team-managed? The create issue action you…