Bill Sheboy Expert

I am glad to learn you got it to work. And it appears when you were using match() that you were missing the grouping in the regular expression: .match(".*(master).*")

Thanks, @Jeffrey Bistrong and I recommend confirming your created variable and branching works as you expect in that other rule... Branches on more than one issue/thing processes separately, and asynchronously, from the rest of the rule. There is no guarantee of when such a branch will complete...up to the last step of the…

Understood, and I still recommend asking the vendor as often marketplace vendors have examples of use cases for products like Jira.

Hi @Jeffrey Bistrong I see a few things in your rules to adjust that might help... First, smart values are name, spacing, and case sensitive, and the one for the trigger issue is: {{triggerIssue}} Next, when you are setting a parent with JSON, that should be only one value, not an array of values. Perhaps try this: {…

Hi @Shashi Matha I recommend reviewing the documentation for the integration tool and contacting that tool's vendor to learn what is possible. From the Jira side, you may be able to preserve some formatting with plain text or HTML, however the markup Jira uses (such as for user mentions) may not will not be compatible.…

Hi @Ali -- Welcome to the Atlassian Community! Adding to Trudy's answer and the JQL you are using... Please consider there can be delays in rule execution due to errors and outages. What would you want your rule to do when more than one day has passed, and so the condition will never be met? Considering how to handle such…

I am glad to learn that helped. Regarding that field, I knew about it from writing JQL over the years. And automation seems to use the same REST API features to access issues...so it made sense it was there. You can identify all the possible smart values available for a rule using the how-to article below. Basically you…

Hi @Mario Amaya (x) -- Welcome to the Atlassian Community! Adding to Mikael's answer... For a question like this, it helps to post images of your complete rule and the audit log details showing the execution. Those provide context to help explain the symptom you are seeing. Thanks! Kind regards, Bill

Hi @Elise In addition to the suggestions others have provided, I have three questions for you: * What problem are you trying to solve by doing this? Knowing this might help others suggest alternative approaches. * What is your Jira type and license level? Specifically, are you using Jira Cloud or Server/Data Center? And if…

Hi @RaphGC -- Welcome to the Atlassian Community! Have you tried using the match() function with a regular expression, and an advanced compare condition? Kind regards, Bill

You can add the Log action to your rule with the smart value, as this can help to provide diagnostic information as a rule proceeds.

Hi @Aiden Swartz -- Welcome to the Atlassian Community! If I understand your question, you want to populate your "End Date" field when an issue completed, and you cannot use Resolved as issues did not set the Resolution until recently. A work-around would be to use the {{issue.statuscategorychangedate}} as a source; this…

Hi @Simone Pellegrini Adding to Trudy's answer... As this rule will have multi-project/global scope, and you appear to be on a Standard license level, you will want the JQL for the trigger to be as specific as possible. Otherwise this will use more of your quota of global rule executions than needed. Kind regards, Bill

If you write the smart value to the audit log, what do you observe: the correct value, an empty value, or something else?

Hi @François Kirié Would you please confirm what you are trying to do? Your description notes removing all of the remaining time, but your smart value references the time just logged. Please check here to confirm your smart…

Would you please post an image of the audit log details, showing the rule execution? And are you certain that the Commitment field type is text?

Hi @Johannes First thing: if you believe you will have more than 100 issues in the release (and so more than 100 in the lookup issues result), this rule may run into processing limits. I recommend doing the math first to determine if this rule is possible. Next...to do what you ask, you cannot use the Linked Issues branch…

Hi! In my experience, sometimes rules get "glitched" by the editor after too many changes...implying there is something that was not cleaned up during a change/save/publish cycle. I have seen this with basic rules and more complicated ones. And so when things just do not make sense why a rule does not work, I try the…

Hi @Parveen Vats I recommend creating a new question, including images of your board column settings and filter. Otherwise only the people following this older thread will see it to offer suggestions. If you feel it would help, you could include a link to this thread in the new question. Kind regards, Bill

Hi @Daniel No, that is not possible with out-of-the-box features of Jira Cloud. If you have the ability to call the Jira REST API from the tool which is performing your "specific tasks", that might be an option. And if you describe the problem you are trying to solve, perhaps the community will be able to suggest other…

Hi @Martin Härri There is nothing built into to do that. How often do you need to perform this check? If it is infrequently, please try a JQL search ordered by the labels to find the duplicates. If you need this more often, consider checking if you have addons to enhance the features of JQL, or make a dashboard showing…

Hi @mo -- Welcome to the Atlassian Community! Are you using a Company-managed project (CMP) or a Team-managed project (TMP)? CMP use the "Story points" field (and smart value) and TMP use the "Story point estimate"...even though they have the same name in the UI. Your rule appears to be referencing both, although only one…

You describe using issue links to connect these "release" issues to stories. And so if you can write JQL to identify the issues, you can use that JQL with a JQL branch or with the Lookup Issues action with an advanced branch.

Just to be clear, I am unfamiliar with the Jira Core Server automation... Is there an audit log for this rule which would show why the rule is not sending the email? For example, perhaps there are no matching issues.

Hi @ADEEL AHMED In my experience, the needs for a specific "scrum master" role depend upon the team's needs, the organization's needs, and how the job is defined. I recommend reviewing any postings and asking questions to understand what is required versus desired, and ask to observe the team in action before committing to…

Hi @Len Bergman Short answer: you have left the Jira Product Discovery (JPD) project views and are viewing the JPD project's ideas from the new Issues search view of another project. I was able to replicate what you see for the list, but not the blank left-navigation...and I am unclear how you got there from JPD except by…

Hi @Terry Booth Would you please show the details section of your rule, showing the rule actor? You noted that you were the rule actor, and to clarify do you mean: the rule is set to your user id for the actor, or that you triggered the rule and the actor is the default Jira Automation one? To Trudy's earlier suggestion,…

Hi @V N Raju Raju What you are asking is very specific for your needs and the part about story links as hyperlinks in some single issue field is unlikely to be supported with built-in Jira features. Rolling up the individual versions may be possible... Are you using Jira Cloud or Server/Data Center? I will assume Jira…

Hi @Phil Bustin You noted this: I also thought there might be more than one way to reference the name itself as a smart value, and I guess there is--either the name itself or preceded by "issue." Context within a rule is important when referencing smart values, and so sometimes omitting the issue prefix can cause an…

Let's stick to this thread as that is where the rule image is posted. After the change to remove the extra bracket please post new images of your rule and the audit log details showing the rule execution. Thanks!