Bill Sheboy Expert

Hi @Biancha I have not used that addon before...Have you checked the documentation for that marketplace addon to see how it is supported by automation rules? And I wonder if the template needs to be applied first...so... * perhaps create a template which has your required fields set to a default value * in the rule, apply…

That is curious...Is this a company-managed or a team-managed project? Let's try this to see if the rule is "glitched", which seems to happen after too many rule publishes/edits: recreate your rule from scratch as a new rule, and then retest.

Thanks for that information and screen images. Is this rule defined in project "A20", in another project, or in a global scope?

Thanks for clarifying that you are using Jira Server. It is possible this is a search indexing issue with the database, so please work with your site admin to re-index the database to see how that helps: https://confluence.atlassian.com/adminjiraserver/re-indexing-after-major-configuration-changes-938847716.html

Is your field defined on the edit view? When it is not present a field cannot be edited by a rule. Who is the rule actor (i.e. user) in the details section of the rule? Has this been changed from the default of "Automation for Jira"?

Hi @Adam Hasselgren You can do that with the selection field's id or name, such as {{issue.customfield_10163.id}} or {{issue.customfield_10163.name}} as described here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/ If that does not help, please post images of your complete rule and the audit…

Hi @Jon Nason -- Welcome to the Atlassian Community! Please try removing the quotes around the field in your function call: {{issue.issuelinks.first.inwardIssue.description.substringBetween(issue.customfield_15201,";")}} Kind regards, Bill

Hi @Edward Dighe Perhaps you could explain further: why is your team using a backlog? If your team is using a Kanban board, and you want new issues on the board, wouldn't the backlog always be empty? Kind regards, Bill

HI @suresh.m.mani -- Welcome to the Atlassian Community! Advanced queries like this cannot be done with the built-in features of Jira Cloud. How you may solve this depends upon how frequently you need this type of query and if you want to spent money to add features to Jira. For example... * Need this just one time: export…

Hi @Russell Brown What is not working as you expect? Please note when using {{lookupIssues}} with an iterator, you refer to the fields without an issue prefix, such as with: {{#lookupIssues}} {{key}} - {{summary}} {{/}} When you use {{issue.somefield}} inside of the iterator, it is instead referring to an issue outside of…

Hi @Vitor Prado and @Mark Segall If I understand your scenario, you are trying to reference both the trigger issue and branch issue's data within a branch. That is possible and the smart values referenced is important. For example: * trigger: some trigger...at this point, both {{issue}} and {{triggerIssue}} refer to the…

No, as the specific features are a bit different for Jira Cloud and Server/Data Center automation. And...Server/Data Center has a "lite" (free) and "pro" (paid) version. Please look here for information on the Server/Data Center versions:…

Well done! For rules like this, it can help to initially write the automatically generated content to the audit log. Then you can confirm the results match what you expect before using the webrequest.

Based on what you show, the custom fieldname or ID will work as a supported smart value. Please try using this example to set a number field with your JSON expression: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Number-custom-field

Yes, I understood that was what you are trying to do. Please try using replaceAll() with a regular expression. You may need to experiment a bit as some of the characters in your complex string are reserved, like quotation mark, and will need to be escaped such as with \"

Hi @Dennis_H Without seeing your rule...and depending upon its structure/design... If you are doing the clone outside of a branch, the rule will run one action at a time. And so you could add a re-fetch after the clone to slow the rule, and then use a condition to look for the new issue. Then only delete the source issue…

Hi @Jeff OBrien That is probably possible, as you have described. The rule would be triggered on the field change in your software project's rules, tested with your conditions (i.e. epic and the field changed to "yes"), and when the issue is created in the other project the epic link could be set to the triggering issue.…

Hi @Samuel Francis What else is in your description, or is this the only text and you want it to only return the state name? If there is more text...there are quite a few non-alphanumeric characters in your string, and so you will need to use a regular expression (regex) to remove them and keep only the state name (and any…

Hi @Caroline Björn Would you please post images of your complete rule and the audit log showing the details of the rule execution? Those may provide context for what is happening. And...would you please provide examples of a series of version names you want. For example: * my Version 585.3 * my Version 585.4 * ... * my…

Hi @Tripti Damodharan -- Welcome to the Atlassian Community! If this is a specific, consistent sprint every time you could set the value by creating a variable with the value and then setting the sprint to the smart value. If this value changes over time and you have a way to identify it (e.g. search criteria) you could…

Thanks, @keerthi for that information. I knew about that limit and wanted to check if it matched at least what you expected. As I noted with the link about service limits, a branch can handle more than 100 issues but you could be running into a processing time limit. At this point I suggest you have two options: * Keep…

Hi @Jules Cuijpers -- Welcome to the Atlassian Community! I note in the image you posted that there is an extra space after the sum function in the JSON. Have you tried removing that? Kind regards, Bill

Hi @jun lee Have you confirmed the smart value for your field to use in the JSON advanced edit? Please note that the smart value may not exactly match the name of the field on the screen or what is shown in drop-down lists. You can find and confirm the smart values for supported fields using this how-to…

Hi @Joel Batac Please consider starting with this reference which provides an overview of automation rules, example rules, and details of the features. https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/ Kind regards, Bill

Hi @Jeffrey Bistrong As you are trying to set the fix versions to one (or more values), you will want to make the edit handle all cases, as shown here: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Fix-Versions Your two options are to do that by splitting the values to add them one…

Can you confirm you are in fact using Jira Cloud, and not Jira Server or Data Center? Can you show a screen image of your list of projects, focusing on any with names similar to the one in you query? Can you show a screen image of the two issues you believe to be in the project and which are not returned by that simple…

Hi! I recommend moving the Re-fetch up to immediately after the trigger. Otherwise there is a chance that JQL condition could fail to match when the data is not ready yet.

Hi @Oksana Baier There are several ways to do that...and one way is to: * Create a rule, triggered on some condition, which updates an story to recalculate the sum * trigger that condition For example, you could detect the parent change for the subtask and then update the parent. The trigger for this approach would be…

Please try to add multiple labels manually first. That will confirm you have the correct syntax, and then we can adjust to add the components dynamically. Again, I have not tried this, and...I was noting the differences in the inadequate documentation page versus what you were trying. I haven't found a reference yet that…

Awesome, and well done! I was about to try that with a homemade encoding like you show for varReleases, yet I haven't gotten a created variable to work in a regular expression match() function call before; often this was because my searches has dynamic and static content, which required quotation marks. I'll definitely try…