Bill Sheboy Expert

Hi @Christos Markoulatos -Relational- The Advanced Branch is not supported for Jira Server or Data Center automation, and thus this approach will not work. Here is the suggestion to add the feature: https://jira.atlassian.com/browse/JIRAAUTOSERVER-749 Kind regards, Bill

Hi @Amy Tebbe JQL is a query language to find work items meeting some criteria. It cannot find the opposite: the absence of information. If there is a REST API endpoint to get all possible vulnerabilities, you could iterate them to find any without associated work items. And, if such an endpoint exists, there may be a…

Hi @Elizabeth_Lee -- Welcome to the Atlassian Community! First thing: deleting work items can be problematic as there is no built-in undo feature. It may be better to move an Epic (and its child work items) to "Done" and set the Resolution to a state such as "Abandoned". This prevents accidents and enables recovery of the…

Hi @Michael Garrett Have you started the rule yet? If so, context is important for automation rule questions. Please post the following: * what version of Jira are you using: Cloud, Server, or Data Center * for Cloud, what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete…

Hi @charu Your rule image is a bit low-resolution, and it looks like you are using conditions, one after another. In that case, when the first condition fails the rule will stop processing. There are several ways to solve your scenario, including at least these: * Use an IF / ELSE block with the conditions for each case,…

Hi @tiago_santos For a question like this, I recommend posting images of your complete rule and the audit log details showing the rule execution. Those will provide context for the community to offer better suggestions. Until we see those... Short answer: With a Live Doc in Confluence, there appear to be timing consistency…

Hi @vincenzo.spatafora Just to confirm...did that solve this question for you? 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. Thanks!

Awesome; thanks for confirming that helped!

Hi @Farisa Ahmed You are correct the create page action does not support a dynamic value for the parent...or even allow a relative selection within the rule (e.g., add a child under the "current page"). A workaround for this is to create the child page and then update the parentId using the REST API and the Send Web…

Hi @Dushyant Sharma The smart value parsing for the new Send Customized Email action's content does not correctly parse smart value defaults using the pipe | syntax. Instead, the values collapse to null, which can break some features such as the table macro...and lead to rule errors in the audit log. Please see this…

Hi @Agnes Bodor Short answer: You have found a defect with this new rule action / smart value parsing. I checked the JAC backlog and do not see this defect / symptom. If you are on a paid Jira license level, please work with your Jira Product Admin to submit a defect to Atlassian Support…

Thanks for that information, @vincenzo.spatafora What do you want to do with that mean (i.e. arithmetic average) value? Let's assume you only want to calculate it, such as for sending in a message. That is quite simple: * trigger: scheduled, with JQL and using the bulk-handling option * action: send email, with the average…

Well done making progress solving this one! When updating the work item, I recommend first performing the label deletions, re-fetching, and then adding the correct ones. This prevents racetrack timing problems / collisions in the updates. For example: * action: edit work item, to remove any matching / old labels * action:…

Hi @Michael Catmur The syntax you are using for the conditional expressions is incorrect; I recommend reviewing the documentation for the different possible syntaxes. #1) The syntax which includes an else block looks like this, and does not support all possible inline functions. Instead, use experimentation to confirm what…

Hi @Slobodan Mamula Adding to the information from @Florian Bonniec -- Here is the backlog suggestion to add other endpoints to modify Confluence databases. You may watch or vote for it to see progress. https://jira.atlassian.com/browse/CONFCLOUD-77328 Kind regards, Bill

Hi @Agnes Bodor Context is important for automation rule questions. Would you please post the following to help the community offer better suggestions? Thank you! * What is the type of your custom field? * An image of your complete rule in a single, continuous image for context * An image of the rule action where you are…

@IT Brute -- What version of Jira are you using: Cloud, Server, or Data Center? Jira Cloud uses accountId value for mentions, while Server and Data Center use the user displayName. In the comment it appears as the name, even though it is the accountId. Or, do you mean when there are multiple mentions on a line of comment…

Thanks for those additional details, @Daniel Lee -- Please note I was listing those other cases to help you consider what / how to handle them...and not as a roadmap to provide you a bunch of rules. I would actually need to implement each one to determine the exact steps, and then post those details. Short answer: my…

Hi @vincenzo.spatafora First regarding the limited fields in Lookup Issues in Jira Server or Data Center automation, there are two possible workarounds...depending upon needs / context: * When you only need to read the data and your rule is not yet using branching, try the bulk-handling option and the plural {{issues}}…

Hi @vincenzo.spatafora I did not find any suggestions in the JAC backlog to add the Lookup Table action to Data Center. Given the upcoming sunset, perhaps that will not ever be implemented. And, I will post in your other thread for the question to offer suggestions. Kind regards, Bill

@Mikki Bisschoff if you run into problems with the rule, please post images of the complete rule and audit log details, and explain what is not working as expected. Those will provide context for the community to offer better suggestions. Thanks!

Hi @Jagoda Zawadzka First, I recommend continuing to use {{issue.created}} in your expressions: that will be when Jira created the work item as opposed to {{now}} which is when the rule eventually runs. During Atlassian outages and problems with rule slow downs, the values will definitely be different: now will be after…

Hi @Daniel Lee When do you want the labels synched? You show a couple of example rules, where one uses a Scheduled trigger and the the other uses Field Value Changed for the labels. Next, you note examples of adding / removing labels and of just keeping them aligned. Have you tried rules where they just copy the labels…

Hi @liamhale -- Welcome to the Atlassian Community! As others have described, those features do no exist yet. Here are some open suggestions you may watch / vote for to see any progress. These cover rule components and the endpoints needed to support them. * https://jira.atlassian.com/browse/CONFCLOUD-77328 *…

Hi @Scott Derderian Just following up to check if this 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!

Hi @Felipe Justino When updating a multiple-selection option field (rather than setting it), please use the "update" attribute with the "add" or "remove" operations rather than the "fields" attribute. Please look here to see examples:…

Hi @Dheeraj Kumar C -- Welcome to the Atlassian Community! As a variation of the suggestion from @arielei please consider checking the maximum date rather than the last sprint added to an issue. This will prevent problems with re-ordering of sprints in the backlog causing mismatches. And, the bulk-handling feature must be…

Hi @IT Brute Let's change your smart values and regular expression to parse only the distinct accountId values: {{issue.comment.last.body.replace("\n", " ").split(" ").match("^\[~accountid:(.*)\].*").distinct.join(",")}} With that, we can eliminate the branching as that can cause update problems (due to racetrack errors…

Hi @[deleted] When iterating a smart value list with unnamed attributes, the current item may be referred to directly as {{.}} or used as an implied value in some functions. For example: * action: create variable* variable name: varMyList * smart value: potatoes<p>carrots<p>Onions * action: log (for the expression you show…

First thing: if you are having difficulty following that explanation, please pause to review these documentation pages before proceeding. They will help you understand how rules, smart value lists, and the match() function will interact: *…