Bill Sheboy Expert

Hi @Clare Wall -- Welcome to the Atlassian Community! You may find those with a JQL search with the watchedIssues() function: https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#watchedIssues-- Kind regards, Bill

Hi @Wagner Silva [C] I believe this is a known problem for several Jira areas, not just automation rules: https://jira.atlassian.com/browse/AUTO-228 Please vote for / watch that issue to see any progress. Kind regards, Bill

Hi @Garret Zhang Would you please post an image of the audit log details showing the rule execution with that error? I wonder if there is another cause of what you are seeing? In the meantime... What is the scope of this rule: project, global, or multiple-project? That is relevant as all three scopes can create issues in…

Thanks; that helps clarify things! This scenario is normally solved by creating a combined filter for the projects, saving it, and creating a new Kanban board. This board is treated as read-only to prevent impacting the delivery teams' work. Clone creates synchronization and other problems, which are not easily…

Thanks for confirming that! There are three ways to access batches of issues with automation rules, depending upon your version (i.e., Cloud, Server, Data Center). They are: * lookup issues (will not work for your scenario based on the limited fields) * bulk-handling (will not work for your scenario based on the rule's…

Hi @Dan Kane -- Welcome to the Atlassian Community! Index cannot be used in functions (or apparently conditions) within the iterator. There is a defect for this in the public backlog for Jira Cloud automation, although it is unclear what the usage scenario was to drive that…

Thanks for that information, and FYI that I am using Jira Cloud and not Server, and so there could be at least three causes of what you see: Most likely one is the field is not in the Lookup Issues result: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 When Lookup Issues was added for Jira Cloud, it only had about a…

Hi @Akinlolu Awodiran This 3 year old question is about exporting the backlog issues, and not the timeline view. Please create a new question if you are having difficulty with something else, including some screen captures of what does not work as you expected. Thank you! Kind regards, Bill

Please try just leaving the field empty, with no selections or smart values.

Hi @philipf There is a lot going on in your question, so if I miss something, please let me know... The error you noted about a JQL query seems to indicate the scheduled trigger had no JQL (and thus no issues) but your rule is referencing "Current Issue" in a branch. That will not work. How do you identify the issues you…

Hi @Colter Sherley -- Welcome to the Atlassian Community! Have you tried using the format() function to set the date to the format you noted? https://confluence.atlassian.com/automation/jira-smart-values-date-and-time-993924864.html Kind regards, Bill

Hi @Nir Damari -- Welcome to the Atlassian Community! Based on what that article describes, it is trying to use an automation rule to set a number field with a counter. I do not believe there are any built-in dashboard gadgets which can show issue keys and a custom number field...with a link to the counted issues. Instead…

Hi @Peter Skokan What is the field type for Invoice Expiry Days? If it is text, you may need to add asNumber to convert it inside of the function call. Kind regards, Bill

Hi @Rita Saad YOUNES Do you have a REST API function in SharePoint to call to create the folder? If so, your rule could call the function using the Send web request action, as described in this how-to…

Hi @Arturs Kalnins 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 ideas.…

Hi @cho -- Welcome to the Atlassian Community! I am curious: what problem are you trying to solve by cloning all of those issues? That is, why do this? Regarding your questions, and without seeing your actual rule image and audit log details, my recommendations would be: * verbally explain the scenario to another team…

Hi @Amr Salem -- Welcome to the Atlassian Community! Is the Scrum Team Name a field in the issues? If not, it will not be found using the issue search with JQL: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-get And it what ways is that function not helping you?…

Hi @Narsha Bac First thing, there are some limitations to what you are trying: * If an issue has been in multiple sprints, the rule will need to decide which one to use * If an issue is in a future sprint with no dates, what do you want to happen? Next thing, confirm the type of your custom field. If it is a date picker…

Hi @Trudy P Claspill and @TJ I think that 50 limit is for subtasks in a single, create subtasks action. The other limits could be from the branching of 100, which is still below the 120 noted by @TJ and / or the processing time limit for rule execution. @TJ -- Please ask your Jira site admin to look at the global…

Successfully using automation rules requires learning and experimentation. If you read this question's posts, from beginning to end, you will find all of the pieces and techniques needed to increment a version name with an automation rule. Here are the documentation references which describe the rule features used to solve…

Hi @Tyler Woolstenhulme Just checking: what is your relationship to the vendor and the products you are recommending? If a member of that vendor's team, please note when recommending a marketplace vendor product ensure you disclose your affiliation to that vendor in your post wording. For more information about this,…

Thanks for that information. Please note using this approach reduces autonomy of agile teams as it may set expectations for people outside of the team that the forecasted dates are commitments, set long before sprint planning has occurred. Regardless of that concern... Challenges with automating these dates are: issue…

Hi! I also wonder about what problem is being solved, and if Jira is a good place to solve it. Regardless of that... Theoretically, one could call the admin REST API to get all users with the Send Web Request action, parse the response, iterate over the values, and then perform actions. * function to call:…

Hi @Maximilian Brand First thing: I am not using JSM and so my suggestions are based on what I know about rules, in general. With that out of the way... I suspect the Responders field / information is a list of users / objects. In that case it can be iterated directly, if it is available to a rule. So first try writing the…

Hi, @Maximilian Brand To help focus the conversation, let's use your question / thread to help solve this. Thanks! https://community.atlassian.com/t5/Jira-Service-Management/Send-email-to-incident-responders/qaq-p/2592921 Kind regards, Bill

I do not have much experience with cascading fields in rules, however I expect both the "parent" and child values would need to be checked for null...leading to more complicated conditions, possibly with nested conditions. (That is possible although tricky to get correct due to the permutations of null handling.) I…

Thank you for that information. Focusing on the original rule first: Looking at the audit log from your rule execution, I see only one Edit Issue result, indicating there was no parent issue to branch to. Is that what you expected for the issue CARGO-5488? Also... * If you navigate to the rules list, * select the complete…

That is curious...I recall similar posts when using the endOfDay() function that < should be used rather than <= for bounding within specific days: project = myProjectName AND created >= startOfDay(-5) AND created < endOfDay(-5) Perhaps try that first, with stand-alone queries in View All Issues (advanced search) to…

Hi @Elior Odinak -- Welcome to the Atlassian Community! The version name is text and so it can be alphanumeric. In your case you want to increment your prior version's name, which seems to be a number value. And so the rule would be just as you described: * triggered on version released * an action to create the new…

Hi, and thanks for the update info, @Monique vdB ...and because you asked for suggestions :^) What do people think of... * Changing the Notifications Feed (formerly known as Activity Feed) to show all entries with date / time rather than intermixed with date / times and relative ages? The consistency would help when trying…