Bill Sheboy Expert

As you want to filter the added labels for ones containing "_Dpt" you may first filter using the match() function and then iterate over the results. For example... * action: create variable, to extract the found matching additions* name: varMatchingLabelsFound * smart…

Wouldn't the leader of the people on the team and the entire team already know this information from paying attention and asking questions during 1-1 conversations and the daily scrum (stand-up), respectively? For example, a forecast is provided, and after repeated daily scrums no concerns are raised and progress seems…

Hi! There are several open suggestions to add enable / disable for the existing animations (i.e., to help with app performance), but I do not see any in the public backlog yet for disabling the new animations in Jira Work Management projects. Perhaps add a suggestion or use the feedback mechanism to suggest an enable /…

Again, please post images of your complete rule and audit log details showing the rule execution. Those will provide context to offer better suggestions. Thank you. When you describe "whenever the Logged Hours field is updated", do you mean a custom field with that name or that you are using the built-in time tracking…

Hi @Victor -- Welcome to the Atlassian Community! Without seeing your entire rule... Perhaps try using the related issues condition with JQL, checking for no issues matching, and use the exact-phrase syntax for the CONTAINS operator to escape the quotation marks:…

Hi @Morgan Ford -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide…

Hi @Jeremy Davis From which field are you getting the assignee to use for the created issues? If it is the same one as used in your advanced branch, that smart value expression could be set to the assignee field when the issue create action is used. If it is a different field from the advanced branch, what you describe is…

It appears the action options are different for Create Version between Cloud and Server / Data Center apps. Regardless, this seems like a bug to me as the current scope in the branch should determine the "current project". After a quick search, I could not find a similar defect in the public backlog. I recommend working…

Hi @Christian Adding to Kalyan's suggestions... Something to consider for a scenario like this is context and edge cases: * What problem are you trying to solve by doing this? That is, "why do this"? * When do you want this linking to happen: at issue create, when the field changes, etc.? * What do you want to happen if…

Hi @Walter Buggenhout Heads up: that link to the article appears to be broken. Thanks! Kind regards, Bill

Hi @Bulingzi_ Su _KW-BER_ DEBE_ -- Welcome to the Atlassian Community! Those other reports are not available for team-managed projects, and there are several open suggestions to add them. Please watch / vote for these to see any progress on them: https://jira.atlassian.com/browse/JSWCLOUD-17787…

Hi @Nils Herhaus Based on the rule you are showing, I hypothesize your trigger does not have JQL as you want to send one email with a list of issues for each assignee. If that is correct, your email body is referencing the {{issue}} smart value, but that is not available. For your case, I believe you should use the…

Hi @Mateja Leskovec Yes, and...to Trudy's suggestion: you could also try using the same JQL with the Related Issues Condition to check there are no issues matching the criteria: https://support.atlassian.com/cloud-automation/docs/jira-automation-conditions/#Related-issues Kind regards, Bill

Thanks to you and the team, @Simon Chan ! That is a very helpful improvement for finding rules. I look forward to seeing any filtering options for the audit logs and other rule content / attributes: triggers, smart values referenced, etc. And perhaps features to support automating documentation of rules in other tools like…

Hi @Shannon DeVico First thing, I am using Jira Cloud and not Data Center, and so my suggestions are based on what I know about rules, and not Data Center version. With that out of the way... In the Create Version action, which project did you select: Same Project, Same Project as Trigger, something else? When I tried this…

Hi @d.kamposos -- Welcome to the Atlassian Community! I recall there are known problems with the changelog accuracy of list / multiple-select fields in automation rules, and I recommend fully testing for any use of smart values such as {{addedfieldChange.values}} That being noted... It may be possible to do what you ask…

Hi @Pier Nicolò Yes, and...to the other answers suggested to do this with an automation rule: I recommend using a Lookup Table for a scenario like this, eliminating the need for a list of if / else conditions. Your team's mapping of t-shirt sizes to story points could be entered in a table with key / value pairs, allowing…

Hi @Wojciech Wardaszko In this updated article about lookup tables: https://community.atlassian.com/t5/Automation-articles/Update-Create-lookup-table-action-improvements/ba-p/2427798 It shows the entries function to return the rows as a list. Your advanced branch could use: * smart value: {{theUsers.entries}} * name:…

Hi @Hajnal Daniel -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide…

First for your question, you could add your calculated field, ICE Score, to the trigger's list of field to check, and any change will lead to recalculating it. However that will not make visible that someone altered the value. When you need to see that, I recommend: * copy this rule from the rule list * change the name to…

Hi @Zsigmond Molnar -- Welcome to the Atlassian Community! As this is a very old thread, I recommend creating a new question to ensure the maximum number of people see it to offer suggestions. You could include a link back to this thread if you believe it helps provide context. Thanks! Kind regards, Bill

Hi @ganna_kyselevych I am curious about your question... You ask about "VS time", which I am guessing means "value stream time" or some interpretation of lead time or cycle time. And you note using sprints, and so there is probably a team using Scrum. What problem are you trying to solve by measuring that number for…

Hi @Mouad Azizi -- Welcome to the Atlassian Community! There are several ways to do this, and all require additional consideration of cleanup, edge cases, etc. to manage the different scenarios. Before considering any of those, what problem are you trying to solve by doing this? That is, "why do this?" Knowing that may…

Hi, and thanks for this topic, @John Funk Here is one I have pondered many times over the years (where the details change but the concerns remain the same)... With the inconsistent changes in feature sets (or lack thereof) between Jira areas (e.g., CMP, TMP, JPD, issue searching / views, dashboards), often only…

Hi @Muhammad Moazzam Hassan For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to…

Hi @ARAVINDAN.KUMAR -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide…

In automation rules, {{triggerIssue}} always refers to the issue(s) which triggered the rule, and {{issue}} or "current issue" can change, based on location in the rule. For example, please note the values in this template of a rule: * trigger: some trigger; {{triggerIssue}} and {{issue}} are the same * condition: some…

Hi @wstromm -- Welcome to the Atlassian Community! For Jira Data Center's version of automation, custom fields and many other fields are not yet supported for the Lookup Issues action. Please watch / vote for this suggestion to see progress on adding them: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 There are two…

Hi @Sam Adams -- Welcome to the Atlassian Community! As @Kalyan Sattaluri described with the linked thread, that smart value expression must first be put into a created variable, and then parsed to get the distinct values. Please review the other thread to understand the technique. Next, when using issue edit for a field,…

Hi @Scott H Adding to the other answers, you may want to look at the overview information, rule examples library, and documentation to help get started: * https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation *…