Bill Sheboy Expert

Thanks for that information, @Kelsi Flores When you describe those things / steps, what is the event which starts things? Rules have triggers, and so knowing where to start is important. For example, if we assumed... * steps 1-3 were manually done, * and the rule was triggered on linking the Delivery Ticket to an Idea, *…

Hi @Pedro Olmo I respectfully and strongly suggest not Creating Variable names with ones matching existing fields / smart values. That is likely to confuse people reading the rule and the rule logic. For example, when there is an issue in scope, the rule could confuse {{issue.project}} and {{project}} (the variable)…

I am glad to learn you have the other scenarios covered. FYI -- As this question is asked often, I created a short article on the approaches I described earlier, including some additional edge cases to consider: https://community.atlassian.com/forums/Automation-articles/Automation-concepts-Percentage-Complete/ba-p/3094445

Hi @Dave Van Hecke -- Welcome to the Atlassian Community! Yes, and...to the suggestions from @Shawn Doyle - ReleaseTEAM First thing, I recommend looking at some of the free training Atlassian provides on using JQL to search for issues. Next, you have different criteria for your Epics than for the other work item types. In…

Hi @Christopher Johnston That is possible using the date / time functions, chaining them together for the various parts you describe. For example, start with the {{issue.duedate}} and set / increment the pieces needed by adding the functions to the end.…

Hi @Eric Younkin There are many problems the built-in rule validation cannot detect, and in this case it is not detecting the incorrect JSON, which seems to imply a mapping function for the values...which does not exist. In some cases, one would use a conditional expression to build the dynamic…

Hi @Malcolm Rogers -- Welcome to the Atlassian Community! Without seeing your entire rule and audit log for context... Using a branch to iteratively add the approvers (or any work item change) can cause update collisions, errors, etc. For a scenario like this, I recommend instead: * using the Lookup Objects action rather…

Hi @André Ribeiro -- Welcome to the Atlassian Community! First thing, let's confirm what / where you are trying to update the fields...You note both a JPD project and a Team-managed project (TMP). And you note "Due Date", which is a built-in field. * In which project are you trying to update the "Target Quarter"? * What…

Hi @JZD Yes, and...to the suggestions from @Mohamed Benziane This question gets asked frequently, including just yesterday. The short answer to your question about any REST API endpoints for logs / failures is: Atlassian does not provide that yet. Please see my response to the question from yesterday for more details:…

Hi @Duc Thang TRAN You are correct: the likely cause of this symptom is the original poster included JQL in the trigger, but it should only be in the Lookup Issues / Work Items action. Removing the JQL from the trigger will solve the problem. Viewing the trigger or audit log would confirm this. As an FYI... The…

Hi @Troy Anderson Yes, and...to the suggestions from @Tuncay Senturk _Snapbytes_ with some adjustments... For iteration which has filtering, I recommend not worrying about a trailing delimiter such as a comma; the complexity / risk of errors is not worth the trouble. Instead, always add the delimiter and remove it later…

Thanks for that information, @Amy Schindel In both your original and the JSON shown in the rule images, there are typos / stray curly brackets. And, please note smart values are name, spacing, and case-sensitive. This is why I suggested using that how-to documentation confirm them. Here is a cleaned up version that may…

Earlier I described creating a Scheduled Trigger rule to help when Atlassian has an outage. That rule may also be used to "catch up" existing Epics: * in the trigger, set the JQL to find Epics where that field is empty * structure the rule based on the trigger work item being an Epic, finding its child work items with the…

Hi @Haddon Fisher If I understand your scenario correctly, you want to just-in-time (JIT) get a field value, selecting that field based upon another reference. As far as I know, there is no JIT interpretation of smart value expressions by-field available to customers. If there was, rules would be even more powerful...and…

Hi @Dan Langenberg You do not necessarily need to wait 2 days if there are work items to process. The rule runs daily so you can check tomorrow...or, for a Scheduled Trigger rule, you may select to run the rule now from the editor and it will process anything meeting your criteria. Kind regards, Bill

Hi @Kelsi Flores -- 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…

Thanks for that information, @Michael Catmur Let's start with the most-likely possible causes... Date value typing You are concatenating a string to a date, and then trying to use that as a date / time. Let's try helping the conversion a bit with forcing the first value explicitly to text before the concat() and then…

Yes, that seems correct as I do not believe Service Projects can have or be in sprints. In my experience, teams use a Service Project to intake requests / problems, and then use that work item to create a separate work item in a Software Project for a team to implement / build changes. As the software work item progresses,…

Thanks for that information, @Louise Woods Have you checked if there are multiple fields with that name, such that you have the incorrect custom field ID? That may be done with an example work item and this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ The essential…

Hi @Pang Yew Ken As is often the case with bot-generated answers for Jira features, that one will not consistently work... There are known defects for list fields (e.g. Sprint, Fix Versions, etc.) such that when a field has changed too many times the changelog provided to the rule is incorrect. The only workaround is to…

@Anurag Vipin Vaidya -- I am not using Jira Data Center, and so a specific example rule from Jira Cloud would be slightly different. The basic outline would be: * trigger: some rule trigger * action: Send Web Request, to call the endpoint with your JQL * action: some action that sums / counts the values from the web…

Hi @Marco Wettstein -- Welcome to the Atlassian Community! Yes, and...to the information from @Marc -Devoteam- The cause of this symptom is a long-standing, racetrack timing problem with some rule triggers, such as Work Item Created. Specifically, the rule can start running before all of the data is available, or the item…

Hi @HQRAZAHS First thing: what source are you using for the smart value expression you tried for the percentage value? I ask, as there are many unsupported and incorrect things in that expression. I recommend not using that source, and instead refer to the documentation from Atlassian for smart…

Hi @Asier Vadillo Short answer: no, that is not possible yet. There is an in-progress suggestion to add REST API support for automation rules and audit logs. The endpoints were added for rule management, but not for the audit logs. I recommend watching / voting for this one to see progress and updates...because once there…

Hi @Pang Yew Ken -- Welcome to the Atlassian Community! As you tried to solve this with an automation rule, context is important for the community to help. Please post the following: * what version of Jira are you using: Cloud, Server, or Data Center * for Cloud, what type of project is this: company-managed, team-managed,…

Hi @Darryl Lee My apologies if I caused any spin, and thanks for confirming my reminder on the branching behavior. I was only trying to help for the specific example rule you showed :^) And another FYI on what you noted for {{lookupIssues}} providing a list of keys to a JQL expression... In my experience, smart values…

Hi @SilkeS Thanks for this new, more focused group! And, you describe this one as "the home for important announcements from Atlassian community managers and product teams." When I joined, I noted that I appear to have permissions to create an article. That surprised me! Should this group's permissions be tightened up a…

Hi @Michael Catmur -- Welcome to the Atlassian Community! 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 * for Cloud, what type of project is this: company-managed, team-managed, JPD, etc. * an image of…

Hi @Ranvijay Singh The purpose of the Lookup Work Items action is to gather a batch of items to use as data, such as to sum a particular field, report them as a set, etc. They cannot be acted upon as issues with individual rule actions. When you instead want to branch over a set of issues, using rule actions on each one,…

Hi @Louise Woods Please post the following for more context to help explain this symptom: * the current, complete rule in one image for continuity * an image of your entire Edit Work Item action * an image of the complete audit log for the rule execution, with all the areas expanded Thanks!