Bill Sheboy Expert

Hi @Amit Bisht Using text functions, conditional logic, math expressions, and date / time functions, you could parse the just-completed sprint name, {{sprint.name}}, store the pieces using the Create Variable action, and then reassemble them to create the new sprint. As each customer's sprint naming convention is…

Hi @Shalini Pradhan Once again...please consider including the ability for customers to disable such features at a site level, even for experiments, as soon as they are introduced. Such changes are often disruptive, taking up valuable screen space, causing confusion from just-in-time changes to the UX that impact…

Please take a look at the template rule first as that may do everything you need. Thanks!

Awesome; I am glad to learn it is working!

Hi @Katie Kusjanovic -- Welcome to the Atlassian Community! First, have you tried writing {{webResponse.body}} to the log to confirm the structure matches what you are expecting with the other attributes you are logging? Next, in the Send Web Request action, did you select the option to wait until the response happens?…

Awesome; I am glad to learn that helped! Regarding the changing date values, that may depend upon how / when the date changes... When it is an expected value, you could use the date / time functions to build a value to match the date(s): https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/…

Hi @Emmanuel Favreau -- Welcome to the Atlassian Community! Yes, that is possible using an automation rule which uses JQL to find the linked work items (formerly called "issues") and the Lookup Issues action to sum the values. Please see these references to help implement that approach: *…

Hi @Lisa McCann Correct, and I noted that in my initial post: https://community.atlassian.com/forums/Jira-questions/Re-Updating-Reporter-field-when-cloning-with-automation/qaq-p/2844756/comment-id/1060951#M1060951 Kind regards, Bill

Hi @Myles Boyd That error you see is because the trigger object is an Alert, not a work item / issue from which to branch to linked items. I am not using Alerts, but I did find this open suggestion indicating automation rules do not have that linkage information: https://jira.atlassian.com/browse/AUTO-1623 You could…

Thanks for that information, and let's adjust / confirm some things... When using the Issue Created trigger, that can start so quickly that some issue data may not yet be available. The "fix" for that is to always add the Re-fetch Issue action immediately after that trigger. It will slow the rule a bit and reload the data…

Thanks for that information, and... I am assuming the source fields for the calculation are number fields. Please let me know if that is not correct. Based on what you described, the first set of conditions in the if / else block is incorrect as it is using OR operators (i.e., At least one condition matches) when they…

Thanks for clarifying the need. Please try the approach I suggested and let me know what happens.

Thanks for that information, and... When using the Edit Work Item action, the field may be selected from the dropdown list or updated using a JSON expression, but not both in the same action. For your scenario, please remove the selection from the dropdown list. Next, you want to add a value not replace them, correct? If…

Hi @Chaya Jacobs -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete automation rule in a single image for continuity * images of any…

Hi @Pierre Violleau -- Welcome to the Atlassian Community! When you only want to create the new Epic when that specific component value was added, the fieldchange / change log smart values may be used to test that. For example: * smart values condition:* first value: {{addedfieldChange.values}} * condition: contains *…

Hi @Veronika Kosová -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete automation rule in a single image for continuity * images of…

Hi @Marina Pérez Ruiz When you review the workflow for the issue type of PRETS2AC-990 does it have a transition path from its current status to "In Progress"? And if it does, are there any conditions on that transition that could fail? Kind regards, Bill

Hi @Viktoriia Bashyrova -- Welcome to the Atlassian Community! This symptom is from an open defect that was fixed, broken again, etc. Please watch / vote for it here to see progress: https://jira.atlassian.com/browse/JRACLOUD-93805 Kind regards, Bill

Hi @Gökhan Arslantaş -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete automation rule in a single image for continuity * images of…

Hi @shaily.mehta -- Welcome to the Atlassian Community! Short answer: as written, the rule you describe cannot work as you intend. There is a template rule you could try instead. From the rule list, select Templates and under the Notify section, select this rule and update the timeframe in the branch to meet your needs:…

Hi @Tomalin Jenner -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit log…

Hi @nida ergenç For a question like this, context is important for the community to help. Please post the following: * what version of Jira are you using: Cloud, Server, or Data Center * what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete automation rule in a single image for…

Hi @eric caprio First, the Edit Work Item action can usually update a field in one of two ways: from the dropdown list selection of "Choose fields to set..." or from a JSON expression, but it cannot do both for the same edit action. Please remove the JSON expression and just keep the one from the dropdown. Next, I suspect…

For some context, please post the following: * what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit log details showing the rule execution * explain…

Please post the following to provide a bit more context for what you are observing: * what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit log…

Hi @Ian MacDonald Are you trying to exactly match on the phrase "Document Header Info"? Your CQL expression uses the CONTAINS ~ operator to search for that text, and I hypothesize those three words are on each page you are checking. I recommend pausing to verify that. And, the documentation for the CQL CONTAINS operator…

Hi @Rick Dorgan First thing: this is a very old thread, and I recommend creating a new question, perhaps including a link back to this one. That will ensure the maximum number of people see it to offer suggestions. Thanks! As for your specific question, this is about issue-scope in the rule as that determines what a rule…

First, it appears you are doing this with the scheduled trigger to perform some type of bulk-updating for the attachments. If that is not needed, I recommend staying the Issue Linked trigger. Otherwise... Your rule is trying to issues based on specific link types to copy the attachments from the issue they are linked to.…

Hi @Sanjay Dangi Unfortunately, the smart value and concept of "destination issue" only exists when the trigger is Issue Linked or Issue Link Deleted. That is why the copy does not work with other trigger types. For your scenario with the Scheduled Trigger using JQL, you could instead invert the JQL so the "trigger issue"…

Once you get the first call working with Send Web Request, the remainder is list processing (like with lookup issues). If you want to give it a try and run into challenges, post images of your rule and audit log details so the community can help.