Bill Sheboy Expert

Hi @Nicolai Viținschii I recommend starting with an example issue and reviewing the history to learn when / how / who is adding the sprint. That may clarify the cause, such as comparing that to any automation rules running at the same time. Until that is checked, I wonder... * You describe a status "Discarded" * For Jira…

Hi @Anthony Amirfar First thing: this is a very old thread, and so I recommend creating a new question, and perhaps linking back to this one. That will ensure the maximum number of community members see it to offer suggestions. Until we see that new question... First, your rule should probably use an if / else condition…

That is curious; I would expect the vendor can tell you if the actions you are taking do / do not raise events that can be detected by Jira. Also, this is a community forum and not Atlassian Support. If you are on a paid Jira license, you can contact Atlassian Support here: https://support.atlassian.com/contact/#/

Thanks for clarifying that you are getting the same error message (i.e., an apparent duplicate field in the project scope) and not that you were also trying to set date fields based on an issue transition. Your new question will help to clarify that better if you include the audit log details showing the error message.…

Hi @Georgia Harty -- Welcome to the Atlassian Community! Updated is the date / time of the last issue change: https://support.atlassian.com/jira-software-cloud/docs/jql-fields/#Updated If your JQL statement is not working as expected, please post your entire JQL statement as that will help the community offer suggestions…

Hi @Hilco de Lathouder -- Welcome to the Atlassian Community! Is your Affected Services field a single-select, custom field? If so, the currently selected value's name is likely: {{issue.affectedServices.value.name}} and so the table get() would be this: {{emailMapping.get(issue.affectedServices.value.name)}} That assumes…

I recommend contacting XRay, either through their documentation or support team, on their marketplace page. They will be better able to answer this question.

Hi @Cheri Kure -- Welcome to the Atlassian Community! Would you please post images of the audit log details showing the rule execution and of the Create Variable action? Those may help explain what you are observing. Thanks! Kind regards, Bill

Thanks for that additional information, Johannes. With that many issues, you will not be able to easily get the counts. Jira triggers, branches, and lookup issues are limited in the number that can be returned / processed: https://support.atlassian.com/cloud-automation/docs/automation-service-limits/ Instead the rule could…

Hi @Wolff Sébastien -- Welcome to the Atlassian Community! There are several ways to do this: * if / else conditions * conditional logic * lookup table I recommend trying a Lookup Table for this: https://community.atlassian.com/t5/Automation-articles/Update-Create-lookup-table-action-improvements/ba-p/2427798 For example,…

Hi @Joshua Hong -- Welcome to the Atlassian Community! Without seeing your entire rule for context... In automation rules, you may type in a smart value for the target issue's key for the link. That is not obvious from the rule editor as it only lists the options you note in the dropdown list. Just type in the smart value,…

Hi @Dima Astahov You could do this with an automation rule or a marketplace addon / app which supports calculated fields. For an automation rule, one question is: when do you need the value available? The answer will determine which trigger to use for the rule. For example... * need it once per sprint: set it on a sprint…

Thanks for the research, @Rachel Wright A few other things observed things are: * Permissions and billing* With the different role / permissions model, admins need to take care to ensure who can add versus view content...otherwise there could be billing surprises * JPD uses its own definition of a "date" field, which is a…

Thanks for that information, Casey! When using the Issue Created trigger, I recommend always adding the Re-fetch Issue action immediately after the trigger. That trigger may fire so quickly that some data may not be available to the rule yet, causing the rule to not work as expected. Please add that action and re-test your…

Hi @William van Dalen In addition to Vishal's suggestions... What do you mean by "a new component of the current project": * set the value of the Component field for the issue, where the specific Component value already exists * add a new Component value to the project, and then assign it to the issue If you mean the…

Hi @Johannes Fuenger First thing, I recommend pausing to review some of the automation documentation. That will help you when creating a rule. To get you started on creating your rule, please refer to these documentation and example sources: *…

Hi @Alexandra Verzier -- Welcome to the Atlassian Community! During the latest automation list changes, Atlassian moved / changed the visibility of that feature... Please hover over the Labels column for a rule in the list and the Add Labels button will appear. Kind regards, Bill

Awesome; I am glad to learn that helped!

Hi @Admin Jira First thing, I am not using XRay and so my suggestions are based on my experience with automation rules, in general. Next, for a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the…

Hi @Benjamin aka B.M -- Welcome to the Atlassian Community! Would you please explain what problem you are trying to solve with the rule? Knowing that may help the community in offering suggestions. Thanks! Until we know that... Once inside a branch on issues, {{issue}} refers to the branched-to issue as it loops. There…

Hi @Josh Allen Once the rule is inside of that branch to the template issue, TAP-58, the edit acts on that issue. There is no nesting of branches which would allow then branching to the most recently created issue. Two possible workarounds are: * From this rule, use the REST API to update the issue (which you note not…

Hi @Jesus Octavio Gutierrez Villegas Did you post your question / response in the correct place as what you describe seems unrelated to this thread? Please consider creating a new question to ensure the maximum number of community members see it and offer suggestions. Thanks! Kind regards, Bill

This is quite curious... Have you confirmed that the field "Days Until Next Follow up" is in fact customfield_10402? Have you tried using the user input directly to see if you get the same result? Perhaps try writing this to the audit log: now plus user input: {{now.plusBusinessDays(userInputs.followupdays.asNumber)}}

Hi @tiago_santos The default value is for the parameter to the get() function, not for the result of the lookup. If you need to check for missing values, perhaps either: * create a table row with a "magic number" (e.g., such as 99999) for the key, and use that value as the default * save the result of the lookup with get()…

Yes, that seems correct. Some of the "date" fields are text, or appear as text, inside of rules and must be converted first. I believe this applies to the Advanced Roadmap fields, in general.

Hi @Dave Furlani As there are known problems where the changelog is not accurate for list fields in rules, such as for Sprint and Fix Versions, that how-to article may not produce reliable or accurate results. Here is the defect if you want to watch it for updates: https://jira.atlassian.com/browse/JRACLOUD-80486 Kind…

I'd suggest this type of workaround is more than a little bit hacky, although likely to continue working after future automation improvements ;^) There is an open suggestion to add an option for parallel versus sequential execution of rules (such as for branches). You may vote for / watch it to see any…

Please try writing that custom field to the audit log to confirm it contains what you expected when the rule runs: Field contains: {{issue.customfield_10402}} And what type of field is the custom field "Follow Up Date": a date picker or something else?

Hi @Louise Baker Would you please post an image of your complete rule and the audit log details? Those may provide context to help. Also, what is the trigger issue for your rule: a JPD idea or something else? (That is, what is the event that triggers the rule and where is it located?) Thanks! Kind regards, Bill

What is the type of your field, customfield_10402? If it is text, please add asNumber to convert it inside of the function call: {{now.plusBusinessDays(issue.customfield_10402.asNumber)}} If it is something else, please post an image of the audit log details showing the rule execution. That my provide more context for what…