Bill Sheboy Expert

Hi @Sina Mathieu Yes, that is possible with an automation rule. What have you tried thus far to solve this? If you have a rule that is not working as expected, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of…

Hi @Mikołaj -- Welcome to the Atlassian Community! First, to identify the smart value (or custom field ID) for your field, please use this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ Next, to use a smart value expression in actions like Manage Watchers, it is not…

Hi @Andrew Zabrzeski Smart values are name, spacing, and case-sensitive, and often do not exactly match the field display names on the pages. And for some fields in rules, the custom field ID is required rather than the smart value by name. Unfortunately, even that is not consistent: sometimes the name is required for…

Hi @Prabhashankar Rai If there are no conditions (e.g., one select = one sub-task), please try using an Advanced Branch over the selections. When there are conditions, you could use if / else condition blocks, or try to consolidate those using Lookup Tables to map the values to the needed sub-tasks. Certainly the…

Hi @Tanu Bhasin -- Welcome to the Atlassian Community! There was an automation outage / slow down yesterday, so perhaps that is still impacting capacity: https://jira-software.status.atlassian.com/incidents/xwthpprq7mhr As the rule execution backlog gets caught perhaps your rule will return to normal operations. If you do…

Thanks for that information, and... I recommend writing the JQL you are trying (with the smart value in place) to the audit log, running the rule, and the checking the log to confirm the JQL contains what you expect.

Hi @Zach Handzlik The Issue Created trigger has a known racetrack / timing problem where the rule can start before all of the data is available to it. As a result, your condition and lookup issues JQL could be missing data when the rule runs. The mitigation for this is to always add the Re-fetch Issue action immediately…

Hi @Judy Edmonds I do not believe there is a public REST API for Jira Product Discovery (JPD), and thus it is not possible to automate creating a view within JPD. Even if that was possible, how many reporters do you have? Would you really want to create a view with JPD for each one? If your reporters are all Jira users,…

Thank you for those images. I see two problems with the rule you show: First, within an issue the sprint field is a list of values. And the condition inside of the branch is checking {{issue.sprint.state}} That could produce a list of values, such as: closed, closed or closed, closed, active Perhaps try testing this way…

Hi @Bob Dalm Here are some suggestions to improve the Smart Button feature, which you may watch / vote-for to see progress: * https://jira.atlassian.com/browse/CONFCLOUD-79704 * https://jira.atlassian.com/browse/CONFCLOUD-80888 Kind regards, Bill

I expect this is related to newlines and other characters in the text...which cause challenges for the regular expression handling of the match() function. Let's make it super easy for match() to figure things out: {{issue.description.replace("\n", " ").split(" ").match(varRegEx).size}} That replaces the newline character…

An example would be as I described earlier: * action: Set entity property* Entity type: User * Select a user: Work Item Assignee * Property key: myUserPropertyKey * Property value: {{issue.assignee.accountId}} For your case, "Property key" would likely be: in progress assignee That must exactly match the field setup name…

Hi @Romy Vermeeren -- Welcome to the Atlassian Community! Short answer: I recommend working with your Jira Site Admin to submit a ticket to Atlassian Support to review this symptom: https://support.atlassian.com/contact/#/ The documentation for JQL with the worklogDate field, and other dates, show them in quotation marks.…

Hi @joscha.reinhard For field sync / sum scenarios there are often many cases involved. Deciding the accuracy and frequency will determine how many rules are needed and their respective logic. Here are some of the cases to consider: * Story is created with an Epic assigned --> update the Epic * Story's field is changed…

Hi @Amulya Sankara When did you first notice this symptom of the rule not running? There is an Atlassian production incident today where rules are delayed / not running when expected. Please look here to follow progress on it: https://jira-software.status.atlassian.com/ Kind regards, Bill

Hi @Saira As described in the documentation, while a Smart Button may be added to a page template, it cannot be configured to use a rule until the actual page is created: https://support.atlassian.com/cloud-automation/docs/smart-buttons-for-automation-in-confluence/#Using-smart-buttons-in-page-templates Here is a…

Hi @Ano Niempje -- Welcome to the Atlassian Community! I recommend first storing that page's body value in a create variable and adding the JSON encoding function to the end to help create the message. Then use the variable in the Send Web Request action for the body. Here are the documentation pages for those features: *…

Hi @[deleted] -- Welcome to the Atlassian Community! As the original scope of your question (based on the summary) is about automation rules, I will confine my suggestions to that scope...as the rest of what you state seems unrelated to that. When an automation rule is created and published, it has a specific scope in the…

Hi @Liron Bdolach Is that gadget a built-in one or from a marketplace vendor? If from a vendor, I recommend checking their documentation and support information from the marketplace pages: https://marketplace.atlassian.com/ Kind regards, Bill

Hi @Doğancan Uğurlu -- Welcome to the Atlassian Community! Jira Query Language (JQL) is not a SQL, and thus does not have features as you describe. It is a purpose-built language to search for issues within the confines of Jira features. The workarounds for such features depend upon how frequently you need it and…

Hi @Philip Ng Your rule is trying the user input field in the match() function but it is not in the correct format for the function's use of regular expressions. To solve this, first create a variable which wraps the input in parentheses and then uses that variable in the function. * trigger: manual input, with the user…

Hi @William van Dalen How often do you expect the "---" text in your Description, in what format / length, etc.? You could try first replacing multiple occurrences of hyphens with a single newline using the replaceAll() function and a regular expression. For example: {{issue.description.replaceAll("(\-{3,})",…

Is the the field a number type? One last thing to try: change the JSON to use customfield_10225 rather than the field name. Rules can get confused by duplicated field names / smart values when they are in different scopes: e.g., global versus team-managed (TMP) versus multiple TMP projects.

Hi @Ryan_Milway -- Welcome to the Atlassian Community! Custom formulas do not support conditional logic yet. As a workaround, you could use an automation rule to set the field. Please look here to learn more: https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/ Kind regards, Bill

No, it is not. When on the project settings > work types > Task page, you should see something like this in the browser URL: yourJiraURL/jira/software/projects/yourProjectKey/settings/issuetypes/10029 The 10029 is the identifier for that type.

The likely cause is the JSON syntax is incorrect, even though the error message does not state that specifically. If that field is a number type, here is the correct syntax for the JSON: { "fields": { "Weeks in status": 0 } }

Please provide the images I noted above as something is incorrect in the implementation of your rule and seeing the images will provide context: * an image of your current, complete rule * images of each trigger, action, branch, and condition in your rule * an image of the audit log details showing the rule execution, with…

I just tried this for that field type with the Set Entity Property action and it works. Let's confirm some things for your scenario: * For the "Property key", the rule sets it to a custom field value, but that must be static as it was defined when you created the field. Please enter the correct value. * For the "Property…

No, I do not know. I just tried that with a OneDrive link and although the link saved and took me to the document from the page, there was no way to embed the content as described in workaround. Apparently that no longer works that way; sorry for the out-of-date suggestion.

To do that, I believe you will need to use an iterator to build the JSON expression yourself, iterating over the field value's objects. However if that value is text representing the object, you could instead: * use a match() or substringBetween() function to strip off the outer information * split() the result on the…