Bill Sheboy Expert

Hi @Rahul Jith That is not possible yet, as you can see in this suggestion: https://codebarrel.atlassian.net/browse/AUT-1694 The challenge is the same as for Slack mentions: the different tools have different user accounts, and so you would need access to the user information in the destination tool: MS Teams. The…

Please try with the User Condition, as I described and as documented here: https://support.atlassian.com/cloud-automation/docs/jira-automation-conditions/#User user: user who triggered the event check to perform: is not in group criteria: your group name

Hi @Jack Wiltshire Lookup Issues uses JQL, and when you want more-consistent results to use the .first try adding an ORDER BY to the JQL. Without seeing your current, entire rule(s), it is also possible there is a timing execution problem in the rule causing this symptom. Kind regards, Bill

Hi @Fernando Estrada Have you confirmed the link type in your trigger matches what is happening in the issue? If you are unable to modify the source rule (which is a good idea for this use case), why not clone it, disable the source rule, and add the comment? Have you confirmed the rule's scoping? For example, is the first…

Hi @Jyoti Manandhar What checklist addon are you using? Would you please post images of your complete automation rule and the audit log details showing the rule execution? Those may provide context for the community to offer suggestions. Thanks! Kind regards, Bill

Hi @Steffen Schmerler If your service desk users are in a group, you could add a User Condition to check if the person who trigger the event (e.g. Issue Commented) is not in the group of the service desk users. Kind regards, Bill

I'm just another customer and so, IMHO... Jira tools seem oriented to many ways of managing work, and only have a few built-in things like Scrum-oriented or Kanban-oriented work practice support. That training link I provided can help close some gaps, along with the dashboard ideas Dave suggested. For example, let's say…

Hi @Timothy Thornburg -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this? I ask that question, as what you describe seems to be a symptom of other possible causes...such as: * the amount of work in progress (WIP) is high and the board is getting "cluttered", * things get…

Hi @Lorraine Gorman What is the trigger for your rule? If I assume it is Field Value Changed or Issue Updated, you could use the {{changelog}} entry for the field and {{toString}} as described here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--changelog-- Kind regards, Bill

Hi @Thomas Seubert Adding to Dave's answers... A Jira Scrum board, shows the current sprint. There is little value to show prior sprints on that board as that would distract the team from the current sprint's deliver. Regarding seeing any issues, you may find them using a filter with advanced (or basic) issues searches. As…

Thanks for that image. That appears to be a Business Project board, which is a type of Kanban board If you look at the right side of the page you will find a Filter icon/feature. Please check if any filters are applied to the board. If so, select Clear Filters.

Hi @478 Fatihah -- Welcome to the Atlassian Community! For company-managed projects, the board is a view of the issues based on the filter. If you look at the issue which is not displaying, does it match the board's filter? If it does, have you checked if there are any quick filters enabled for the board? If so, try…

Would you please post images of your complete automation rule and the audit log details showing the rule run for context? Those may help to explain this symptom. Thanks!

Hi, Max! I was wondering about team interaction, trust, commitment, and focus for scrum...versus rewarding individuals completing things. This can be a balance, and for some teams rewarding individuals may lead people to focus on "my work" instead of the sprint goal and what the team is trying to achieve. Thanks, Bill

To be fair, @Charlie Gavey does appear to be reviewing/updating the suggestions I have made in the public backlog for automation. Thanks!

Hi @Srikanth Vemuluri It is unclear what you mean by "in a notification". To access the summary of a subtask of the trigger issue, there are at least two ways: * use the {{issue.subtasks}} list and list filtering to find the one you want, or get all of them with {{#issue.subtasks}}{{summary}}{{^last}}, {{/}}{{/}} * use JQL…

Hi @Derek F I just did a quick test in a Company-managed Project, and here were my results: That last one has stopped working in rules but I believe still works in JQL and the REST API.

Greetings! I am curious...why are there two independent threads on this exact same question, from two different Atlassian automation product managers, posted within a week of each other? Here is the other one: https://community.atlassian.com/t5/Automation-articles/What-would-make-Automation-better-for-you/ba-p/2196258 That…

Hi @Shoshana.Patel -- Welcome to the Atlassian Community! Eventually team members want to answer questions about issues using JQL to search. So I would recommend this free one from Atlassian: https://university.atlassian.com/student/path/849533-gain-project-insights-through-jql One valuable thing about this one for…

Hi @Sarit Ashtar -- Welcome to the Atlassian Community! First thing: as you are using a marketplace addon and asking about automation rules, I suggest checking the vendor's documentation to learn what is supported. Some addons have calculated fields which may not be accessible from rules. Whilst waiting for an answer from…

Yup, "Due Date" is one of the messier smart values. I have seen multiple things work for that field in rules, and so checking with that how-to article can help when in doubt. And also...sometimes quotation marks are required when a field's smart value contains non-alphanumeric characters, such as {{issue."My custom…

Hi @Temur Khalilov You are using a team-managed project so I assume you are using Jira Cloud. When do you want to sum up these story and task values into the Epic? I assume it is when the value changes. One challenge with this rule is that Story Point Estimate can only be edited in the rule using JSON. So your rule would…

That should work for Server/Data Center or Cloud. In that rule you are showing, {{sprint.name}} will be the name of the sprint which completed and {{sprint.id}} will be the identifier. What do you see in the audit log details when the rule runs?

Hi @Max Twemlow -- Welcome to the Atlassian Community! That is an interesting idea for a scrum team...What about the unintended consequences of rewarding this behavior? Regardless... Yes, and...to Darryl's suggestion: It is possible that multiple issues could complete in a short window of time. Rather than check the Lookup…

Hi @Derek F -- Welcome to the Atlassian Community! Adding to Trudy's answer... Smart values are name, spacing, and case-sensitive. To confirm you have the correct smart value for a field, please use this how-to: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ Essentially you find an…

Hi @Benajmin Kun Please check your smart values in send email, as you have a typo in {{assignee.displayName}} And...you seem to reference an issue's fields outside of the Lookup Issues iterator; before it specifically. Try using {{thisassignee.displayName}} or {{lookupIssues.first.assignee.displayName}} for that one. Kind…

Thanks for that information. If your scheduled trigger is indeed using JQL to only find the Initiatives, using the Lookup Issues on the epics for each Initiative should work. As are reminder, the branch to parent is not needed. What is not happening as you expect, as your rule could be: * trigger: scheduled on JQL to…

Hi, Scott. Please post images of your complete rule and the audit log details showing the execution. Those may help uncover what is happening. Thanks! Until then...my rule was using Story Points, and if your custom field is not a Number type, you may need to convert it with asNumber to make this work.

Hi @Ryan Lagola Yes, that is possible with the Automation for Jira addon. There is a free (Lite) and a paid (Pro) version for Server/Data Center Jira, so check with your site admin if you have either of these. https://confluence.atlassian.com/automation/get-started-with-jira-automation-993924596.html I recommend creating a…

Your rule is split into a a couple of images, so I am not quite following the situation...How about this example. * some rule steps... * create a story #1 * branch on most recently created issue* create subtasks A, B, C * create another story #2 * branch on most recently created issue* create more subtasks D, E, F * more…