Bill Sheboy Expert

Hi @Javed Ahmad -- Welcome to the Atlassian Community! No, there is no built-in reporting to extend to that time range. As workarounds you could either export the Jira issue data and build reporting in another tool (e.g., a spreadsheet) or investigate the Atlassian Marketplace for alternative…

Hi @Semih APAYDIN -- 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 @Kayleen Cucugliello For the post shown above referring to "Subtotal", that is a custom field in their Jira site / project. If you do not have a field with that name, it would not be present. If that does not help you, I recommend creating a new question and perhaps adding a link to this one for context. That will…

You are using Jira Data Center's version of automation, and that does not have advanced branches yet, so I am unclear how you will iterate over the values. Assuming you have figured out a way to do this... When splitting a list, the get() function may be used. That is 0-based, and so: * first entry:…

Hi @Josh There are several open suggestions related to adding the Team (and other missing fields) to the dropdown list for automation actions. Here is one of them: https://jira.atlassian.com/browse/AUTO-525 Kind regards, Bill

Getting the maximum occurrences of specific values in a multiple-select field, or the count over a threshold, would be challenging with an automation rule. With the current features of rules, I believe this could be done by saving the counts for each possible value and then using a series of comparisons. There may be other…

To enter the sprint id values in the Edit Issue action you may: * type in a smart value expression in the Sprint field * it will appear below the field * when it appears, select it to use for the edit To find the sprint id values you need, you can see them when creating a query. For example, using Filters > View All Issues…

To use the same value from the trigger, please enter the value {{worklog.started}} in the Date Started field when you log the work.

Awesome; I am glad to learn that helped. Please consider marking this question as answered to help others in the community with similar needs find solutions faster. Thanks!

I recall this symptom could occur if the user account did not have create / edit issue permission...although that seems unlikely for this case. There was an defect a few years ago for this symptom, which was fixed by Atlassian: https://jira.atlassian.com/browse/JRACLOUD-74103 I recommend working with your Jira Site Admin…

Hi @Ernests Lipko Jira org admins get additional notifications, related to admin functions. For those, I recommend checking the global, site audit log to try to track down the cause(s). For issue-related actions leading to notifications, you describe you did check the automation rules. Have you also checked any marketplace…

Please note your expression is missing the # before changelog, and so it does not evaluate correctly.

Like any programming language, Atlassian Automation has its strengths and weaknesses. As it continues to evolve with new features, keep watching for community posts and the weekly release blog of improvements that may help make your scenario easier.

Hi @lila Would you please post images of your current rule action with the JSON attempted and of the error you are seeing? Thanks!

What type of project are you using: team-managed or company-managed? If using team-managed, the project admin can add those fields. If using company-managed, your Jira Site Admin will need to add them.

Hi @Elena Papa Yes, that is possible. The rule could be triggered on Issue Created, and use either a lookup table or if / else conditions to add the issues to the respective sprint by the sprint id values. And...I wonder if instead of putting these issues in "sprints" to arrange them in the backlog, you could use Quick…

Looking at the audit log, the JQL is not correct. Is your custom field cf[30902] a multiple-select option field? If so, please try the IN syntax and not the CONTAINS ~ one: project = BCC AND cf[30902] IN ( {{#triggerIssue.Target Specialties.value}}"{{.}}"{{^last}}, {{/}}{{/}} )

Hi @Jeffrey Bistrong I have not tried that in a while, and I recall you add the "optionId" attribute to refer to the parent. For the example you show, if "8.0" with an id "13094" is the parent, adding a child could be: { "disabled": false, "optionId": "13094", "value": "stuff after 8.0" } Later when you view the complete…

Hi @mateus.oliveira To find the issues with one (or more) of the same values selected as the trigger issue, you could use JQL like this: project = yourProject AND yourSelectionField IN (value1, value2, etc.) ORDER BY Key ASC To obtain the values from the trigger issue for the IN expression, use a list iterator over the…

I do not believe it is possible to log work on behalf of another person, and I recall there are open suggestions to add that feature.

Hi @Ward Schwillens_ Schwillie A couple of options using automation rules are: * Whenever work is logged for a Task or Subtask, log the same amount to the Epic. Then when you need the total (or details) examine the Epic. * Whenever work is logged for a Task or Subtask, sum the total for all child and grandchild issues and…

Hi @Thomas Vial Apparently that information is not available with the public REST API yet. One workaround would be: * using a multiple-project or global scope, automation rule * use the Lookup Issues action with JQL on the linked "implements" issues, and based on their type, gather their child issues also * use their…

Several of those smart value expressions you show are invalid and will not process. The example I provided will work if that is the correct smart value / custom field id for your field. Have you confirmed the smart value for your field, as I described in my first post? To provide more context, please post images of: * your…

Again, I am using Jira Cloud and not Data Center, and so cannot test what I am suggesting... Perhaps try splitting the values, encoding, and then joining them with commas.

Hi @Shasheekant Patel What is the symptom the other person is seeing that leads them to believe the label "Subtask_Tree" is not available. Labels are shown / recommended in the field after they are first used. Has the label been used in your site yet? Kind regards, Bill

Hi @Nik Rogul -- Welcome to the Atlassian Community! A created variable cannot be accumulated that way. And even if it could, the variable would not be available outside of the branch. (Branches which could be on more than one thing are run in separate processes, and the variables created inside vanish once the branch is…

Hi @Jonathan Scott -- Welcome to the Atlassian Community! One of the limitations of automation rules is: once inside of an iterator, no data from outside is visible / available. That is: {{#issue.labels}} ...inside the iterator, can only see labels, and lower... {{/}} And so your lookup table is not visible. A workaround…

Hi @Yannick TEMPORAL -- Welcome to the Atlassian Community! To select the value for the edit, please use advanced edit with JSON for the field: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Single-select-custom-field For example: * remove the selection of Type de demande from the…

If the user names are comma-separated values (CSV), this seems to work, probably up to some search limit of 50 users: yourJiraURL/rest/api/2/user/search?query=username="Alice","Bob","Eve" And so if your input can be made into a CSV list, with surrounding quotation marks, please try that approach.

As I already described, the custom field is not "visible" inside of the iterator on versions. Only data from versions (and lower) is visible. I do not believe a greater than date from a custom field search of version, release dates is possible with an Atlassian Automation rule with Jira Data Center. If you know the exact…