Bill Sheboy Expert

When you use the Edit Work Item action... * select the Due Date field from the dropdown list * on the right side of the field, use the ... menu and COPY * select the expression shown * and change the copy value from to the parent (i.e., the Epic) If that does not help, please post an image of your complete rule and the…

Let's make two changes to your rule and then re-test it: * The new feature to add conditions to triggers conceals why a rule did not trigger. Until Atlassian solves that and other limitations with this feature, I recommend not adding conditions to triggers. Instead, add a separate condition after the trigger. * Your rule…

Yes, that is a limitation for rules: there is no concept of a function / subroutine callout to another rule. Instead, you could try using the REST API endpoint to get the metadata, or an example work item, and thus have a list of all of the fields. Then use that structure to build the mapping information in a created…

Thanks for that information, @Martin Hirsch When you create a work item in the rule, and then want to access it for updates, the rule needs to branch to it first: * trigger: manual, with your input * action: create work item, for the task * branch: to most recently created work item* action: log work

Hi @İclal Aslan Adding to the other suggestions provided... The new search endpoint apparently does not return some of the worklog data, and the format is different for comments, worklogs, etc. due to the changes to respond with ADF. Please see this defect to learn more: https://jira.atlassian.com/browse/JRACLOUD-71136 The…

Hi @Svante Gustafsson Björkegren I wonder if the JSON parsing from the webResponse is detecting the type as number rather than text type. You could check that by forcing conversion to text with format() prior to the match() function: {{webResponse.body.id.format("#").match("(27653)").size}} Kind regards, Bill UPDATED: as…

Hi @Mar Yes, and...to the suggestions from others: The behavior of the list size function can be inconsistent, such as when no work items are found for the Lookup Work Items action. That could definitely happen in the rule you show due to known, racetrack timing problems with the Work Item Created trigger. Some adjustments…

Hi @SilkeS Thanks to you and the team for the opportunity to provide feedback! For future surveys, please consider increasing the character count for comments; I had to triage mine by 80% to fit in the 500 chars :^) Kind regards, Bill

Hi @Christopher Carvalho First thing, I recommend not deleting work items. There is no "undo", increasing the risk of deleting something accidentally. Instead, consider removing the "delete permission" from everyone except Product Admins, and instead ask people transition items to Done (or Cancelled), with a Resolution of…

Hi @Mahesh Ghanta -- Welcome to the Atlassian Community! The image you posted seems to be truncated. Please post an image of your complete rule and another image showing the audit log details for the rule execution. Until we see those... Please note links have direction (e.g., "blocks" versus "is blocked by"), so ensure…

Hi @Martin Hirsch What have you tried thus far to solve this? If you have an automation rule that is not working as expected, context is important for the community to help. Please post the following: * what type of project are using * an image of your complete rule * an image of the audit log details * explain what is not…

Awesome; I am glad to learn that solved it! If you are interested and still have the old rule, you may be able to identify the cause by exporting it to JSON and reviewing it. My hypothesis is it's one of these: * the lookup table's stored ID value is corrupted and does not match between the two actions: the create and the…

Thanks for checking those things, @Vikrant Yadav I just ran my ginormous test rule to exercise lookup table features and saw no change in behaviors. Have you tried disabling this one and re-creating it to test for a rule "glitch"? And, you do not show your entire rule. What is trigger? Perhaps there is some weird timing…

Hi @Vikrant Yadav Without seeing your rule's audit log... * What is the type of the custom field: select option, an asset value, something else? * Have you confirmed the lookup table Key values have no trailing spaces? * Same thing for the custom field value? * Have you confirmed the lookup table Key values exactly match…

Hi @Ganesh Sureddy -- Welcome to the Atlassian Community! First, this is not the contact channel for Atlassian Support. It is a community of people trying to learn and collaborate regarding Atlassian-related products. When you are on a paid license, your Product Admin may contact the support team here:…

Hi @transreductionist -- Welcome to the Atlassian Community! Which REST API endpoint are you using when you "look at my Jira ticket in the Cloud" and observe a "tab called Metadata"? https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/ And, I recommend reviewing the documentation for the Jira python library…

Thanks for that information, @Ron Hayes The endpoint I suggested could help with that, and the general rule structure would be: * trigger: some trigger, such as scheduled * action: send web request, to call that endpoint to get the queues with their JQL expressions * assuming a known number of queues...* use the Lookup…

Thanks for the additional information, and as an FYI -- I am not an Atlassian employee. I'm just another Jira user trying to collaborate in the community. If you are seeing a specific problem, consider working with your Product Admin to submit a ticket to Atlassian Support. They can do that when you are on a paid license…

Hi @Ron Hayes -- Welcome to the Atlassian Community! What problem are you trying to solve? That is, "why do this?" Knowing that may help the community offer alternative suggestions. Until we know that... * You can view / edit the queues and their filters from the queue settings page * To get the stored filters directly,…

Hi @Maxime Besson -- Welcome to the Atlassian Community! First thing, what problem are you trying to solve by recreating the Sprint Report which is already in Jira? Knowing that may help the community offer alternative suggestions. Until we know that... Theoretically, one could call the REST API endpoint to get the…

Ah, thank you for that information, @Christy Lutz JPD Custom Formula fields cannot be updated directly with automation rules. Indeed, they are calculated just-in-time for display only, and I do not believe they actually store a value anywhere. The workaround to use them outside of the JPD display views is to re-create the…

Awesome; I am glad to learn that helped!

To test, you could change the Scheduled Trigger's JQL to only return one work item with: key = LOCAL-4571 And, please re-read what I posted as the rule would use a Lookup Work Items action in order to use the {{lookupIssues}} smart value. It would not use the JQL condition as you show.

Thanks for that information, and I believe you have outlined the rule with the steps you note: * trigger on the transition, * check the issue type is a Story, * check the Due Date with a condition, * and when empty, copy from the parent Epic. Have you tried creating the rule, and if so, run into any challenges?

Hi @Christy Lutz First thing, smart values are name, spacing, and case-sensitive. The correct one for the trigger issue is: {{triggerIssue}} Next, what are types of your fields: text, select option, etc.? Knowing that will help identify how to copy the value. Also, would you please post an image of the audit log where the…

Hi @Travis Sims Are you wanting to do this with the workflow on some condition or with an automation rule on the status transition? Kind regards, Bill

Correct: when using smart values to create a dynamic JQL expression, that cannot be validated by the rule. Instead, it is a good idea to test the JQL outside the rule with an example work item to confirm it works as expected. And...With my suggestion, your rule would not use the branch as the lookup and condition take the…

Hi @Sierra L_ -- No, you could use the JQL needed to select only your specific ones. For example: * action: lookup work items, with JQL of project = yourProject AND issue IN linkedIssues("{{triggerIssue.key}}") AND issueType = Task AND statusCategory != Done * smart values condition* first value: {{lookupIssues.size|0}} *…

Hi @Sierra L_ -- Welcome to the Atlassian Community! Would you please clarify your scenario? Is it one of these: * GIVEN a work item which has 8 other Tasks linked to it, WHEN all 8 Tasks are closed, THEN... * GIVEN a work item with a linked Task, AND that linked Task has other linked Tasks in a chain of 8 work items, WHEN…

Thanks for the additional information, @Ellen Gruebbeling The primary thing with dependent work items is having something to connect them, as that allows walking the chain for checks, updates, etc. And so the team needs to select one method and use that consistently. If the team is manually creating the work items, they…