Bill Sheboy Expert

Hi @Trudy P Claspill I updated the post you linked to; it did not properly handle the case of multiple mentions in the same sentence/line of text, so I fixed it. Kind regards, Bill

Hi @Gregory James From the board's ... menu, select Board Settings > General and you will find the option to edit the filter. Kind regards, Bill

Thanks for those additional details. I am still unclear on the purpose of the rule from your question, as it seems to just set a custom field in all issues included in the sprint...which would be spanning multiple projects, in your case. You do not indicate if you are using parallel sprints, and so I wonder if there are…

Hi @Benny -- Welcome to the Atlassian Community! You appear to have a board which is including every project in your instance, and you are creating a sprint for that. Is that correct? If so, the sprint-related triggers cannot work for the All Projects setting of global-scope automation rules. There are several suggestions…

Hi @Robin Kapoor -- Welcome to the Atlassian Community! The versions are independent of the issues (even though they relate through fields). To do what you asked, I recommend using the Lookup Issues action to find the issues associated to the released version, and then you can list them in the message. For an example of…

Well done, and that is interesting! I have found the rule parsing inconsistent in accepting a trailing comma for updates. Please note I added the conditional processing with {{^last}}, {{/}} handling as I know extra commas inside the list items fail.

Hi @Randy O'Neal You are correct that the Manual trigger's context is the issue from which the rule is run. That is all the rule "knows" about. There is no mechanism to select "input conditions" for a rule, or to multiple-select issues and then "run rule on these issues". Yes, and...when you need more context for the rule…

Hi! My understanding was you were trying to set the Due Date for specific time frames, and so...there should not be a need for an advanced branch in the rule. * If you want the rule to trigger on that date/timeframe, set the scheduled rule schedule using the selections or a CRON expression, and then create the issue and…

 Hi, Fabian. You are close with that starting point...you will need the JSON for a multi-select user field and the account id values from the response using with an iterator. { "fields": { "Approvers": [ {{#webResponse.body.actors}} { "id":"{{actorUser.accountId}}" }{{^last}}, {{/}}{{/}} ], } } If that does not work,…

Hi @ibrahim.aly -- Welcome to the Atlassian Community! You seem to be asking a different question as this one relates to versions (releases) and you apparently want an increment for creating projects and determining their id value. I recommend creating a new question, and linking to this one for reference. Otherwise only…

Hi @Fabian Dengel One way to do this would be to call the REST API from a rule to gather the accountId values of people in the role, and then assign them as approvers with a JSON edit. If you want to try that, here are some references to help: * how to call the REST API from a…

Hi @Justin Princehorn Let's start with what the documentation says about the Days in Column setting: https://support.atlassian.com/jira-software-cloud/docs/customize-cards/#Using-Days-in-column Note that if you move an issue back to a column where it's previously been, the indicator gives you the cumulative number of days…

Agreed, and...there are several things not available in the public REST API functions, and thus not available to automation rules. I could not find any open suggestions for this so I recommend adding one. Perhaps one of the automation product managers will associate it to any open work items so we can see progress. Just as…

Hi @Ken Young For the release related work feature, I found this post in the dev community which indicates there is an experimental REST API to access the links and that the Atlassian team is working on a public API (last update info from Atlassian was August 2022):…

Hi @Mary Kasinger -- Welcome to the Atlassian Community! There are built-in date-time functions that could help do that: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ For example using plusYears() and dayOfYear() you could adjust {{now}} to the first of the next year with:…

Hi @Brock Jolet Smart values are name, spacing, and case-sensitive...so I recommend confirming the name when there are doubts using this how-to article. Basically you identify an example issue which has your fields and then call the REST API with a browser tab to find the smart value.…

Hi @Kara Taylor -- Welcome to the Atlassian Community! This gap in basic, process analysis functionality has long been missing from Jira...especially for teams using Kanban or non-trivial workflows. How to close this gap depends on your frequency of need and ability/desire to spend money to enhance Jira... * If you feel…

Hi @Jeffrey Bistrong TL;DR: the variable goes out of scope because of how branches work, and so is null. Apologies in advance...I tried to write a shorter answer for this and was unable to do so. :^) Branches which can only be on one-and-only one issue (e.g. on Parent, on Current Issue, etc.) are actually run in-line. And…

Hi @Chad Vernon and @Karen Corbeill It appears you want to add additional components, rather than replace or copy them. To do that, you would use the advanced edit with JSON options. Unfortunately I do not believe you can add just one component value with JSON, like with Labels. Instead you must capture all the existing…

Hi @Trudy P Claspill I believe Target Start, and some other advanced roadmap fields, cannot be selected from the Edit Issue dropdown list yet. Instead only JSON edit works for them. Here is the suggestion to fix that: https://jira.atlassian.com/browse/JIRAAUTOSERVER-159 Kind regards, Bill

Hi @Jesus Octavio Gutierrez Villegas For the scenario you have described of using the country flag emoji in a table created by an automation rule in the description field, I do not believe that is possible for a least a couple of reasons: * The country emoji which can be selected manually while editing the description do…

Hi @[deleted] Last week I got a notification that said the rollout was 22 March 2023, and referred people back to this article for details: https://community.atlassian.com/t5/Jira-Software-articles/Upcoming-changes-to-epic-fields-in-company-managed-projects/ba-p/1997562 Kind regards, Bill

Hi @Grace Shaw -- Welcome to the Atlassian Community! My understanding is the function portfolioChildIssueOf() is only available with Advanced Roadmaps, provided with a Premium Jira license. And the person who originally asked this question is not on that license level. Kind regards, Bill

Hi @Jenn Sherman Before dealing with the error... Your lookup issues seems to span lots of issues. Would it help to narrow that list's JQL down a bit so it doesn't get more and more issues, each time the rule runs? Next, how many recurring stories/subtasks are you trying to create? If this is a smaller set consider…

That makes sense due to the embedded bracketing. I suspect the reason the chained value does not work is typing related. Perhaps consider sending that one to the support team and ask them why it does not work for the Server/Data Center version of automation rules.

Hi @Devon Holt -- Welcome to the Atlassian Community! You are correct: there is no built-in way to search for the last commented date. If you have one of the marketplace addons for JQL, those may help. With out-of-the-box features, this JQL would get you close to the answer: project = myProjectName AND comment ~ accountId…

Hi @Daniel G_ Sinclair To do that with a wildcard match to the text, you could... * grab all the current labels with that text using a regular expression and the match() function. * And using those results, either...* using advanced branch, iterate over them to remove one-by-one with edit issue, or * build a JSON…

Hi @Aurélie Pilette With the curly-bracket syntax, you do not need to use them again once inside of a set. Please try this: {{issue.summary.replace("- -", issue.yourCustomFieldName)}} Kind regards, Bill

Hi @Kit Friend Here is the fix below. This rule which I believed worked in the past stopped working when there were multiple mentions on the same text line. The improvement below first splits the comment by spaces into separate lines, and then tests each entry to find the accountId. {{issue.comments.last.body.split("…

Thanks for that information. Perhaps trying using chained functions instead: {{now.plusDays(webhookResponse.body.table.body.rows.valueColumns.value.get(0).asNumber.round)}}