Bill Sheboy Expert

I do not believe it exists by default, and I just did a quick test with my free-license site to confirm that. You may do the same by: * identify your user's account ID * enter this URL in a browser tab to load the entity properties* yourJiraURL/rest/api/3/user/properties?accountId=yourAccountId * search on the page for…

Hi @Łukasz Parafiniuk -- Welcome to the Atlassian Community! Adding to the suggestions from @Dick ... Please also post an image of the audit log details showing the rule execution. And, I recommend changing the name of the variable in the Manual trigger from "parent" to "varParent" (and also in the Clone Issue action).…

Thanks for that information, @Jeffrey_Denton Your new rule is missing the branch to the Idea found and the second Lookup Issues action to gather the issues linked to the Idea. Please add those and re-test. Thanks!

Thanks for that additional information! Let's try to clarify some things to learn how-configurable of a solution is needed... #1) Is there a date formula which can be used to determine the Delivery Start Date and Delivery End Date? Assumed Answer: no, and that is why the lookup tables are used. #2) From what you show, I…

That appears to be checklists provided by a marketplace app: #3 in my list above. Please check the documentation for the app to learn how to automate changes to the checklist's custom fields. You may find it by selecting that item in your Apps list and the marketplace (or vendor) page link should be shown.

Yes, and...I hypothesize the design idea was "if you are moving an issue on the board, that issue should retain focus based on where it lands by rank within the issues in the column, except when..." There have been many suggestions / defects logged around this behavior, and many are closed with "won't do". Here is a…

Hi @Danijel Šili -- Welcome to the Atlassian Community! Please see this documentation to disable the "smart reply" comments for the entire site: https://support.atlassian.com/jira-software-cloud/docs/use-smart-replies-in-issue-comments/ Your Jira Site Admin will need to do this. Kind regards, Bill

Hi @Tushar Short answer: To enforce the issue creation order the rule must clone them one-by-one (not using a branch) or use a marketplace app (which will essentially do the same thing to enforce the ordering). More information... I hypothesize your rule is branching over the issues to clone. Automation branches which…

Hi @Menia Laina -- Welcome to the Atlassian Community! The problem is the use of single-quotation marks, as the match() function expression takes double-quotation marks. What is the type of your field: numeric or text? If the field is numeric, please change the expression to this: { "fields": { "Overall effort":…

Hi @Trudy P Claspill Yes, and...to the suggestions from @Matthias Gaiser _K15t_ After the old CodeBarrel backlog was hidden from the public, some of the issues were recreated in the AUT backlog (i.e., apparently not cloned, and so losing valuable info!). Here are a couple asking for the ability to return data from Incoming…

Hi @Jeffrey_Denton That rule description / information looks like stuff from a bot / AI-chat. If it is, please review the community guidelines to identify sources when posting such content: https://community.atlassian.com/t5/custom/page/page-id/rules-of-engagement Back to your questions... As written, that rule will…

Hi @Travis Hill When you note a "checklist", are you using: * the built-in, checklist custom fields, * the new "action items" feature for the Description field, or * a marketplace addon for checklists? The first one can be set / cleared easily with an automation rule, as can the third one for many marketplace addons (just…

Hi @chrisyeem What do you mean by "next" regarding the versions? Where do you want to "get" that version: in the UX, with a query, etc.? By default on the Releases page, the "next" version is the one at the bottom of the list, regardless of the release date, name, etc. And so the "one after next" would be the one…

Hi, @Monique vdB -- Thanks for the follow-up info!

Hi @Nick Haller Thanks for your answer, as this question is getting asked more and more :^) Please consider changing your link for Scope to the one in the documentation to explain the differences: https://support.atlassian.com/cloud-automation/docs/create-and-edit-jira-automation-rules/#Edit-the-details-of-a-rule Kind…

Hi @Rees, Ian Pondering a bit further, this is the third question for this type of search (with a table) I have seen this week...and I did develop a much more elaborate way to solve it with dynamic list searching about two years ago. I even wrote an article on it in October…

Hi @Joseph HANI The keys for a Lookup Table are static text and although they could represent a regular expression, they would not behave that way in the lookup's get() function. Instead, I recommend parsing out the unique part of your "Program Baseline Sprint" field to match distinct keys in the table, and use that for…

Hi @Georgina Everett -- Welcome to the Atlassian Community! First thing, what problem are you trying to solve by doing this? That is, "why do this?" Knowing that may help the community to offer better suggestions as replicating the field text could cause problems / confusion (particularly if the rules do not run when…

Hi @Uma Manoj -- Welcome to the Atlassian Community! Yes, that is possible. Please review this information about connecting your source control / pipeline tools to Jira and then using automation rules with the development triggers to transition the issues:…

Yes, and...this question has already been asked as a following up to this one: https://community.atlassian.com/t5/Jira-questions/Re-Re-Updating-a-field-when-a-specific-component-is-used/qaq-p/2917317/comment-id/1081389#M1081389

Yes, my understanding is the Advanced Branch always executes in parallel as it could be zero-to-many items. Recently, I noticed branch parsing getting "smarter" as a JQL branch was previously always run in parallel, and now a JQL branch over one issue is run inline. For example, key = TEST-123. That may be a handy trick…

Hi @Oksana Kolesnyk -- Welcome to the Atlassian Community! Yes, "Total Effort" was a custom field added by the person who originally asked the question. Kind regards, Bill

Hi @Gilad Waldman Is the rule still branching over the distinct versions, and so each one is only attempting the REST API call one time (avoiding any racetrack conditions)? If so, you may want to ping the Atlassian Support team so they can check the internal logging for anything they…

Hi @Neil Fletcher Rules can get "glitched" by too many edit / publish cycles, or incompatible settings that are not resolved by the editor. Apparently something gets broken in the JSON behind the scenes, although I have not found any public backlog defects listing the symptom. Typically the two ways to check for that are:…

If that is what you want to do, there is no automation action to "delete worklog entry". Instead the rule could call the REST API endpoint with the Send Web Request action to do so.

Why are you using a Lookup Table? That will not work for this scenario because the "Plugin ID" field may contain multiple values. And why is your rule using a Scheduled Trigger? An example rule using the smart values condition would be: * trigger: issue field changed for "Plugin ID" * if / else block* smart values…

As I already described, you could use the Issue Fields Condition or Smart Values Condition to check if the Description field contains the text. You appear to be adding quite a lot of text, so perhaps just check for part of it, such as: What are the transactions/authorization object that is needed?

Hi @Trudy P Claspill and @Jorge Bruna -- Welcome to the Atlassian Community As Jorge mentions updating the "Give thus section a name" information, I wanted to note that is not supported by the REST API yet. Here are the relevant suggestions to add the capability: https://jira.atlassian.com/browse/JRACLOUD-87088…

Hi @Rees, Ian Short answer: This scenario requires using an inline, iterator over the multiple-select, option field and a series of chained replace() functions to convert to the code / abbreviation string value. For example: {{issue.myMultipleSelectField.value.join(", ").replace("LongtextA", "CodeN").replace("LongtextB",…

Hi @Tomislav Tobijas FYI the original intent of the question seems to be to retain the focus on the top of the page when transitioning an issue, not to re-rank issues in order to do so. Re-ranking could have unintended consequences for the team and their product owner / champion. Kind regards, Bill