Bill Sheboy Expert

Hi @Dinesh Bontha -- Welcome to the Atlassian Community! The older v2 Issue Search endpoint provided a "total" attribute with the count, and that one is deprecated: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-get The newer v3 Issue Search does not provide the…

Hi @Ronda On the first page of this thread, select Watching after the article's text and that will toggle it off. If someone mentions you directly, I believe you will still be notified. Kind regards, Bill

Hi @Ana Santos There are a couple of ways to update an existing page... There is a new rule action Edit Page, which supports adding text to the end of a page. This action is based on updating either the "trigger page" or the "current page" within the rule scope. And, I expect if you add the Jira work item as a URL it will…

Agreed; they definitely slow down workflow as they often need to be dismissed manually before one can proceed...especially when using keyboard shortcuts.

First thing: while Atlassian is renaming "issue" as "work item", they have stated it will not impact smart values a this time. And so the smart value for Lookup Issues (or Lookup Work Items if your UX has updated) is still: {{lookupIssues}} Next, as I hypothesized, your rule is missing the lookup action. Please add that…

Please review my earlier suggestion as your rule is missing the condition after the lookup and before the transition: * smart values condition:* first value: {{lookupIssues.size|0}} * condition: equals * second value: 0

Awesome; I am glad to learn it is working! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

Hi @M0214104 For a question like this, context is important for the community to help. Please post the following: * what version of Jira are you using: Cloud, Server, or Data Center * for Cloud, what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete automation rule in a single…

Hi @Tomasz Osik Which endpoint are you trying to use? To get a specific page's content, please try this one: https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-page/#api-pages-id-get Kind regards, Bill

Hi @Kristján Geir Mathiesen Fun topic! I agree with Andy on ALT-TAB for window switching, and using Control-F (Find) for software development, page searches, etc. Yes, and... It took me a long time to stop using the old WordStar commands that were universal in different vendor products for block selection, and copy-paste,…

Hi @thumuluru.shreya What problem are you trying to solve by doing this? That is, "why do this?" Knowing that may help the community to offer better suggestions. Until we know that... What you describe may become a brittle solution; it will require several rules to keep the Summary value accurate: * When an issue is…

Hi @Mohammed_Zeyad -- Welcome to the Atlassian Community! Please see this knowledgebase article which describes a rule for this scenario. For your case, you will need to change the JQL and fields used. https://support.atlassian.com/jira/kb/automation-to-send-a-single-email-to-assignee-when-multiple-issues-are-due/ Kind…

Hi @LPK You may use smart value, list filtering to do this: https://community.atlassian.com/forums/Automation-articles/Filtering-smart-value-lists/ba-p/1827588 The general approach uses conditional logic to filter by the issue type, and then a wrapped math expression to perform the count. This will be faster than using…

Yes, they will. You (as the admin) are configuring the fields / behavior and others will see the result of that configuration...the same as for other project types.

Please post an image of your entire rule and the audit log details showing the rule execution for more context. I hypothesize the rule is missing the Lookup Work Items action (formerly called Lookup Issues). Also, as different email apps have different levels of support for HTML, please update the markup used to match what…

Hi @Anna Luszcak -- Welcome to the Atlassian Community! Short answer: Not yet. Currently, you may use the REST API, and possibly multiple rules (i.e., one to create the folder and another triggered by that to add the page inside with the endpoint). I have not seen any updates in the weekly change blog for better folder…

Hi @Leanna Bremenkamp When building a table with dynamic rows for the lookup results, please try putting the iterator inside of the <table> ... </table> structure. For example <table> <tr> <th>Key</th> <th>Summary</th> <th>Status</th> <th>Assignee</th> </tr> {{#lookupIssues}} <tr> <td>{{key}}</td> <td>{{summary}}</td>…

At the right side of the log for those entries expand the details with the arrow > icon, and re-post the image. That will show the issues involved and possibly indicate why this is happening. For example, if the trigger issue is not an Idea, then you may not be finding the correct ones inside of the branch...leading to the…

UPDATE: Atlassian just posted an incident for this symptom... Customers may experience delays or failures receiving emails https://jira-software.status.atlassian.com/

Hi @Riccardo Bellitto -- Welcome to the Atlassian Community! For more context of this symptom, please provide the following: * what type of project is this: company-managed or team-managed * an image of your complete rule * an image of the send email action Kind regards, Bill

Hi @Anu Edirisuriya FYI for automation rules and created variables... I recommend not using any variable names which match built-in or custom field smart values. For examples in your rule, please see: priority and component. Those could confuse both the rule logic and people reading the rule trying to understand what they…

Hi @Daniel Schillig The diff() function takes date or date / time values: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-difference--- But, you have added the jiraDate format, which converts the values to text...preventing the diff() from working. Please try removing that…

Hi @Kiran Punjabi -- Welcome to the Atlassian Community! Adding to the suggestion from @Karan Sachdev ... * You could use a Scheduled Trigger automation rule, which runs every day, * And add a Smart Values Condition to compare that to the second business day of the month before proceeding. That date may be found using the…

Hi @Nguyen Thanh Tien The condition you show appears to use the plain text for the value: * smart values condition:* first value: {{comment.body}} * condition: contains * second value: Feedback NPS Score: That will work if the comment has a value as plain text or in a bullet markup format. Have you checked if there are any…

Hi @reza rouhafza If you read the documentation for the Issue Commented trigger, you will find it supplies an additional smart value for the specific comment involved: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Issue-commented Kind regards, Bill

Hi @Jorge Y. Mattheos Delgado There have been several questions about this symptom in the last couple of weeks...the Atlassian design team seems to be conducting an experiment to remove this feature with no way for customers to turn it back on themselves. As you are on a paid license, please work with your Jira Site Admin…

Hi @Phil Not with the built-in features of Jira. One would need a marketplace addon / app which extends the features of JQL (e.g., calculated fields), or add a custom field and use an automation rule to populate it daily. Kind regards, Bill

Hi @Latoya Broodie -- Welcome to the Atlassian Community! When the backlog is used with a Team-managed project, the work items must be specifically moved to the board from the backlog view. This is different from a Company-managed project where the status mapping to the board determines when an issue displays on the board.…

Thanks for that information! What is your role with the JPD project? I believe you need to be a Project Administrator to configure the fields to use Autofill.

Just so I understand...were you using a Created Variable rather than the field directly? If so, that explains the problem: Data Center's automation rules do not have the asNumber function yet (but Cloud does). With that function, you could have used ComplAverage.asNumber and it would have worked. Please consider marking…