Bill Sheboy Expert

Hi @Ioana Sundius -- Welcome to the Atlassian Community! Are you using a marketplace addon/app for Checklists? If so, I recommend contacting their vendor from the marketplace site to ask this question. Kind regards, Bill

Hi @Dillon Kenniston This is complex use case, tailored your your team's usage of Jira, although it may not have seemed that way when it was implemented by manually changing the issues. I recommend having a discussion with your Jira Admin on how to implement this with rules, and how to handle any exception/edge cases…

Hi @Genevieve_Green Have you tried to chain the entire expression, including the division by 3, such as with this: {{issue.customfield_10679.asNumber.plus(issue.customfield_10680.asNumber).plus(issue.customfield_10681.asNumber).divide(3).round}} And...do you expect any of the values to be empty (i.e. null)? If so,…

Yes, and... Here is the related defect for automation, which covers both Jira Cloud and Server/Data Center versions of the symptom: https://jira.atlassian.com/browse/JIRAAUTOSERVER-207 Please note, you may observe changelog intermittently working for fixVersion. I found through testing there are very specific paths by…

Hi @Martyna Marcinkowska -- Welcome to the Atlassian Community! It appears possible to update a custom field's options by calling the following experimental REST API function using a web request from the…

Hi @Oksana Baier The symptom you describe seems to indicate a timing problem, where * multiple things are changing for the issue, * the first thing changing is not the parent, and so * the change log contains the "current value"... * until the rule triggers again. Two things to check if this is the cause are posting the…

Hi @chucklepie You may be encountering the defect noted below. It seems both related to the use of swim lanes (which seem to be in use on your image) and where one clicks (top or bottom area) on the issue before trying the drag and drop operation. https://jira.atlassian.com/browse/JSWSERVER-8801 Kind regards, Bill

Hi @Adam Dulberg and @Darryl Lee Darryl, when using asJsonObjectArray in this way you first specify the key you want from the structure (e.g. "value" for a checkbox field) and after that, use a replace() function to substitute for the desired field name. I recommend writing the function call to the log to learn why it is…

Correct, and...the REST API call will be limited and require paging to see the details. However if you only need counts one call should provide the counts in the "total" field of the response.

Here is a how-to article for calling the REST API from a rule: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

Hi @Ste404 Yes, and to Mikael's answer... Depending upon what information you need, a couple of work-arounds would be to: * use narrower criteria for the lookup to report in sections * if you only need counts...using a web request in the rule call the REST API with JQL for a search and note the maximum count in the…

Hi, and sorry for the delay in responding. For the lookup inside of the branch, you will use your earlier JQL and add this: original JQL AND assignee = {{varBranch}} Now you can test the {{lookupIssues.size|0}} on that result to determine if the specific user for {{varBranch}} has more than 10 issues assigned.

Hi @Felipe Felix Braga and @Trudy P Claspill If we assume the sprint an issue was completed in is the most recent one associated, it is possible to use a complicated rule (on a scheduled trigger) to search for the maximum sprint end date, and set the custom field for that value's sprint name. You could run the rule until…

Hi @Vikas Gupta -- Welcome to the Atlassian Community! To set the sprint number directly, you could either: * use advanced edit with JSON to directly set the value: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/ * or create a variable, set to your value, and then use that smart value…

Hi @Keith Vedol That is working as expected...What is happening is the distinct function is applying to the set-of-selections for your custom field, and with 3 choices there could be 2^3 or 8 possible results. The work-around is to merge the sets before using distinct. Please try this one:…

Hi @Umar Maroof Subtasks are not normally used with a parent Epic, but instead their parents are stories, tasks, or bugs. If you actually are associating subtasks with an epic directly, I suspect the branch for epic (parent) will not work in the rule. Instead you could try either... * using what was intended in Jira and…

Did you confirm the labels are available? And if you are trying to set multiple versions based upon data, such as from the fields, you would need extract the labels, expand the list, and then format them for advanced edit with JSON, as described…

Smart values for fields are name, spacing, and case sensitive, so a small typo could lead to null results, and no error. Let's try this: find an example issue with your field and then use this how-to article to confirm the exact name of your smart value. And...if you do not see the field, that tells you it is not supported…

Based on the documentation, those labels may not be available: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/#--Pull-request-- However...everything possible is not listed in the documentation. So I recommend making a test rule which is triggered to access a PR, and then write the…

Hi @shelleyc -- Welcome to the Atlassian Community! In your lookup issues JQL that is inside of the branch, you may refer to parent = {{issue.key}} rather than the literal value. Inside of a branch, {{issue}} refers to the branched-to issue(s). What is the purpose of your webrequest in the rule? If you just need the sum…

Hi @Sean Sullivan -- Welcome to the Atlassian Community! The issue created event only fires after the event has happened, and so the rule only happens after that. I do not believe issues have a "draft" condition, and so adding such a trigger would be predicated on other substantial changes for issues. When you need the…

Hi @Austin Churchill There is an old suggestion to support this in rules but I could not find a more recent one in the public Jira backlog: https://codebarrel.atlassian.net/browse/AUT-62 I believe the business days calculations are always integers and for Monday-Friday, 9 am to 6 pm. These behaviors are often limitations…

Hi @Salim Ubeydullah -- Welcome to the Atlassian Community! The short answer to your first question is: probably not. Smart value lists do not have the ability to be sorted, and so you cannot find the "one before the next one". For your second question, the answer is "yes". A version can be set from the drop-down list or…

Yes, and...it is possible to nest iterators but apparently not for the same list (.i.e. same lookup issues result set). A child list (e.g. Sprint, multi-select field, etc.) can be walked inside. Darryl, for your extended use-case, I would instead suggest pre-filtering to a created variable to create a delimited list of…

Hi @Florian Royer When I wrote that post, I did not recall what happens accessing the sprint information of future sprints. I recommend trying a manually triggered rule to test, writing this to the audit log: {{issue.sprint.endDate.max}} One big challenge with this approach: what do you do when an a future sprint is edited…

There are several ways to do this. First find an example issue which uses that field, and then: * Try an advanced search and issue export, including all fields. Look in the results to find the id. If that does not work... * Use this how to article to learn both the id and the correct structure in JSON to set the…

Hi @Darryl Lee I wonder if this is either a field type/value or a smart value typo thing...I tried this with another single select, custom field's value and it worked for me in Jira Cloud... total count: {{#=}}0{{#lookupIssues}}{{#if(Current environment.value.startsWith("T"))}} + 1{{/}}{{/}}{{/}} and total story points:…

Hi @Adam Evans It is likely this a timing issue rather than the alphabetic ordering of the fields. You could try a work-around by adding a Re-fetch action to your rule, immediately after the trigger and before the condition tests. That action will slow the rule down by about one second and re-load the data before…

Hi @Ksenia Abdulina Do you mean a multi-user selection like this: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Multi-user-picker-custom-field Or something else? Kind regards, Bill

Hi @Brian Estrada -- Welcome to the Atlassian Community! The basic steps ares similar to what I noted above, where custom fields are added for each status/thing you want to track and then use automation rules triggered on issue transitions to set them. Then add a separate rule to compute the differences for the time…