Bill Sheboy Expert

I am glad you got that to work. You may want to let the support team know as that appears to be a defect in the regular expression implementation for Server/Data Center rules.

First thing, which I should have noted earlier: I am using Jira Cloud, and not Server/Data Center. And we know the automation features are different for those products. So please experiment/validate what I describe to confirm it works for you. Thanks! Okay, I just tried this version and it worked exactly how I wanted to…

Okay, the next thing to check: are those the correct smart values for the fields? Smart values are name, spacing, and case-sensitive. And, just because something has a field that does not mean it is supported by automation rules (e.g., vendor addon, calculated fields). To check your smart values, please use the how-to…

Hi @Jeff Gordon How about this: replace the newlines first to simplify the matches? {{issue.description.replaceAll("(\n)"," ").match(".*Strengths/Weaknesses:(.*)Preferred Location.*")}} This would remove the line formatting, although you can work-around that by replacing with a character/string as a token (e.g., NEWLINE)…

Hi @Valerie Blondel Looking at the image you posted of the Create Variable action, it appears there are some typos in your mathematical expression. Some of the smart values start with {{issue.fieldname.value}} while others start with an extra character before "issue" {{Iissue.fieldname.value}} Please try removing those…

Hi @Michael Da Costa Without seeing your entire rule, I suspect this is caused by your branches. Please consider posting an image of your entire rule and the audit log details, as that will help confirm that. Thanks! Until then...some information to help: Stuff that happens in a branch, stays in the branch. More…

I was suggesting that rather than use the branch, use Lookup Issues to find the UAT Task with your JQL to get the key; the key would be {{lookupIssues.first.key}} Then you can use another lookup issues action to find the other Bugs for the UAT Task in the same way, but inverting the link direction: issue IN…

Tina, would you please post what you have tried thus far for that case? I believe this is possible with conditional smart values...the trick may be getting the correct conditions so the item before has a trailing comma.

Hi @Tina Leszkiewicz That article you linked to is for Jira Server/Data Center, and you appear to be using Jira Cloud. Is that correct? If so...you can still use the advanced edit with JSON described in the article. Here is another article specifically for Jira Cloud on using JSON for edits. To do that... * in your Edit…

deleting duplicate post

Hi @Elizabeth_Johnson Yes, and...to the answer from @Stefan Salzl If your description of the scenario is accurate you may not be able to do this in one rule, and depending upon your Jira license level may not want this to be a global rule. First thing: rules can have up to 65 components (i.e., trigger, actions,…

Well done on your explanation! Just to confirm: do the Bug issues have labels for Agency, CO, or DX, or are those values in the summary? If they are in the labels, you can find the "sibling" Bugs sharing the label and which block the same UAT Task with JQL. And then use that JQL with the Lookup Issues action (rather than a…

Here is the documentation on adding labels with JSON, and here is an example of how to do this with created variables... Let's say you want to set the hard-coded value in a variable and then add the label with JSON. * action: create variable with* variable name: varAddLabels * smart value: { "add": "myNewLabel01" } *…

Hi @Kathryn Swearingen For an apparently complicated scenario like this, please consider diagraming this out (before and after), and post those images. That may help the community to suggest how to create the rules you are asking about. Thanks! Kind regards, Bill

Hi @Marc van Niekerk Since I originally responded to this question, I learned more about this use case and the parallel processing of branches on more-than-one-thing (i.e., issue, value, etc.) Because of this one issue edit could "walk over" prior results. Although there could be another cause for your rule. Without seeing…

Created variables are text, and so there are no other attributes, such as url. I can think of two ways to do what you ask with a link to the issues... a) Add links for each issue in the lookup after the number, with {{#lookupIssues}}{{url}}{{^last}} ; {{/}}{{/}} b) Use HTML formatting and encoding in your Slack message,…

That defect I referenced was when the Story Points field had the problem and that does not appear to be the case for this one. As it could be another field, you may need to wait to hear back from Alex contacting the Atlassian team.

No problem, and I will try to help with explaining the steps. To learn if this symptom is caused by that defect, please try this: * Look for the gear icon at the top-right of your page for "Settings" * Select that, and under "Jira Settings", select "Issues" * Then on the left page, under "Fields", select "Custom Fields" *…

Thanks, and I found another which is the symptom you described, so please take a look at the work-around in that one: https://jira.atlassian.com/browse/JSWCLOUD-23326

Hi @Andre Fortier Looking at the public backlog for this symptom, this could occur when... * trying to map a custom field in a team-managed project to the import * trying to import a field value which does not exist, such as a Status value not setup for the project * trying to import issue types which do not exist * trying…

Hi @Yakov Babich Adding to Fabio's ideas... If you added quick filters to the board, you would have the same problem: once you add many quick filters, those then appear in a drop-down list and there is no keyboard shortcut to "navigate to next filter". I did a quick check of the public backlog and did not find a suggestion…

Thanks for that information. When posting an image of long rules, I recommend using a browser extension (or app) which can capture a complete, scrolling browser tab view. Back to the error you observed, the cause is because the rule is referencing an issue's fields in the condition test on Issue Type. That condition is not…

Hi @Shashwini Nair -- Welcome to the Atlassian Community! Adding to John's answer... Smart values for fields are name, spacing, and case-sensitive, and they may not match the names shown on the screen. When in doubt of a field's smart value, please try using the information in the how-to article linked below. Essentially…

Hi @Craig Wells I just tried your rule scenario, in a company-managed project, and it worked for me. I included a Re-fetch action after the trigger to confirm the data re-loaded prior to the condition and edit action. I recommend re-creating the rule from scratch to see if that helps, as rules sometimes get "glitched" and…

Hi @Vincent Mutambuki { Mumo Systems } When recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Community online guidelines for Marketplace and Solution Partners…

Hi @Brent Jenkins Would you please post images of your complete rule and the audit log details showing the rule execution? Those may provide context for what you are observing. Thanks! Until those images are posted...here are some other thoughts: I do not believe the old Code Barrel backlog is available/accessible any…

Hi @Hadar Dinte I do not understand your question. Would you please explain the problem you are trying to solve? That may provide some context for the community to offer suggestions. For example, if you are are trying to link to a web site in an email why not just put in the exact URL, as many email formats would…

Until you post the image of your entire rule, I don't know how to answer the questions you are asking about the errors.

There is a rule action named Log which allows writing text or smart values to the audit log. Please add that action to your rule after the lookup issues action, including this: Here are the expected assignees: {{#lookupIssues.assignee.emailAddress.distinct}}{{.}};{{/}}

First things first: would you please post images of your current rule and the audit log details showing the execution? That will provide context for what you are trying to accomplish, and then we can suggest ideas to help. Next, once we have that info, it should be clearer which issue you are trying to edit: the trigger…