Bill Sheboy Expert

Hi @Dwayne -- Welcome to the Atlassian Community! To change the Rank of an issue, please call the REST API endpoint using the Send Web Request action. The essential rule outline could be: * trigger: issue created * condition: issue type is Bug * action: lookup issues with JQL, to return all backlog issues with an ORDER BY…

Unfortunately, there are cases when changes to issues are not recorded (or displayed) in the issue history. That normally happens for changes made by addons or combined operations by Jira... In this case, where the subtask "inherits" the parent's Sprint value, when the subtask is converted to an issue (e.g., Task) the…

Hi @Bandarupalli Sai First thing, as this is an older thread I recommend creating a new question, perhaps with a link back to this one. That will ensure the maximum number of people see it to offer suggestions. Back to your question... What problem are you trying to solve? What do you mean by "we can't use the floating…

Thank you for that information. And please try to respond within one thread. That will help others reading this question in the future know if there are multiple solution approaches. I still do not understand how copying a Task helps with counting the number of assigned issues. Instead the counts may be found using a…

I am unclear why this is not working for your rule with a text (or a number) value for the watcher id. And I am certain setting the watcher from a variable works for Cloud and for other posts I have seen for Data Center. I recommend working with your Jira Site Admin to submit a ticket to the Atlassian Support team. Perhaps…

Hi @Casey Gould You are correct: currently, an if / else condition cannot be used within a branch. Sometimes this need can be solved by inverting the cases: use if / else, and put the branches inside of each case. That may not been needed for your scenario. For your specific questions / options: #1) Yes, you could use…

Hi @Anna Short answer: I do not believe that is possible, and even if it was, it may be unreliable. The {{rule}} smart value provides the rule's name and the actor: {{rule.name}} and {{rule.actor}}. It does not provide other information about the rule. And, there is no public REST API yet to query the rule for other…

Hi @Adilet Seit What problem are you trying to solve by doing this? That is, "why do this?" Knowing that will help the community to offer better suggestions. Until we know that information, let's align on some Jira terminology... When you note "tagged" do you mean when a user is mentioned? Where do you want to check for…

Hi @Sean Duffy -- Welcome to the Atlassian Community! By "average days aging", I assume you mean: for all unresolved issues on date X, what is the average number of total days since issue creation. There is a built-in dashboard gadget called Average Age Chart which can provide a yearly grouping, but it does it for the…

Hi @Bryan Kim 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 for the community to offer ideas.…

Hi @Chukwuma Ezeh -- Welcome to the Atlassian Community! What do you observe happening when the rule does not work as expected for Story issue types? Please post an image of the audit log details showing the rule execution. Kind regards, Bill

Hi @Mehdi Bouazza There is no built-in way to do that. Two possible workarounds are to select every option shown in the create issue action for the field, or use a more dynamic approach: * use the REST API and the Send Web Request action to gather all possible options for the field * use advanced edit with JSON to build a…

Hi @Chukwuma Ezeh As this is an older thread, I recommend creating a new question, and perhaps linking back to this one. That will ensure the maximum number of people see it to offer suggestions. When you create you new question, please include this information for context: * what problem are you trying to solve; that is,…

Hi @David_Mason -- Welcome to the Atlassian Community! You describe trying Lookup Tables, and so I wonder if you are using an automation rule. If so, context is important for automation rule questions. Please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of…

Hi @Sari Kachorovsky Are you using a company-managed or a team-managed project? Does the converted issue appear on the Sprint Report as removed from the sprint? If using a company-managed project, this is a known defect: https://jira.atlassian.com/browse/JSWCLOUD-23342 Kind regards, Bill

Hi @Amir Shmulevich -- Welcome to the Atlassian Community! Please clarify what you are trying to accomplish as it is unclear. And what have you tried thus far to solve the need? Are you trying to accomplish this: GIVEN there is an Epic with one or more child issues AND the child issues have one or more selected Fix Version…

Hi... Creating a variable inside of a branch which could be on more than one thing will not work for this scenario. Such branches run in parallel and asynchronously, and thus the variable will repeatedly go out of scope. After the branch, the variable is not available.

Hi @Angie Adams The reason for that difference is the {{triggerIssue}} always refers to the trigger issue and {{issue}} is relative to the location in the rule flow. For an example, please consider this sample rule... * trigger: some trigger with an issue ==> At this point, both {{triggerIssue}} and {{issue}} refer to the…

Hi @rajul.mehta -- Welcome to the Atlassian Community! Yes, that is possible. What have you tried thus far to solve this need? If you have a rule which is not working as expected, please post images of the complete rule and audit log details, and explain what is not working. That will provide context for the community to…

Hi @Chris M_ The reasons some of your early attempts did not work could be... Smart values are name, spacing, and case-sensitive, and you were using the incorrect case for the field. To learn the correct smart values for a field, please use this how-to…

Hi @McKenna Hogan This appears to be a design choice by the team-managed project (TMP) people. Specifically for these scenarios: GIVEN there is an active sprint in a team-managed project WHEN a story is created with the top-navigation Create button AND the sprint is selected when the issue is created THEN the sprint is set…

Thanks for that information, Nick. What do you want the rule to do with the Epic's date fields when there are no values found in the child issues? For example, should it clear the date, leave it as is, or something else? Regarding min / max, for your scenario you are apparently trying to find the earliest Start Date and…

Hi @Maela Aseglio To use the Lookup Issues action, first write the JQL needed to gather the issues and add the action inside your branch. In your case, that would be this: parent = {{issue.key}} That will return all of the child issues of the Epic branched to. Then the correct smart value (or custom field id) is needed to…

Hi @Nick Brotherton -- 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 @Snorre Strand Asbjørnsen Short answer: that is likely possible. First, Jira Product Discovery (JPD) projects have Idea issue types, and those have specialized link types to "delivery tickets". Those delivery tickets are normally Jira Software Project (JSP) issues, allowing visibility of delivery progress. Next, a…

Hi @Sidharth verma With the Lookup Issues action, there is no way to dynamically access a specific number of issues. One alternative is to use the REST API if your number of issues is 100 issues or fewer: * rather than using Lookup Issues, call the REST API issue search with the JQL using the Send Web Request…

Awesome; I am glad to learn that helped! And...I recommend pausing to understand how that expression works, perhaps re-reading the original thread description, and then explain the rule to a teammate. Doing so will help with rule maintenance / improvements in the future.

Hi @Dd 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 for the community to offer ideas. Thanks!…

Hi @Sana Usman -- Welcome to the Atlassian Community! First thing, there is an open incident for automation rules not running when expected (or appearing as missing): https://jira-software.status.atlassian.com/ Please follow that incident to see progress / status. In the meantime...For a question like this, please post an…

Great! Now let's update that audit log write to include the status information to observe if they are filtered out: looked up issues: {{#lookupIssues}}{{key}}: {{Story points}} points in {{status.name}} ({{status.statusCategory.name}}); {{/}} Hold on...I just reviewed your earlier post and it is missing the story points…