Bill Sheboy Expert

Let's try some writes to the audit log to diagnose this... Please add an action to write to the audit log after the Lookup Issues action, then re-test: looked up issues and story points: {{#lookupIssues}}{{key}}: {{Story points}} points; {{/}} Based on what you described, that should produce something like this: IL-46268:…

Hi @Tim Larkman -- Welcome to the Atlassian Community! Adding to the other suggestions provided: People-type fields (e.g., your Business Owner field) do not provide the email address to automation rules at this time: https://jira.atlassian.com/browse/AUTO-519 The two possible workarounds are: * Using the accountId from the…

Hi @Eloise Taylor Just an FYI... Regardless of what the UX indicates, all People-type fields in team-managed projects use the JSON array syntax (i.e., multiple-selection) even when a single-selection, user option is enabled. When in doubt what automation rules (and the REST API) are needing, please use this how-to article…

Hi @Kelvin Teng Adding to Trudy's suggestions... Do you want to replace the values in the destination issue's Affects Versions field or add to the existing values? What is the type of your source, custom field: multiple-selection Version, multiple-section Option, something else? If you want to replace the values and the…

Hi @Kathy Dickason You are correct: for Jira Server / Data Center automation, the Lookup Issues action only supports a small number of fields at this time. There are two possible workarounds, depending upon your needs. To use the average value you describe to set another field, you may use the Send Web Request action to…

Hi @JCameron Well done solving your own question and please note Atlassian is aware of this symptom (according to other community posts). By default, the Automation for Jira user has permissions to do most non-administrator things in Jira, but JPD is a different product and has a separate licensing model with named /…

Hi @rob.jeal Adding to Trudy's suggestions and your findings... If that option to allow rule trigger was enabled for a while, perhaps it was selected incorrectly by a rule-writing person. And thus their rules may be consuming your monthly, automation usage limit:…

Gilad, what type of project are you using: Company-managed or Team-managed? You may find that information in the project list or at the bottom-left of the screen expanding area. Why that matters... Company-managed projects use the Story points field, and Team-managed projects use the Story point estimate field (even though…

In the add watchers, please try using this instead: {{varMentionedUsers.split(",").asNumber}} That will confirm if a number is required (rather than text from the variable).

Hi @Wayne Bryan For an automation question like this, context is important... 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…

Hi @Piotr Intres -- Welcome to the Atlassian Community! Without seeing the details of your automation rule and the audit log for the rule execution... Those two time tracking smart values have different purposes: * {{issue.timetracking.timeSpent}} is the "pretty print" one, making it human-readable. And thus it is text…

Awesome; I am glad to learn it is working for you!

Please post an image of the audit log details showing the rule execution. That may provide more context for what you are observing. Thanks!

Hi @Gilad Waldman I see two things with what you show: 1) There is no Lookup Issues action in your rule to gather the issues. 2) The expression you show is missing the closing parenthesis and digits for the ROUND function. In my original post, I showed this:…

asNumber is a function and so I advise not using that as a variable name to avoid confusing the rule. Next, you are trying to add multiple things at one time as watchers and so that could be causing challenges seeing what works, or does not. Let's simplify to one single test and evaluate what happens: * trigger: issue…

What type of project is this: company-managed or team-managed? And...for the multiple-selection user picker field Tester, please try this to mention all the selected users: {{#issue.customfield_49919}}[~accountId:{{accountId}}]{{^last}}, {{/}}{{/}} Please note well: smart value expressions are case-sensitive, so confirm…

Hi @Mc Darryl Atacador -- Welcome to the Atlassian Community! That error indicate the Transition Issue action needs an issue and none is provided at that point in the rule. Does your Scheduled Trigger use JQL to supply issues to the rule? If not, that would explain the error message. Kind regards, Bill

Hi @Maximilian Floß Please try using {{issue.project.key}} instead of {{issue.project.name}} in the JQL expression. Smart values can be used in the JQL for the Lookup Issues action. There are exceptions with dynamic smart values, and they may be worked around by first storing the JQL in a created variable to force the…

Hi @Steve Holland For a multiple-selection, user picker field an iterator must be used, as described in my earlier post. If that does not help, please post images of your complete rule, the action where the mention happens, and of the audit log details showing the rule execution. Those will provide context to help explain…

Hi @Joanna Weir -- Welcome to the Atlassian Community! Sorry for the delay in responding as I have been offline for a few weeks. I am glad to learn you got something working, and as a follow-up...Are you using Jira Server / Data Center or Jira Cloud? I ask because the {{issues}} (please note the plural) smart value is only…

Hi @rajeswari saravanan As this is an older thread, I recommend creating a new question, and perhaps linking to this one. That will ensure the maximum number of people see it to offer suggestions. When you create your question, please include: * explain the problem you are trying to solve; that is, "why do this" * include…

Hi @Troy Sorry for the delay in responding as I have been offline for a few weeks. Regarding "blocked", if you mean the Flag feature for issues, that time cannot easily be found with out-of-the-box features. You could create an automation rule to detect and record the start of blocked date / time, and then use JQL to to…

Hi @christopher.branaman Sorry for the delay in responding as I have been offline for a few weeks. Rules which have multiple-project or global scope are managed for the entire site in global settings...and so a Jira Site Admin (or Org Admin) needs to manage them. The reasons are likely due to potential impact of such rule…

Hi @Devlend Maul Sorry for the delay in responding as I have been offline for a few weeks. Did you try the expression I suggested? That will first split() on spaces to reduce the scope of the match() and produce a list of user account id values. Then you will need to use an iterator of that list to create dynamic JSON to…

Hi @Chris S_ Sorry for the delay in responding as I have been offline for a few weeks. First, I believe sub-tasks are children of Story, Task, and Bug issue types, and not of Epic ones. Let's assume you meant the Epic has one or more Stories, each with zero-to-many Sub-tasks. To validate all of them are completed before…

Hi @Chris M_ Sorry for the delay in responding as I have been offline for a few weeks. Lookup Issues can gather a list of issues. Have you confirmed there is one-and-only-one returned? And, it appears from your screen image of the Create Variable action there is a leading space before the smart value. Please try this as…

Hi @Ewelina Kluska -- Welcome to the Atlassian Community! Sorry for the delay in responding as I have been offline for a few weeks. And, as this is an older thread, I recommend creating a new question and perhaps adding a link back to this one. That will ensure the maximum number of people see it to offer suggestions. Back…

Hi @Sunny Liao Adding to the suggestions from Trudy... You describe checking for updates to issues within a time frame, send only one email communication per assignee spanning their issues, and then update the issues. There is no nested branching to support a scenario like this. As Trudy described, your branch on the…

Hi @Sarah Isaacs As Marc was describing, the backlog (and board) can display at most 5000 issues: https://community.atlassian.com/t5/Jira-articles/Jira-boards-and-backlogs-can-now-show-5-000-issues-in-company/ba-p/2708797 After that point, paging or filtering is required. If you only need a count of how many issues are in…

Hi @Garn Sorry for the delay in responding as I have been offline for a few weeks. Thanks for confirming what the variable contains, as the one with just the id should work in the action. (Unless those ids in Jira Data Center are numbers...in which case conversion is needed with asNumber.) Would you please post an image of…