Bill Sheboy Expert

The answer to that is a bit complicated...in general the limits are related to the processing SLAs. It appears they have changed since I last looked so I suggest reviewing this information below, look at your rule structure, and then determine if there will be…

Hi @Kolawole Aderupatan -- Welcome to the Atlassian Community! Here are some questions to help focus what you ask, as these will help the community to offer suggestions: * What have you tried so far to solve this need? * What addon/extensions do you have for your Jira instance? * Your JQL only shows one assignee. Is this…

Hi @Makai Baker -- Welcome to the Atlassian Community! First, a disclaimer: Although this is possible, the reliability depends on the alignment between your rule and the select-value fields contents. Basically the rule would parse the target field name and value from the source issue data, and then use created variables…

Hi @Ylan Muller To learn if a field is supported by automation rules, please use the how-to article linked below. Essentially you find an example issue (or idea for JPD), call the REST API with a browser, and search for the field. If it is not present, it is not supported by rules. This technique also helps to confirm the…

Thanks for that information. With your additional details I do not believe my suggestion will work for you...There is a limit of 100 issues/items for a branch to process, and so you would not be able to process all of the users found in the group with a rule.

Hi @Chaya Bhagavathi -- Welcome to the Atlassian Community! Are you typing in (or pasting in) HTML in the comment? Have you instead tried pasting in plain text? One way to do that is to paste your source into a plain-text editor first, re-copy the text, and then paste. Kind regards, Bill

Hi @Claas Babendererde Adding to what the others have suggested... When one of your fields could be empty, what do you want to happen? If there is a default value to use, that can be supplied with the pipe | operator. For example, let's assume you want your custom field to default to 1 when it is empty:…

Hi @Nagarjuna Busireddypally The branch type of Most Recently Created Issue refers to issues created during the rule execution. Instead consider referencing the parent issue's field directly, and if that does not work, you may need to first branch to the the parent and save the value in a created variable and then use it.…

Hi @Jarosław Solecki [Deviniti] When recommending a marketplace vendor product, please ensure that you disclose your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Community online guidelines for Marketplace and Solution Partners…

Hi @Qais Alkhatib Adding to Walter's answer... If you want to measure the issue cycle times (e.g., time from/to specific status values) you can use the built-in Control Chart instead. That chart does have some limitations, so please review this documentation/suggestions to learn how it can help:…

My apologies, as I forgot there is a defect/behavior of the order of dates with diff() when using now...as that cannot be first. Please try this: {{updated.diff(now).days}} I updated my earlier post to reflect this. 

Hi @Hugo Moraes Neto I noticed a few things in your use of Lookup Issues that might help... (1) The results of Lookup Issues is a list, and so use the size function to learn how many results there are for the JQL. I recommend this, as it includes a default value of 0 {{lookupIssues.size|0}} (2) As your lookup could be…

Please try removing the urlEncode wrapper and instead use this only for your smart value included: {{issue.customfield_10236.substringBefore(":").urlEncode}} If that does not work, I again suggest saving the URL in a created variable first, writing the result to the audit log, and then using the created variable as the Web…

Hi @Alae Riahi -- Welcome to the Atlassian Community! When I did this a while ago, there were two parts I used to make it successful: * Store your URL in a created variable, and use urlEncode on your text to ensure it is formatted…

Hi @Martin Please try using the accountId value, and not the displayName, to select a user in a single-select user field. Here is the syntax for that: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Single-user-picker-custom-field Kind regards, Bill

Hi @Andrii Mykhailytsia -- Welcome to the Atlassian Community! I see two problems in your expression: * Inside of a Lookup Issues iterator, you use an {{issue. prefix for the fields, but that is not needed as the fields are part of the lookup instead. Try removing those. * Your calls to the equals() function were missing…

Hi @Ronni_Lou -- Welcome to the Atlassian Community! The information shown on that documentation page is an example, with example values of users, project keys, etc. I would not expect it to work without changes. Please try updating it to match your site instance values. And also, it is possible that after the privacy…

Hi @Manju What problem are you trying to solve by doing this? Knowing that will help the community provide more focused suggestions. Until we learn that... There is no build-in branching on users...beyond the scope of their association to issues. One possible work-around would be to get the users with the REST API and…

Thanks @Tanguy Crusson as that seems to work for access.

Hi @Tanguy Crusson First thing, thank you for the excellent, step by step, instructions for the upgrade! This definitely raises the bar for helping in GA roll-out assistance from Atlassian. I have a question is about Step 3 (optional): remove product access from site administrators Using this step definitely removes all…

Hi @Miguel Rodriguez It appears the lookup issues action is being added to Jira Server/Data Center now, and you can follow the progress on this here: https://jira.atlassian.com/browse/JIRAAUTOSERVER-53 Kind regards, Bill

Hi @Candice Gerard and @John Funk It would seem that something like this would work... {{issue.fields.duedate.plusDays(-issue.fields.customfield_10037.intValue())}} However the math operations for smart values only support two syntaxes: inline or math expression. Perhaps try the inline syntax:…

Yes, the idea is to call the REST API method with JQL to gather the issues, and then parse the response. Here is a good article on calling the Jira REST API from an automation rule: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828 And here is the REST…

Awesome! I am glad to learn that helped, and also... Using automation rules often requires both experimentation and learning. To help with those I recommend building skills by: * look at the examples in the template library to learn how they solved problems * look at posts/examples in the community to see if others have…

Hi @Priyanka Gupta -- Welcome to the Atlassian Community! Please try using the CHANGED operator with your JQL: https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/#Advancedsearchingoperatorsreference-CHANGEDCHANGED For example, project = myProjectName AND NOT status CHANGED TO…

How about using that filter (or others) with a shared Jira dashboard? People could pull (rather than a pushed email) when they want information about their assigned items, or watched, or etc.

Yes, that is correct, as you only have the account id and not the other fields. (The default field for a Watcher is apparently accountId, and not the entire user object). When I pause and re-read your original question about Watchers, I do not think this is possible in the way you asked with a rule. I wonder: what problem…

I like the webhook technique for this one, although that may not help enough. My mistake on the two rules advice! Let's back up and try this: Back to the one-rule approach, what if you call the REST API with a JQL search, including an ORDER BY End Date DESC, and grab the first record's date in the web response? That should…

Let's try this one piece by piece... First, mentions in comments store only the account ID for a user. To find all of the users mentioned in the last comment, the expression below works. It would split a comment into lines, find mentions, and then extract the account id values. {{issue.comments.last.body.split("…

Thanks for that information. The problem is how you are performing the math operation. The way you are doing it is leading to a text string and not a number. There are two ways to perform math operations in rules: inline and using a math expression: {{issue.fields.timeoriginalestimate.multiply(0.2)}} or…