Bill Sheboy Expert

Okay, let's try using smart value, list filtering with the issuelinks smart value! This would replace the lookup and advanced compare, providing the Summary value directly. I am using Jira Cloud, so you may need to experiment a bit. In my example below, I am looking for any issues linked to the trigger with a link type of…

Which version of Jira Data Center are you using, as I believe that action was added over a year ago: https://confluence.atlassian.com/automation/jira-data-center-automation-release-notes-1018767858.html#JiraDataCenterautomationreleasenotes-9.0.0-9.0.19.0.0-9.0.1

No, you want to uncheck the option on the rule triggered on Value Changes for Date Closed. By the way, that option is disabled by default to prevent looping and other race-track errors. It is normally only enabled when you specifically want one rule to trigger another. I recommend reviewing your rules to understand why it…

Yes, I just copy-and-pasted in the values as that is a technique to hard-code values in rules using variables. Hmmm...your audit log clearly shows there are no leading / trailing spaces for the values that could break the assignment. If you look at the issue history for the created issues, is anything else perhaps…

Just use 1 and not {{1}} in that expression and you should be all set. And...do you actually want to use customfield_12848 5 times in that expression for the conditions, or should it use the other custom field ids / values: 12919, 12866...?

Hi @Brittany Montgomery From what you describe, your first rule triggered on Issue Transition is triggering the other rule when the field is updated. Please check the details at the top of the rule triggered on the field change as you likely have this option selected / checked and it should not be: Check to allow other…

Hi @Diego Martínez -- Welcome to the Atlassian Community! As you are using linking to connect the issues, I recommend using the Lookup Issues action with JQL to get the linked Epic, and then access the Summary. * trigger: issue transitioned * condition: issue type equals Cambio * action: lookup issues, with JQL to get your…

Yes...you may add this to the JQL for the Lookup Issues action to exclude the trigger issue: AND key!={{triggerIssue.key}}

Hi @Trudy P Claspill I have not been able to recreate that symptom. Instead, my test rule was able to successfully assign the issues during issue create (with same project / type as trigger) using either the branch variable directly in the Assignee field or with JSON. This also worked for Epics and Story level issues, and…

Hi @Rafaella Sena -- Welcome to the Atlassian Community! First thing, where are you learning about this syntax for filtering a list? That is not a valid syntax for filtering a smart value, list, and this is the second post today I have seen with that syntax. --This does not work! {{lookupIssues.filter("status.category.name…

Thanks, and I seem to recall posts where those did and did-not work in Jira automation rules, given the whole "underlying implementation is based on..." thing.

Thanks, @Barbara Szczesniak Based on the comment from @PJ Zaiac I thought the new one would appear for selection (once the others are done), yet I do not see it or it automagically "selected" in the profile. Guess I'll wait a bit to see if it eventually appears :^)

I am glad to learn that helped, and for your second question... You could use a similar syntax to count them for division. Perhaps like this, using my same example from above, were I substitute 1 for the values in the conditions: {{#=}} ( 0{{#if(customfield_12863.lte(200))}}{{customfield_12863}}{{/}} +…

Hi @rhylton By default, the state of the trigger issue(s) when it loads is used for the rule actions, conditions, branches. When your rule edits the issue and you want that value to be used by later steps, add the Re-fetch Issue action after the edit. This will slow the rule a bit and reload the data before proceeding. The…

Hi, community! I am curious: has anyone actually seen this new one in the challenges list yet? Thanks!

As you already have a rule started, try that last bit to see if it helps with the Initiative vs Story as the trigger. If not, I could envision 4 rules: * triggered on the Initiative transition to Discovery, call the recursive rule #2 to create the Squad issues * triggered on incoming webhook, add one set of Squad issues,…

You may do that with the Lookup Issues action I described. I recommend finding an example issue and writing JQL to find the issues you want to count. Then update the JQL to be used in the rule with that action.

Hi @Anetha -- Welcome to the Atlassian Community! What have you tried thus far to solve this need? If you have a rule that is not working as expected, please post an image of the complete rule, an image of the audit log details, and explain what is not working as expected. If you have not yet started a rule, I encourage…

Thanks for the additional details, Diane! On your last question: If it is a timing issue, something hasnt synced? or something? even though the lookupIssues finds the key but the branch cannot find the key, is there something that can be done, a delay, a something? I hypothesize this is the built-in behavior where JQL…

I am glad to learn it is working now...and, I have intermittently seen that symptom when content is being moved (or deleted) in the community by one of the managers. For moved stuff, waiting a minute or so normally clears the problem.

Hi @Igor Stojkovic Please review the community guidelines regarding necro-posting to older threads. Thank you. https://community.atlassian.com/t5/custom/page/page-id/rules-of-engagement Kind regards, Bill

Yes, you could use that expression I provided to calculate the percentage in one step to set the field. I have not seen the .filter() syntax documented as an automation feature and so that appears to be one of the problems: -- This does not work: {{lookupIssues.filter(status = "Done").size}} Instead use this to count the…

When editing the issue and using the math expression within the function call, please try using the divide() function rather than the / symbol...although I do not know if that is supported for Jira Data Center automation. { "fields" : { "Target end": "{{issue.Target…

@Darryl Lee that symptom may have been caused by newlines in comment body, causing the match to halt after the first "record". I believe the workarounds for that are to replace all the newlines before the match (and return them later, as needed).

Hi @Fares Laroui_Vectors_ Thank you for this information. Your post indicates the app is free and the marketplace page indicates it is the first beta release, with no additional information provided on future release plans. To help the community decide any usage, is the plan to convert to a paid application after a beta…

Hi @Marc -Devoteam- As a reminder, custom fields are not yet supported for lookup issues with Data Center: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 Although they should not be needed for the scope of this question. Kind regards, Bill

Hi @Gonzalo Perez Alonso To isolate the problem, I recommend writing this to the audit log after the Lookup Issues action, then re-test your rule: Story point values: {{#lookupIssues}}{{key}}:{{Story Points}}; {{/}} Story points sum: {{lookupIssues.Story Points.sum}} That will confirm the values are set for the issues in…

Hi @Sidharth verma Have you already solved this question? If not... What version of Jira are you using: Cloud, Server, or Data Center? That impacts the features available for automation rules. For example, with Jira Cloud there is an Advanced Branch feature which supports iterating over a smart value list, such as the user…

Hi @Eric Witkowski -- Welcome to the Atlassian Community! For your first question about the filter options for the timeline view: * The Labels option is only shown when issues in the project have values in the Labels field. If you check your "project 1", I suspect that no issues have such values. * Your "project 1" is…

Hi @Simon Jones First thing, I recommend always prefixing variable / table names in rules to avoid any problems with smart value name confusion. For example, using varCustomField instead of customField for the variable name. Next, when using the "add" with the labels field in JSON, please use the "update" rather than the…