Bill Sheboy Expert

Hi @Tim First thing, well done trying to diagnose this one for your rule! This seems to be a known problem, and here is a suggestion to fix it: https://jira.atlassian.com/browse/AUTO-890 Your workaround could be to use the group name to get the users, adding the urlEncode() function to manage the embedded spaces:…

Hi @Ray Balmeo Cagayon 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 offer…

Hi @Myrthe van Marissing -- Welcome to the Atlassian Community! Adding to Kalyan's suggestions... Myrthe, you noted "Start Date field is customer made field by ourselves." But there is already a built-in field with that name. If you did indeed add a custom field, why create the duplicate field name as that may cause…

Hi @Aron Gombas _Midori_ As a reminder, when recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Community online guidelines | Marketplace + Solution Partners | App Central…

Hi @Marcel Rossouw Your rule needs one adjustment to work as you asked: add a branch to the most recently created issue. * trigger: manually created * action: create issue * branch: to most recently created issue* action: add watchers Rule actions, conditions, branches are based on context of what is the "current issue" at…

The rule you now show is very different from your original approach, and is incorrect for different reasons. As you appear to have already solved the need using if / else conditions, perhaps use that approach and remove this other rule.

Please show an image of your Advanced Branch details. If you are trying to send one email for each assignee, please see the suggested solution I described earlier. As your rule is written, it appears you are trying to send email for each issue.

Hi @hpatani -- Welcome to the Atlassian Community! That is not easily done, except for a few built-in fields that can use the CHANGED operator for JQL: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#CHANGED A workaround is to use a date / time, custom field, setting the value when the issue is…

FYI, when responding please try to stay with the same thread. That will help others reading your question in the future know if there are multiple solution approaches to try. Thanks! And thanks for the clarifying information. That dependency issue makes sense to me for flagging the backlog items. A workaround would be to…

Hi @Rees, Ian You appear to be using this function, correct: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-project-versions/#api-rest-api-3-project-projectidorkey-version-get When I call that without a matching text to a version, it comes back immediately. For which versions is the person searching?…

That version information indicates you are not on Jira Cloud; I do not believe there is any UI in Jira Cloud showing version information (except for the addons / apps). Here is the list of Server / Data Center release notes: https://confluence.atlassian.com/jirasoftware/jira-software-release-notes-776821069.html Again, I…

Hi @oliver.boban.alempijevic -- Welcome to the Atlassian Community! Yes, and...to Nick's suggestions: I strongly encourage reading the packaging guidelines and automation limits documentation. Some actions count (while others do not) for usage, and so rules may be structured with that in mind to help manage usage better. *…

Hi @kranthi kumar g j -- Welcome to the Atlassian Community! First thing, I am using Jira Cloud and not Data Center, and so cannot test my suggestion. I believe the default attribute for Status is the id and not the name. Perhaps try adding .name after the status field to compare to "CANCELLED". Also, please confirm the…

Hi @Ben Hart I recall the easiest way to do this is: {{#now}}format="toMillis"{{/}} That will return the UNIX timestamp to milliseconds. If you need some adjustments at the same time, such as incrementing a field, this would work: {{#issue.Start date}}func=plusMonths(1), format="toMillis"{{/}} FYI...I also did the…

Hi @Jonathan Chatfield There is a typo in one of your log write smart values: subtask should be subtasks: parent subtask count: {{issue.parent.subtasks.size}} I recommend adding prefix text to log entries like this to confirm which value is logged. Kind regards, Bill

Regarding that error, please check your workflow to see if a field is set by the transition. Regarding logging the values, once inside of the branch, you may refer to it as {{issue}} in a Log action, such as with this: Key: {{issue.key}} and Status: {{issue.status.name}}

Hi @Bill McMillen First thing, where are you seeing an indication of "blocked days" in Jira? Is this a report, a dashboard, a custom field, a marketplace addon, or somewhere else? I am not using the Premium license level so perhaps that is a feature of that level. Back to your question... My guess is any suggestions may…

Hi @Tom Elfers That is not configurable for a team-managed board, and there are several suggestions to make it an option for users. Here is one example, which you may watch / vote for to see progress: https://jira.atlassian.com/browse/JSWCLOUD-21257 Kind regards, Bill

What I observed was this: * For a team-managed project, the Epic option was only listed in the Group By dropdown when there were epics issues in the project. When no epics existed, the option was not displayed in Group By. * For a company-managed project, I am inconsistently seeing Epic displayed or not, in the Group by…

Hi @Amy Chang What have you done thus are to solve this need? If you have an automation rule and it is not working as expected, please post an image of your complete rule, the audit log details, and describe what is not working. Those will provide context for the community to offer suggestions. If you have not started a…

Hi @vruttant.mankad -- Welcome to the Atlassian Community! Please post an image of the audit log details showing that error message. That will help provide context for this symptom. Until we see that... First thing, please describe the problem you are trying to solve with this rule. That is, "why do this"? Knowing that may…

How do you know the "first subtask"? Can it be identified by a field or sort order of fields? In your response to John, you noted it was this one: {{issue.subtasks.get(0).key}} If that is always the case, you could use this JQL: key = {{issue.subtasks.get(0).key}} However that may create problems if anyone re-orders the…

Hi @Sjoerd Bernards -- Welcome to the Atlassian Community! There is nothing built-in to automatically create a Jira issue for a failed rule execution. One workaround would be to use email rules in your email application to raise the visibility of the received email, such as with flagging, urgency, alerting, etc. Another…

Hi @Fredrik Carlsson -- Welcome to the Atlassian Community! Have you confirmed your project has any Epic issues? When I try this with a team-managed project with no Epics in the project, the Epic option is not shown under Group By on the board. As soon as I add an Epic issue to the project it becomes available. Kind…

I was suggesting to add to your branch JQL (or replace it with): key = key of the desired subtask That will ensure you only get the one you want.

No worries, as some of the Atlassian documentation can be challenging to confirm which features work with a specific version of automation rules. Checking the top of the pages for any disclaimers / context info from Atlassian helps. The non-Atlassian information / videos (and bot agent answers) can be even worse; they are…

Thanks for that information. The "more options" and "additional fields" sections of the Edit Issue Action use JSON, as described here: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/ However you should not need those for your scenario, as the field could be selected from the dropdown…

Hi @Zach Are you using Jira Cloud or Server / Data Center version? The {{issues}} (note the plural) smart value is only documented to work for Server / Data Center. For Jira Cloud, please use the Lookup Issues action and {{lookupIssues}} smart value. Back to your question: please try smart value, list filtering to make…

Hi @Sabyasachi Samal To assist with automation rule questions, context is needed. Please post the following to help the community offer suggestions: * 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 with any…

Hi @Pandeeswaran Subburaj -- Welcome to the Atlassian Community! First, this is an older thread and I recommend creating a new question rather than adding to it. That will ensure the maximum number of people see it to offer suggestions. When needed, you could add a link back to the earlier thread for context. Back to your…