Bill Sheboy Expert

As an alternative, you could try the generic Issue Updated trigger and add an Advanced Compare Condition to check the Change Log for the team value change. __Bill

Hi @Andrew Vaughan I am unclear about some of the extra characters in what you posted, and... * If you have a custom field named Employee Full Name which is available within an issue's scope... * Usually one of these will work:* {{issue.Employee Full Name}} * {{issue."Employee Full Name"}} Smart values are case-sensitive,…

Hmmm...I have one more thing to suggest to rule out a problem with the condition type: * In your compare replace the created value with the source value: {{lookupIssues.size|0}} and re-test * And then, rather than using the if/else condition, substitute an Advanced Compare Condition and test again using the created…

Hi @Kris G _Alacriz_ Would you please point out where in that article it describes what you noted? What I found was: How does automatic clearing work alongside manual clearing? The 14-day automatic clearing rule is based on when you resolve an issue, which is currently tied to the DONE column. Manual clearing allows you to…

Hi @Paul Stasiak -- Welcome to the Atlassian Community! I saw several open suggestions to improve WIP counts for boards. You may watch/vote for any of these, or write your own idea. * https://jira.atlassian.com/browse/JSWCLOUD-20568 * https://jira.atlassian.com/browse/JSWCLOUD-21511 *…

Hi @Phyllis Zhu What type of project is this rule for: company-managed or team-managed? I'm wondering if Epic Name is the problem for mismatches in conditions. And, if you use log statements to write the issue fields used in the conditions to the audit log, do you see the values you expect for the conditions to pass/fail?…

Hi @Северин Вервальд -- Welcome to the Atlassian Community! You appear to be using a team-managed project (formerly called next-gen), and that is not yet possible for those projects. Here is the suggestion to make that configurable: https://jira.atlassian.com/browse/JSWCLOUD-21257 Best regards, Bill

Hi @Adi Halfon -- Welcome to the Atlassian Community! I know of no such capability built into Jira Cloud to do that. You may want to investigate cloud backup processes or marketplace addons with your site admin. Before you do those things, I suggest describing what problem you are trying to solve with that level of…

Hi @Javanshir Mustafayev _ HIT If you were to run that JQL stand-alone in advanced issue search, it would resolve to: project=HR and issuetype='employee' and 'Yes'='Yes' What you probably want in your rule is: project=HR and issuetype='employee' and MyCustomFieldName = 'Yes' Not the value from the field... If I am missing…

It appears you and the team have enough info to sit down with your product owner to discuss the problem and any experiment... * what is the problem we are trying to solve * what would better look like * how will we know it is getting better * how would we measure that * what are some planned steps toward better * take the…

Hi @Agile Curve -- Welcome to the Atlassian Community! How about "take it to the team", and sit down with the product owner (PO) together to understand what you observe, why you hypothesize that is happening, and deciding how to experiment to improve the situation? There could be lots of reasons for this symptom, and…

Hi @Lydia Hawkridge You could do this with custom fields, as you suggest, and then use an automation rule to calculate the product. As there are 31 possible results (null, and 1-30) you may not want a select field for the result; just a text or numeric field. Perhaps also consider then selecting a range of values to adjust…

Not really, as each case is often different. Let's assume you uniquely identify your newly created stories (based upon the epic labels) with a value in their own labels, such as "Needs_Subtasks". Your next piece of the rule would be: * branch: on JQL of project=myProject AND labels = Needs_Subtasks AND... any other…

Please see the example from @Deepanshu Natani as that is much simpler than trying this with the JSON edits. Thanks!

Hi @Blen Assefa -- Welcome to the Atlassian Community! I do not know of any built-in JSON array merging for automation, but I expect you could use the text (string) and list functions to perform the merge. Please look here for more information: *…

Hi @Benjamin Peikes I believe you can do that with advanced field edits with JSON. Please take a look at the examples in this documentation to try to match up with your field types for the edit: https://support.atlassian.com/jira-software-cloud/docs/advanced-field-editing-json/ Best regards, Bill

Hi @Brian Eschen I haven't had a lot of success with the related issues branches. My work-around is to use JQL branches to re-create what the related issues would have returned. Perhaps give that a try. Best regards, Bill

Hi @Jerry Laster _Divim_ Inc__ As you suggest your vendor's products to the community, please consider updating your user name to include your company information, as described in the community guidelines for marketplace and solution providers: Identify yourself as a partner: Make sure the user is aware you are affiliated…

Hi @agladkikh You may want to check that marketplace vendor's documentation to see if they support that with automation. I suggest checking here for the specific product you are using, and then check their "support" tab: https://marketplace.atlassian.com/search?hosting=cloud&query=figma While waiting for the vendor's…

Hi @ANUSHA RAJU -- Welcome to the Atlassian Community! For a question like this on a specific marketplace vendor's product, you may want to check their documentation or contact the vendor directly. Here is the link to their information:…

Hi @Olga Kolov -- Welcome to the Atlassian Community! Disclaimer: I do not have advanced roadmaps... You can determine if there is a smart value available for a field using the method described in the article below. Basically, you find an example issue, use a browser to call the REST API, and then search for your field.…

I am glad to hear that worked for you! One more suggestion: you may want to use a different name for the created variable than {{key}} as that is the name of an existing smart value, and there is a risk it could end up resolving to a different issue in the rule.

Short answer: I do not know and I suspect "no". JQL is not a SQL. My understanding is that when you search status by name, it matches anything that matches...which is why filters, boards, and dashboard gadgets can have problems when team-managed projects are used within an instance...when the filter is not specific enough.…

Hi @Jennifer Lamont -- Welcome to the Atlassian Community! Agreeing with what Jack and Dillon suggest, I have a follow-up question: What is your concern with using multiple issues (parent/child issues) to track the work? You noted that: I use JIRA to manage marketing projects/traffic and for each project, I assign one…

Hi @Grygorii_sh -- Welcome to the Atlassian Community! There can be different status values with the same name and different ID values; this impact has increased with the addition of team-managed projects, where every project has its own copies of the status values. One approach would be to use a different REST API method…

Hi @Robert Mein Yes, and...to what Jack noted: there is an open suggestion to support one or multiple email addresses to receive error notifications: https://codebarrel.atlassian.net/browse/AUT-457 Best regards, Bill

Hi @Jack Arndt I do not believe this is in out-of-the-box automation for Jira (A4J) yet as there are a couple of open suggestions to add it. If you look over this thread you will some explanations of trying this using a webrequest to call the REST API from an automation rule:…

Hi @Brian Eschen -- Welcome to the Atlassian Community! You may want to consider posting your request as a new question with an image of your rule and the audit log. That will give the community more visibility and context to provide you suggestions. Thanks! Best regards, Bill

Thanks, and as I noted: in some cases extra spacing in the smart values is required and usually it is not. Just an FYI in case things don't work as expected for your rules. For example, in your post to the audit log the value does not appear to resolve to a number. Let's try three things: remove the extra spacing from the…

Thanks for the follow-up @[deleted] ! Would you post what you learned as a new answer here, and then mark it as "accepted"? That will help others in the community find solutions faster, as we cannot see the information about your support ticket. Thanks!