Bill Sheboy Expert

If the custom field is just a dropdown list of text values, then .value should work as the parameter in the lookup...as long as they exactly match: {{tableAgentToTL.get(issue.customfield_11772.value)}}

Thanks for your post, @Sam Nadarajan I find this is a common issue, for both inside of work and outside of work scenarios. Inside, lots of software engineers rationalize spending "just 10 more minutes", expanding into hours / days, to fix something rather than pausing to explain it out loud to another person, where the…

Hi @Farhad Malegam -- Welcome to the Atlassian Community! First thing, I am just another Jira user and have no knowledge of automation engine internals or Atlassian decision-making. With that out of the way... I suspect the answer to your question is: "no". Although Atlassian products have been around for a while, they…

First thing: well done experimenting to get it to work! Some adjustments and I believe you will have it done... Your table now contains the Agent user's displayName for the key and Lead user's accountId as the value. To find the lead for an agent, try this: {{tableAgentToTL.get(issue.customfield_11772.value.displayName)}}…

Hi @Stefan Salzl and @Nathan Unsworth Well done finding a workaround, Nathan! Stefan, I believe searching / filtering the table requires: * grabbing the table content, * creating a dynamic regular expression, * splitting the tables rows and using match() with the dynamic regEx, and * parsing the results to get the App…

To append rather than replace the values, use the "update" syntax with "add". There is example of that syntax shown in the link I provided you earlier. If that does not help, please post the JSON you are using to provide some context for suggestions. For the approvers who are not Jira users, I am not familiar enough with…

For your two additional questions: When a field is edited by a rule, the updated information is not visible to the remaining steps of the rule; it still contains the information from the time the issue was loaded by the rule, such as at the time of triggering. That is what caused the need to split the rule. You can…

For the field rankBeforeIssue, only one issue key is expected. And so using the first one from the lookup helps ensure that. Also...the criteria for your linked issues condition and the lookup issues are different. Thus it is possible the lookup issues could return zero or more issues. (It could return zero due to the…

Hi @Christian Gräfe -- Welcome to the Atlassian Community! First thing, I am using Jira Cloud, and not the Data Center version. My suggestions are based on what I know about rules, so please test for your Jira version. Second thing: if this is a scrum team, and the people participated in sprint planning, wouldn't they…

Thanks for the feedback and ideas, @John Funk Good points about the project type, especially noting company-managed versus team-managed, as sometimes the same type of field for the UX are implemented differently behind the scenes. (e.g., People fields are always multiple-select, even when the single-select option is…

Hi @Divya S M -- Welcome to the Atlassian Community! 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 rule execution, and explain what is not working as expected. Those will provide context…

Hi @Andrew That is not possible yet and is one of the known limitations for JPD and automation rules: https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Known-limitations-of-Jira-Product-Discovery/ba-p/2069648 You may want to follow that thread and the JPD group for any updates on topic:…

Hi @Daniel Bermudez Which checklist addon app are you using from the marketplace? The specifics for that app will influence how to do this, or if it is even possible. I recall several of the apps have documentation on their marketplace pages explaining the use with automation rules. Kind regards, Bill

Hi @Carolina Rodriguez Currently, the default when a list field is used that way is to join the values of the default attribute with a comma and a space. I have not found this default behavior documented, so it may be better to take some control over it... Instead use an explicit join() function to force the key to delimit…

Hi Sunny Kumar, What version of Jira are you using: Cloud, Server, or Data Center? The version you use impacts which automation features are available to do this summing for custom fields. For Jira Cloud, the Lookup Issues action could be used with JQL to gather the issues and sum the field:…

Thanks for confirming that, and... When testing a rule like this, you may want to use a test project and set the scheduled trigger frequency faster. That will confirm the trigger, JQL, and rule actions work as expected. Once testing is done, the schedule may be updated before the rule is copied / updated to run in the…

Returning to your JQL statement for a moment, did you really want to check things that have not changed for the last 2 minutes? Your original question stated 3 days.

When doing things in Jira Cloud automation rules with user fields, the account ID value must be used to set a field. You tried using the display names, which would not work directly. (Please see the end of my long post for more info on searching by display names.) Here are some suggested adjustments to help... * I…

Hi @Juan Camilo Gomez What have you tried thus far to solve this need? If you have a rule that is not working as expected, please post images of your complete rule and the audit log details, and describe what is not working. If you have not started a rule, you have written an outline for it with your question. The…

Hi @Ferdinand Peu Test -- Welcome to the Atlassian Community! You posted this question in the automation rules area. If you want to format a date, such as for display in an email or message, please use the built-in formatting or the format() function with your needed layout:…

Thanks for that information, Jenny. If you expand any of those "No Actions Performed" items with Show more, I hypothesize it will show in the details that no issues were found. Three things to check for that: * In the trigger, is the option checked for "Only include issues that have changed since the last time this rule…

Hi @Rose Seed -- Welcome to the Atlassian Community! One possible cause of that symptom is the sprint started before the story points were set for the issues in the sprint. Did you check if that happened? It is easy to see if you look at the burn charts as they will show the increase in scope (i.e., total story points)…

Hi @Mark Williams Do you mean something like this: GIVEN there is an existing issue-X WHEN a new issue is created that could be a child of issue-X THEN the new issue's parent is set to issue-X AND specific fields from issue-X are copied to the new issue If so, yes, that is possible. Try hardcoding the parent issue's key in…

Hi @Joana Dias Fernandes -- Welcome to the Atlassian Community! First thing, I am not using JSM; my suggestion is based on what I know about rules, and I have not tested the suggestion. As you want to add values from different sources, including some pre-selected ones, you could try using the advanced edit with JSON to add…

Hi @Luyang Zhang -- Welcome to the Atlassian Community! 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 rule execution, and explain what is not working as expected. Those will provide…

Hi @Mareli The Lookup Object action is available for Jira Service Management (JSM) projects: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-objects Your first rule's scope could not "see" it, and the global rule could because of the larger scope. Given the trigger is on issue…

Let's assume this is for one project and you only care about issues in the backlog. To find the issue which is currently the highest-ranked one, JQL may be used: project = yourProjectName AND status = Backlog ORDER BY Rank ASC The first one in the list is the highest-ranked issue. Thus a rule could use the Lookup Issues…

Hi @ayoung From what you describe, it seems there is a mapping of many-to-one for: Agent Requiring Coaching -> Agents Team Lead Perhaps try the Lookup Table first, although that has a limit of 200 rows. Do you have more than 200 Agents or Team Leads? For some ideas on using Lookup Tables, please see these two articles: *…

Have you discussed this scenario with your Jira admin yet? I recommend doing that before you proceed further, as you have not explained the problem you are trying to solve and the conversation with your admin may help. For example, you do not describe why or when this change of rank is needed, and those impact the rule…

Hi @Rafal Wzorek The cause of the problems seems to be there are multiple fields with the same name causing confusion in rule processing. What is the purpose of the added custom field? Additionally, the built-in "Due Date" field has multiple smart values that work in rules and so that could cause further confusion with…