Bill Sheboy Expert

Hi @John Funk I do not believe lookup tables have been implemented yet for the Data Center version of automation rules. Kind regards, Bill

Hi @Yarden Admon -- Welcome to the Atlassian Community! For a question like this, please explain the problem you are trying to solve, and 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…

Hi @Najjar _Innovura_ As a reminder...when recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Community online guidelines | Marketplace + Solution Partners | App Central…

Hi @Sam I suspect the answer is "no" as that feature seems to be for the display view of the time tracking, and it is likely implemented in the code for time tracking display only. If it was something that was configurable elsewhere (or even readable with the REST API) that checkbox setting would be set with the Estimation…

Hi @Adrian Szubert -- Welcome to the Atlassian Community! Regarding the rule triggering information you note, this may be a matter of semantics where: * a rule cannot directly start another rule executing (i.e., one rule cannot call another rule); instead... * the actions performed by one rule can trigger another rule.…

Hi @GC This is a challenging scenario to solve for non-trivial Jira site configurations. Perhaps start small, with a single project and then scaling up to handle other projects / types. You appear to be using a Jira Premium license level, and so I hypothesize you have many projects, of different types (including…

Hi @Luca Schernbeck -- Welcome to the Atlassian Community! The diff() function for date / time values always returns an integer value...and I believe may use some floor, ceiling, or rounding, based upon the units of measure for the diff. When you want the fractional part, you could use a smaller unit of measure and a math…

Hi @Mguiss_ Anis _AllianzGI_ Adding to John's suggestions: Please also include an image of the audit log details showing the rule execution and explain what you observe when you note "it did not work". Those will provide more context for the community to help. Thanks! Kind regards, Bill

Hi @Purnama Sari -- 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 @Pritam Rakshit -- Welcome to the Atlassian Community! 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 your complete rule and the audit log details, and explain what is not working. Those will provide context for the community to offer…

Hi @Yugandhar Kumar Chintamaneni -- Welcome to the Atlassian Community! Automation rules trigger after an event has occurred, such as an issue transition. They cannot block or prevent the event. Instead investigate using workflow validators, perhaps from an addon, to prevent the transition. Kind regards, Bill

Hi @abhijeet.chitriv -- Welcome to the Atlassian Community! A rule could do that with an advanced branch, iterating over the values in the Fix Versions for the issue: https://support.atlassian.com/cloud-automation/docs/jira-automation-branches/#Advanced-branching For your case, the rule might look like this: * trigger:…

Hi @Sophia Do Thank you and the team for these great updates! Regarding the rule validation item, how would you expect that feature to work when: * there are multiple errors * errors within condition blocks * errors within branching blocks * errors after either conditions or branching blocks I did some quick tests and…

From what you describe, it appears you are trying to gather a distinct list of the Fix Versions in the linked issues (i.e., Feature, Bugfix, and Maintenance) and store that distinct list in a field in the Task. If that is correct... Your rule shown uses a branch, and that will not allow updating the Task. Instead consider…

Hi @Aleksandra Leesment What is not working? When I just tried the lookup from the original question with Jira Cloud, it does filter to only return the JPD projects with the example below: myJiraURL/rest/api/2/project/search?typeKey=product_discovery Version 3 of the REST API also works for this. Kind regards, Bill

Yes, and... For Jira Cloud, Server, and Data Center, I believe the if / else conditions are a high-maintenance solution. With Jira Cloud, a Lookup Table would make that slightly easier to maintain. One would hope for a method to "find the teams for a user", but there is no REST API endpoint to do that yet. Here is the…

If you mean getting the sprint created immediately before the one in the trigger, that is more difficult. Using some assumptions you might be able to reduce that difficulty... If you assume there are issues assigned to that prior sprint, you could use the Lookup Issues action with JQL, and get an example issue's value for…

In the Create Issue action, you may use the "Choose fields to set" dropdown list to select the Sprint field. In that field, select current, active sprint for your board.

Hi @Joni Johnson Yes, a smart value (containing a list of, or delimited, values) could be used to create a dynamic JQL statement to find issues. For example, to find the subtasks of an issue: key IN ( {{issue.subtasks.key.join(", ")}} ) However you seem to be describing a scenario that would require both nested branching…

Hi @dlphi -- Welcome to the Atlassian Community! If you already have these two rules written, you may mine their contents to create your new, single rule. If not, this outline of a rule may help: * trigger: scheduled weekly with no JQL * action: lookup issues with JQL, to identify any issues with owners / assignees that…

Hi @Antoine Claudé-Pénégry Short answer: there is no easy way to do this unless you have a very small number of users in your Jira site. More information... There is no sequential looping in automation rules, and so it would be challenging to loop through any mentions and find / replace the accountId values with looked-up…

Hi @Max Haley I have not used that one before, and based on the documentation for the REST API: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#pagination maxResults is the maximum number of items that a page can return. Each operation can have a different limit for the number of items returned, and…

Hi @Dalcina Duval -- Welcome to the Atlassian Community! Context is important for automation rule questions. I recommend creating a new question, adding a link back to this thread, and including images of your complete rule, the action details where you are using that JSON, and the audit log details showing the rule…

Hi @amehar -- Welcome to the Atlassian Community! Adding to Rudy's suggestions... You describe a rule which may look like this: * trigger: Sprint created * action: create issue * action: create issue * ... As Rudy notes, for the Sprint Created trigger, the {{sprint}} smart value is the one just created based upon the…

Hi @ehr -- Welcome to the Atlassian Community! First thing, what problem are you trying to solve by replacing the description of the linked issues with a URL to the Fix Versions for each issue? That is, "why do this?" Knowing that may help the community to offer better suggestions. Until we know that... When inside of an…

Hi @Paul Merrill When you create the new issue, do you set the Sprint field to the "active sprint"? If you did and it is not working, please post an images of the Create Issue action and the audit log details showing an example where the rule ran and the field was not set. Those may help to explain this symptom.…

Hi @Dipen This is a frequent question in the community, and you may calculate the percentage complete (by story points) using one Lookup Issues action and no Created Variables for intermediate steps. To do this, please see this earlier post:…

Well done solving that one!

Hi @Mihir Vibhu 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.…

That log shows one of the three users is inactive, and so perhaps that prevents adding the approvers. Try removing that one.