Bill Sheboy Expert

Hi @Michele Liberman Just following up to check if the suggestion from @Hardik Babbar answered your question. If so, please consider marking this one as "answered". That will help others with a similar need find solutions faster. If not, please let the community know what help you need with the rule changes. Thanks, and…

I do not believe there is a "default script" to do what you describe. Please show a screen image capture of where you see this feature. That will help the community better understand what you are describing. Thanks!

Hi @Greg Unfortunately, that is not currently possible. Even when all such features are disabled, the marketing prompts to add them and their buttons are still present. Here are a couple of related suggestions to remove those when they are disabled. You may watch / vote for them to see any progress. *…

Hi @Alexandre Daher -- Welcome to the Atlassian Community! Where and how are you summing the values? For example, with an automation rule to a custom field, with a marketplace app and scripted field, etc. Knowing how you are doing this sum will help the community offer better suggestions. Kind regards, Bill

I recommend using one approach and trying to understand why it does not work, checking the audit log for problems. Focusing on the first Edit Work Item action you show, you may select Request Participants from the dropdown list or use JSON to update it, but not both at the same time. When you try to set just one…

Hi @Jader Peixoto Volkmer For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit log details showing the rule execution…

Hi @MGulick_chatsworth_com You are using the deprecated endpoint. Please review the documentation for the new endpoint, and when you request any fields other than the id, the maximum results are limited to 100 work items:…

Hi @MidnightExe This would be easy if Jira Data Center's automation had advanced branching over smart values, which it does not yet: https://jira.atlassian.com/browse/JIRAAUTOSERVER-749 Possible workarounds depend upon your assumptions and the effort to solve this: * When this need is infrequent, use a CSV import to create…

Hi @Jayesh Raghuvanshi The original poster asked about Jira Data Center, which does not have advanced branching for automation rules, and thus your suggestion cannot work. To learn more, please see the supported branch types for Jira Data Center and the suggestion to add the feature: *…

Thanks for the additional information, @Thomas Brennan First, your rule appears to access work items in multiple projects. Thus, the rule scope must be global or multiple-project to access those. This can be done by a Product Admin in the global automation area. Next, for the rule you show there are a few things to…

Hi @Natalia Peleshok -- Welcome to the Atlassian Community! While you could submit that suggestion inside of Jira (select ? and then "Give feedback about Jira"), you could also implement it immediately using an automation rule, choosing your project scope to limit usage. There have been several community questions to…

Hi @ckopanon This might be possible, given some assumptions: * there are fewer than 100 work items in the "Prioritization" status * there are well-defined criteria of the "Priority" transition values * there are no dependencies for the value of "Priority" between different work items * you do not care if this gets broken /…

To learn more about using created variables as numbers in different contexts, please see this article I wrote on the topic: https://community.atlassian.com/forums/Automation-articles/Automation-concepts-Using-Created-Variables-as-Numbers/ba-p/2953116

Hi @Liz Borrelli -- Welcome to the Atlassian Community! The conditions shown when adding to the trigger are for the product where the rule is defined, not the trigger. You are trying to create the rule in Confluence and so Confluence conditions are shown. Your options are: * Do not add conditions to the trigger, and…

If it is not a valid email address, I do not know how you could proceed adding it as either a customer or user. As you appear to be on a paid license, you may want to work with your Site / Product Admin to contact Atlassian Support and ask for their input. Your admin can submit a ticket at the link below. When you hear…

Oops; thanks for the reminder this was for Confluence rules, @Koloman Pfeffer ! There are many related, open defects for timing-related symptoms, and here is the most recent one I found: https://jira.atlassian.com/browse/AUTO-2061 And, here is the post from an Atlassian team member regarding the in-progress architectural…

Hi @Thomas Brennan -- Welcome to the Atlassian Community! Adding to the suggestions from @Marc -Devoteam- ... Without seeing the exact scenario you are trying to solve and your current rule, it may be difficult to make suggestions on how to proceed. Specifically, what problem are you trying to solve with this type of…

Hi @Gustavo Moraes For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit log details showing the rule execution *…

Hi @Koloman Pfeffer Short answer: I recommend removing the condition from the trigger and adding a separate condition after it, setting the actor back to Automation for Jira, and then monitoring your rule. Rule triggers can have racetrack timing problems, where all of the data may not be present at the time the event…

Hi @Zeroocool Using an alphanumeric expression as a "number" could lead to unpredictable results. I recommend parsing it to validate the data and to remove any non-numeric characters. And...many of the inline date / time functions only take an integer as a parameter, and so using a number in a variable converted with…

You are making the distinction between a JSM user and a Customer. Have you added the customer for the person reporting the issue / submitting the request? To learn more, please review the different roles for JSM:…

Hi @Jeff Davis -- Welcome to the Atlassian Community! Well done solving your own question! Yes, and...you could post an answer describing how you solved it and then "accept" that as the answer. That will help others with a similar need in the future find solutions faster. Thanks! Kind regards, Bill

Hi @Sara Nicholson Short answer: please try the match() function with your regex and experiment to perform that test rather than using the contains condition. There is nothing in the automation documentation about what is (or is not) actually supported for regular expressions. Instead, it states this, with emphasis added…

For automation rules, the "initiator" is who did the action to trigger the rule. That cannot be changed. I asked if you instead want to set the Reporter: the person who is reporting a particular issue. Please review the linked information I provided to learn how to set the Reporter using the Edit Work Item action by…

I did see your updated rule, and that is why I noted to please see the earlier suggestions as I believe they have what you need: * When you want to use the if / else block, that cannot be inside of a branch * Instead, use the Lookup before the if / else block, and then branch inside (if necessary)

Hi @Fco_ Javier Blanco González You are correct that the rule needs a Work Item Transitioned trigger, and it must have multiple-project or global scope to access both projects. To change the scope, your Jira Site / Product will need to help change that in the global automation area. Kind regards, Bill

Hi @Hergenhan, Maria Do you want to set the Reporter field for the work item / issue? If so, when the work item is created, an automation rule could use text functions to extract the email address from the Description field, and then set the Reporter using that email address. The key to making this work is knowing the…

@Manav Shah -- Does the updated rule work as you expected? If not, the latest rule image you show still uses a branch, and so the if / else block cannot be used inside of that.

Thanks for that additional information, @Anna Mjau When creating a version, you need to know the project. And if you have the project, the REST API endpoints may be used to identify the versions. With Jira Data Center, that endpoint is:…

Thanks for that additional information, @Manav Shah You do not show your entire rule, and from what you describe, I wonder if you could use the Scheduled Trigger with JQL to find the "recent issues" rather than a lookup. Then the trigger would handle the iteration rather than branching. For example: * trigger: scheduled,…