Bill Sheboy Expert

Team effort on this one, so you can decide...it seems it took seeing the details (as Jack suggested) and then you trying to improve the JQL/rule out problems, that helped to solve this. I am just happy you got it working!

Sadly, not yet...For some reason the People-type field's design in team-managed projects does not support the user attributes like email address. Here is the suggestion to add that information, which you may watch/vote for to see progress: https://jira.atlassian.com/browse/JSWCLOUD-22200 The work-around depend on usage...…

Hi @Karyna Tyrnavska _SaaSJet When recommending a marketplace vendor product, please ensure that 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…

Your created variable SubtaskTime seems to be referencing itself in the smart value expression...and so that is null and causing the error.

This is curious...I tried your scenario and it worked for me... * I added a single-select People field to a team-managed project * triggered the rule from an issue * added an action to create a subtask for the trigger issue * and tried to set the assignee from the field, using both the field name and custom field id, with…

Yes, it is. Please use .name first to select the displayed value from the selection list. For example: {{issue.SelectListField1.name.asNumber}} https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/

Hi @Erin Blomert There is a open defect created today (12 October 2022) for this symptom. It impacts advanced branching for Lookup Objects, Lookup Issues, and smart value expressions creating lists. Please watch/mark as impacted here to see progress: https://jira.atlassian.com/browse/AUTO-179 Kind regards, Bill

Hi @Emma Hecht First thing, you seem to be trying to set the assignee in two places, with the field and in the advanced edit with JSON. Try clearing out the advanced edit. Next, would you please post images of your complete rule and the audit log showing details of a rule run? Those may provide context for what is…

Hi @Rogerio There are a couple of ways to do this, which you may read about here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/ Either use this syntax: {{issue.myCustomField.asNumber.plus(issue.myOtherField.asNumber)}} Or... {{#=}}{{issue.myCustomField.asNumber}} +…

Hmmm...Let's try this: try using that JQL stand-alone with advanced issue search to see what happens: parent = OP-903 AND summary ~ "Dev" AND status = "Backlog" AND "Doxxed" IS NULL That will rule out any field errors or search/JQL problems.

Until that suggestion/defect with People-type fields is addressed, the options are limited... * create a saved filter to detect when issues transition to that specific status, tell stakeholders about the filter, and let them subscribe to it at their desired cadence * add all the interested stakeholders as issue "watchers",…

Hi @Allan Vaifale I recommend discussing with your teams stopping the use of story points. You appear to be using time-based estimation for everything, and so using story points as a rounded version of time may just be confusing (and repurposing the value of story point sizing). Instead consider just using time as your…

Hi @Kateryna Which of your rules received that message in the audit log? If it was the one with the Issue Created trigger, this symptom can occur because the trigger happens faster than the data is available for the conditions. The work-around/fix is to add the Re-fetch Issue action immediately after the Issue Created…

Thanks, and let's try this again...with some extra condition checks for insurance :^) First question: will the child stories *always* have that text of "KYC" and "Dev", or are those subsets or examples of text? Let's assume they only contain those values. * trigger: issue transitioned to Done * condition: issue type is…

Hi @j.saceda With the Server/Data Center version of automation, I do not believe it is possible to edit a comment: https://confluence.atlassian.com/automation/jira-automation-actions-993924834.html That action appears to only be available with the Cloud version of automation rules. Kind regards, Bill

Until that defect/symptom is fixed I believe you are blocked for your use case. The only work-around would be to manually create, clone, or import issues...and perhaps disable that rule for a while.

Hi! You appear to have changed the JQL in the branch for your rule, from the original question and the new image posts...and neither one of those JQL values is going to match the sibling story's Summary field of "Dev" I feel I am missing what you are trying to do.

No worries, and I agree there are lots of things to improve in the Atlassian tools. I wish there was a reporting engine, like in competitor products, to allow just-in-time report definition and display. Teams never know what they will need to see as their work methods improve...and so fixed/narrow reporting is not always…

Hi @Chitrangada Wagh -- Welcome to the Atlassian Community! The built-in sprint reports support that information (scope change and rolled over items), allowing teams to review it and learn how to improve. For teams using the Scrum Framework, that can happen every sprint during the retrospective. A challenge is when teams…

That first log is correct and the second one is not. I just retested this and advanced branch over a smart value list is also not working, per that defect noted by @Manu Devos so I will add a comment to the defect.

Hi @drgilby Are you trying this in a team-managed project with the People field type? If so, automation rules cannot support that field type yet. Here is a suggestion to support that, which you may watch/vote for to see progress: https://jira.atlassian.com/browse/JSWCLOUD-22200 Kind regards, Bill

Hi @Jim Ralston Adding to Jack's questions... Would you please post an image of the audit log details showing the rule execution? That may provide some context for this symptom. Thanks! Kind regards, Bill

Hi @perla.miranda In your rule before the advanced branch, would you add a write to the audit log to show the value of {{varLoopValues}} then run your rule and post an image of the audit log details? That may help to isolate this symptom a bit. Thanks! As a reference for other readers, this question is following up from a…

Hi @Mary Prather Are you using a company-managed or team-managed project? Team-managed projects do not use the "Epic Name" field; they use "parent" to set the epic link for child issues. And company-managed projects have "Epic Link" and "Epic Name", but both of those fields are being sunset. You can use "parent" instead…

Hi @perla.miranda I just retested with my original example rule and it works as before. I suspect that your Module Count field or automation rule have changed to cause the difference. As this may take a bit of back and forth to resolve, please consider creating a new question for this, posting images of your complete rule…

Certainly! Here are a couple of examples, using the math functions and smart value list filtering, with references below... https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/ https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588 For the same…

Hi @kenneth.gomes Your hypothesis is correct about the rule scope: a lookup issues action (or branch, etc.) can only see the issues within the selected scope of the rule. Next regarding the % progress...first how do you want to measure progress? The image you show is of a parent and child issues. That progress indicator is…

Hi @Rio Chandra -- Welcome to the Atlassian Community! First thing, the documentation on match() states the "underlying implementation is based on Java's Pattern class and uses Matcher.find() to find matches." Note the "based on" part; I suggest using as simple of a regular expression as you can to get a match first, and…

Hi @James Williams I do not believe what you ask is possible with built-in automation features. When using a quick filter, the individual user is doing so from the browser they have open to access Jira. An automation rule cannot access the information for your browser instance. If you flip your use case around (and I make…

When using balanced workload with that JQL statement, the rule editor states that: The issue will be assigned to the user with the least amount of open issues assigned to them as defined by the jql. If multiple users have the same count, one will be randomly selected. For project scoped rules, only issues in that project…