Bill Sheboy Expert

Indeed...there is no "Edit Variable" action yet and so variable-shadowing is the work-around to help with this other work-around :^)

Hi @Alexis LAFONT -- Welcome to the Atlassian Community! As you have found, once inside of a list iterator no other higher scoped fields/variables are visible. There are several possible work-arounds for your scenario. One is to expand all of the displayNames into a created variable first (with delimiters), then use the…

Hi @Mario Amaya (x) -- Welcome to the Atlassian Community! I believe you want {{issue.priority.name}} for that one. The attribute displayName only applies to user fields, and for other fields the human-readable value is often name or value. Next thing, here is the reference of issue…

I reproduced that symptom, and you have found a defect: For a Create Issue action inside of an if/else clause, when using issue linking both the Most Recently Created Issue (drop-down value) and {{createdIssue}} smart value incorrectly identify the last created issue as any issue created *before* the if/else clause. Now…

Hi @Dd Adding to Hana's answer... Please post images of your complete rule and of the audit log details showing the rule execution. Those will provide context to help explain what you are observing. Thanks! Kind regards, Bill

Hi @James Harris -- Welcome to the Atlassian Community! I do not believe there is a built-in way to do that; it would require having roll-up data about the grouping of ideas. When "group" is used, the sort always occurs within the group. A work-around could be to use the matrix view... * create a field for the Group…

Hi @Eran Roiter How is that specific issue associated to the release? For example, is the fixVersion of the issue set to that release? If so you could branch to the issues in the release and then use a condition to check the issue type. Kind regards, Bill

Thanks for clarifying and posting your rules, @Mee Soo What I noted earlier is for branches. For the if/else when I tested the {{createdIssue}} is indeed set correctly. The challenge for your rule is the first issue create is inside of the if/else...and when the issue is NOT created there is not "most recently created…

Reviewing the audit log, it appears your release names have non-alphanumeric characters in them. Please try wrapping the smart value in quotation marks to make that work. Also...do you want that condition in both this rule and the second one? The first does the version release and the second rule does the email, correct?

Hi @Josh Collins -- Welcome to the Atlassian Community! I can think of a few ways to do this, and one is with * Using a scheduled trigger rule with no JQL * Add a branch to find overdue issues for a specific assignee, and enable the bulk-handling option * Use a condition to check if there are issues, and * If found, send…

Hi @Antonio Carvetta What problem are you trying to solve by doing this? And specifically, what is significant about the "first" value, and what does "first" mean to you? Simply put, why do this? Knowing these things will help the community to offer suggestions relevant to the problem you are trying to solve. Kind regards,…

I wonder if the dynamic nature of assets and lookup objects is preventing this, similar to what happens for calculated fields with marketplace addons. Let's try a work-around: * with a Create Variable action, save the value {{lookupObjects.first.id}} and let's name that varFirstId * write that to the audit log to confirm…

What do you mean by "show the % completion"? For example if you wanted to send a message/email, you could use the bulk-handling feature of branches and smart value, list filtering, and math functions to calculate the sum of story points for done issues divided by the total. If instead you want to update a field in the epic…

Thanks for clarifying. In your case you only want the differences and are using the change log for a single People field change. I do not know if {{fieldChange}} works with people fields, but there are a couple of options there you may want to try: {{addedFieldChange.valueIds}} {{deletedFieldChange.valueIds}} Those may…

Hi @Dylan Willis -- Welcome to the Atlassian Community! Adding to Trudy's answer... If you want to preserve the value for later analysis, consider adding a field to capture Age of WIP, as described…

Hi @Paul Benati -- Welcome to the Atlassian Community! Before proceeding...Please note that team-managed project's People fields have limitations in automation rules. I believe there are several open defects on them not being usable in emails, notifications, etc. from rules. If you need to do any of those things please…

Hi @Gabriel Greenbank -- Welcome to the Atlassian Community! Is your list of email address only for this rule or for other uses? If it is just for this rule, perhaps try a Lookup Table to store the email addresses and then key them to the custom field value. Please look here for more information on that…

Hi @vasileios.ntelopoulos That is not possible with out-of-the-box features of Jira, and there are several suggestions related to improving the display of empty fields. Some of these have work-arounds to try updating the site banner, although that does not appear to always work for some browsers. Kind regards, Bill

Hi @Ahmad Sidawi First thing: I am not using Insights, and so I am basing my suggestion on what I know about automation rules. I believe lookup objects is returning, well...an object. That has structure to it and is not just text. Perhaps try accessing the value attribute before the split, like this:…

Hi @[deleted] For a question like this, I recommend posting images of your complete rules and the audit log details showing the rule execution. Those will provide context for the community to offer suggestions. Until we see those... As you have learned, some of those DevOps triggers fire for each issue, which is unhelpful…

Hi @S Suresh -- Welcome to the Atlassian Community! I believe you could do that with either an automation for Jira rule, or one of the marketplace addons for scripting fields. However... What problem are you trying to solve by doing this? What does this counter field represent? Knowing those things may help the community…

Hi @TP Are all of the fields you note in your Jira Product Discovery (JPD) project? If so, it does not appear there is a max() function for custom formulas in fields yet. Have you considered using an automation rule in your project to set the field? Kind regards, Bill

Hi @Mee Soo -- Welcome to the Atlassian Community! That is a known symptom/behavior and is based on how branches work...Scope is important with branches when trying to understand smart values: Branches on one-and-only-one thing (e.g., branch to parent) get run inline, as if the branch was not there. For that case I believe…

Hi @Reshma Ulvekar Lookup Issues is currently in progress for adding to Server/ Data Center, and you can watch progress here: https://jira.atlassian.com/browse/JIRAAUTOSERVER-53 Until then, would you please confirm what you are trying to measure; that is, what do you mean by % completion for a child issue? Server / Data…

Hi @Sankalp Chugh First, I recommend creating a new question, with images of your complete rule and audit log details, and providing a link back to this thread. Otherwise only the people following this older thread will see your post. Are you using Jira Cloud or Jira Server/Data Center? That impacts which features are…

Interesting...when I did a quick test to check the REST API with an Idea issue type, I did see the linked delivery issues in the results. Please post what you learn after the call to benefit the community. Thanks!

Hi @PeterE Without knowing more about your scenario, I hypothesize accessing the linked issues between Ideas and other Jira issues is possible in automation rules. You can confirm that using this how-to article, which describes how to learn if a field is supported by automation rules, and the exact structure and smart…

Hi @Sebastian Somi That branch type works when the trigger is for a version (e.g., version created). Instead you will want to use a JQL branch to find the issues which have the same fix version as your trigger issue: project = myProjectName AND fixVersion IN ({{triggerIssue.fixVersions.name}}) Please note: if your issues…

Rank (aka, LexoRank) is the internal mechanism Jira uses to handle ordering issues for sorting. It allows adding/removing/updating/moving an issue with no changes to the surrounding issues while managing the ordering. Although you can look at Rank, it may not help as it is a text string of letters, numbers, and…

Hi @Yahyaa Bham -- Welcome to the Atlassian Community! Do you get a rule trigger for each update, or do you get several in a batch? I believe there are at least two ways to solve this, based on your answer to above... * Try smart value, list filtering to select the record(s) meeting your criteria, and then process them.…