Bill Sheboy Expert

@Paras Dua please review the suggestions from @Trudy P Claspill ... The Lookup Work Items action you show uses JQL which is too broad: it will attempt to find all items with a link type of "Blocks" rather than ones linked to the trigger issue.

Hi @Dmitry Sednevets -- Welcome to the Atlassian Community! I believe that is part of the changes to the admin pages. You may search for "Fields" rather than "Custom Fields", or go directly to it with your Jira URL: yourJiraURL/jira/settings/issues/fields Kind regards, Bill

Hi @Dan Foster Rather than using two fields, have you considered using a Select List / Cascading field for the options? Kind regards, Bill

Hi @A_ Boehme _Communardo_ The Lookup Work Items action requires valid JQL, and the expression you show is comparing a list of field values (e.g., Declined, Declined, To Do) on the left side of an operator to a single value. JQL requires a field, not a value, on the left. Next, why test the outwardIssue ones specifically?…

Thanks for that information. I have seen questions with timing problems with Rovo agents where first storing the {{agentResponse}} in a created variable allowed better access, although I would not expect that to be a problem when logging the value. I recommend working with your site admin to submit a ticket to Atlassian…

Hi @Martin -- Welcome to the Atlassian Community! First thing, well done figuring out a workaround! As a short answer: your solution works so document how it works and explain it to another team member to help with maintenance / improvements. Next, automation rule features differ between Jira Cloud, Server, and Data…

Hi @Lamija Pasalic -- 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 @Paras Dua -- Welcome to the Atlassian Community! I understand why a single delivery team might do this for their work items within the scope of a single project. Other scopes may not provide the expected results. Regardless of that challenge... I notice you are trying to make updates when the Story Points field changes…

Hi @Agus Kanihatu -- Welcome to the Atlassian Community! I recall something like this symptom from a while ago but cannot find a defect for it in the public backlogs for Confluence, automation, or the ecosystem. Are you on a paid Jira / Confluence license? If so, please work with your Site Admin to submit a defect to the…

Hi, @Peter McCann Please try using the if / else condition block for this case: https://support.atlassian.com/cloud-automation/docs/jira-automation-conditions/#If-else-block For example: * ... * action: lookup work items * if / else block* smart value condition: to check if the lookup returned your value * action: edit…

First thing: in my experience, successfully using rules requires learning and experimentation. I recommend pausing to understand the features needed from the documentation and trying simple test expressions, perhaps just writing results to the audit log, to learn what works. This is better than only implementing what you…

Hi @Phoebe Black No, that is not possible yet. Here is the open suggestion to add such improvements to the user inputs for the manual trigger, and you may watch / vote for it to see progress: https://jira.atlassian.com/browse/AUTO-744 Kind regards, Bill

Hi @Daniel Navarro I am glad you found it! With the extent of the UX changes lately, one almost needs to set aside an hour, or more, per week to pause and review all the differences to find things :^) That, and watch all the community articles related to Jira which announce updates. Kind regards, Bill

Please let me know if that works for you...and anything you learn from the support team when submitting the ticket. And if it works, please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

Thank you for that information, and... First, let's add some parentheses for the issue type check to enforce the order of precedence in the JQL: project = "IT ServiceDesk" AND reporter = 557058:f58131cb-b67d-43c7-b30d-6b58d40bd077 AND summary ~ "Jira subtask - New Hire*" AND statusCategory NOT IN (Done) AND duedate =…

Well done, @Céline - Maestrel ! One more suggestion for your rule... The Work Item Created trigger has known racetrack / timing problems, and so the rule can start before all of the field data is ready to be used. This can cause weird errors and unexpected behavior, such as conditions not matching. The symptom does not…

Hi @Greg Trombo -- Welcome to the Atlassian Community! What problem are you trying to solve by writing changes to the Description in the Comments field? That is, "why do this?" Knowing that may help the community to offer alternative solution approaches. Until we know that... The changelog smart values in a rule are only…

Hi @Robert Hook What is the full JQL expression for your search / trigger? What is the scope of your rule in the details at the top: single-project, multiple-project, or global? And, if the rule is single-project scope, is the rule defined in the "IT ServiceDesk" project? If not, it cannot "see" those work items and the…

Hi @엄성렬 -- Welcome to the Atlassian Community! Without seeing your entire automation rule and its audit log details... Perhaps there is an update or timing problem in the rule and thus the work item's data is not matching for the different scenarios you describe. Seeing the rule and audit log may help clarify this symptom.…

Hi @shruti.rupani -- Welcome to the Atlassian Community! The audit log indicates the parent work item type is unable to make the transition. Does the workflow for that work item type support that status and transition, as the the work items appear to be in different projects? Regardless of that symptom, the scenario you…

Thank for confirming that all of the work items (parent and children) are in the same Jira Project. Next thing to try: let's assume the Child condition check does not work as expected. We can test that by disabling your current rule and performing the check using the Lookup Work Items action instead with a new rule: *…

Hi @Kevin Wujcik -- Welcome to the Atlassian Community! The built-in Target Start and Target End fields' values provided to rules are text representing a date value. They cannot be used with the diff() function until they are converted with toDate:…

Okay, resetting a bit...Let's confirm a key assumption: are all of your work items in one single Jira project? If not, what is the scope of your rule in the details at the top: single-project, multiple-projects, or global? A single-project scope rule cannot see the work items in other projects, and so the result of that…

In that case, the JQL should contain both work item types. Without seeing all of the JQL as it is concealed, an example might be: project = myProject AND issueType IN ( Feature, Initiative )

Hi @Lee Street Yes, and...to Walter's suggestions... Apparently the built-in field cannot be added to a team-managed project. Here are the relevant suggestions and defects: https://jira.atlassian.com/browse/JRACLOUD-85690 https://jira.atlassian.com/browse/JRACLOUD-94862 Kind regards, Bill

Hi @philip_song Short answer: you have found a defect in the Lookup Work Items action using JQL, and there is a workaround for it. Testing a standalone work item search with that JQL and the CONTAINS ~ operator, I observed: * when there are spaces after the commas, no results are found:* myField ~ "123, 124" * when there…

Hi @Ivan Zuniga Alegria -- Welcome to the Atlassian Community! Adding to John's suggestion... You may do this in two steps: find the comments which were not internally flagged, storing them in a Created Variable, and then get the most recent one (last, non-empty one in the list). For example, and assuming these are issues…

Hi @Jon Platt For a single work item, please try this value for the earliest started date / time in the worklogs: {{issue.worklogs.started.min}} As that is a date / time and Start Date field is a date only, please add the jiraDate format to the end to set the field in the correct format:…

No worries, and we are all learning as rule-writers while the product continues to improve.

Hi @Ivo Stoyanov There is an active production incident causing delays in rule execution. Please review or subscribe to this one for updates: https://jira-software.status.atlassian.com/ Kind regards, Bill