Bill Sheboy Expert

Hi @Lori Milam Do your six different rules all have the same trigger on the Request Participants field? Specifically, are the trigger options for "Change Type" and "For [issue operations]" the same? This may be the cause if they are not triggering consistently. If that is not the cause...reviewing the audit logs for the…

Thanks for those images! The problem is someone removed (or did not add) the Story Point Estimate field for the issue types involved. To solve this as a Project Admin: * from the left side navigation, select Project Settings * select Issue Types * for each type you want the Story Point Estimates to be available...* select…

In my testing, round-robin uses information associated to the last date / time the rule was updated / published. After that point, the "counter" in the list starts and this allows the re-assignment to work for this scenario. If you update / publish the rule later, the "counter" resets and starts again on the list of users…

Hi @Francois Turcotte What method of assignment are you using? If you are using round-robin, one workaround for this scenario is to check the assignee and re-assign. For example: * trigger: issue transitions to "code review" * action: assign issue, from a group with round-robin * action: re-fetch issue * smart value…

Hi @Adrian Avalos Are you using a Jira Automation rule to do this? If so...I recommend implementing this incrementally: Your rule could use the Lookup Issues action with JQL containing an ORDER BY clause to order the issues: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues Then…

For my test site with Free license, that message seems paired to the "Smart Replies" feature. I recommend disabling all the "lab" features, logging out, clear your browser cache, close all the browsers, and open / login to see if it vanishes.

Hi @Joris Huisman -- Welcome to the Atlassian Community! The message does not indicate the smart value is not supported. What is means is for the current context in the rule, the smart value is not available. The branch-related smart values are only available with the branch-related, rule triggers:…

Hi @József Porohnavec -- Welcome to the Atlassian Community! Updating issues and using a Re-fetch Issue action within any branch which could be on more than one issue may not help / work. The reason is such branches execute in parallel and asynchronously. As a result, edits could collide, have errors, and lead to…

That v2 one still works for me for an example project, as you have called it. Have you tried using a different user's credentials (or API token)? And...you may have noticed that v2 endpoint is deprecated: https://developer.atlassian.com/cloud/jira/platform/changelog/#CHANGE-1304 And so with the new one, I suspect each…

Thanks for the additional information, Jennie. My short answer is: I think you would still need a marketplace app (or external tool) to report this. Let's start with "committed" and "completed". Because Jira has some accuracy problems with the issue changelog regarding the Sprint field, and anyone could add / remove issues…

Thanks for the rule image and additional information. And, I am using Jira Cloud, not Data Center, so please test any changes I suggest. The Issue Created trigger can fire so quickly it may not yet have all data for the issue. I recommend adding the Re-fetch Issue action immediately after that trigger. This will slow the…

Hi @Harry Sanders -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this? That is, "why do this"? Knowing this may help the community to offer better suggestions. A team using agile methods, particularly Scrum, would share responsibility and accountability for the work and value they plan…

Hi @Angela Terilli There has been quite a lot of "spirited conversation" about this questionable feature, which Atlassian is calling "Smart Replies": https://community.atlassian.com/t5/Jira-articles/Jira-now-offers-smart-replies-in-issues/ba-p/2804797 Here is the suggestion to configure it or turn it off for a…

Here is the suggestion to make this "feature" configurable or to disable it completely for a site: https://jira.atlassian.com/browse/JSWCLOUD-27235

Hi @steven.allcock What have you tried thus far to solve this need? Have you tried using AQL to identify the specific objects? If so, you could then use a scheduled trigger rule and the Lookup Objects action to find them to query further, and then create the Jira issue when needed. Kind regards, Bill

Hi @Tehmina Aslam First thing, in your Edit Issue Fields action you are trying to update the field two ways: with the field dropdown and with JSON. Only one of those may be used at a time for a specific field, so remove one of them. Next, there are errors in your math expression: it is missing the precision for the ROUND()…

Hi @ashkarrahman -- Welcome to the Atlassian Community! What have you done thus far to solve this need? If you have an automation rule that is not working as expected, please post the following so the community can provide suggestions: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image…

Hi @Edouard Parison JPD uses its own date format, providing a date range. If that was shown in a Confluence page view, it would appear like this: {"start":"2024-07-01","end":"2024-07-01"} Any built-in, global / company-managed fields will appear as a single date value. For example, the Created and Updated fields.…

Hi @Brian Hennessey Are you asking "can the issues be re-ranked when the due date changes"? If so, the answer depends upon what other features you want to use with Jira... If you do not need the drag-and-drop feature to re-order issues, the board's filter could be updated to change the ORDER BY clause to include due date.…

Hi @Alex Dokhtiar When an issue is created in a status other than the first in the workflow, it does that in two steps: * create the issue * transition the issue This can be observed in the issue history. Do you have two rules, where one is triggered on Issue Created and another is on Issue Transitioned? If so, for this…

Hi @Seenivasan K -- Welcome to the Atlassian Community! What have you done thus far to solve this need? If you have an automation rule that is not working as expected, please post the following so the community can provide suggestions: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image…

Hi @John Funk I definitely recommend testing the smart values with forms in other project types before spreading the word too much ;^) In the Atlassian team's community post announcing this, I recall specifically asking them if this applied to automation in other project types. The responder said something to the effect…

Hi @Eoin Thank you for this information. As this feature deploys to additional project types, how will the performance issues with cover images be addressed so boards are not impacted? Please see the defect on this symptom here: https://jira.atlassian.com/browse/JSWCLOUD-25553 Kind regards, Bill

Hi @Raman Verma -- Welcome to the Atlassian Community! Please post images of the screen and errors you see for the team-managed project when: * updating the story point estimate in the backlog view * creating a new issue and setting the story point estimate Until we see those images for context... For a team-managed…

Hi @Jennifer Neusch Most of the built-in reports / dashboard gadgets in Jira are based on issues, and the built-in Scrum reports roll up at the sprint level. Where would you store information in Jira and generate the reporting for what you describe? For example, Entity Properties in the Project, or App Properties in the…

Hi @Ismael -- Welcome to the Atlassian Community! Adding to Trudy's answer... If you want to sum a custom field and save the result in another issue, you cannot use the Lookup Issues action; that action does not support custom fields for the Data Center version of automation rules…

Hi @Tiffany Miller -- Welcome to the Atlassian Community! Referring to your other question, to remove the task the page content would need to be updated using the REST API endpoint. That is likely to be difficult as it would need to parse and then remove the specific action item. An alternative is to use the Task Report…

Hi @Dwight Holman I believe this is still only possible with marketplace apps / addons. Here are the relevant suggestions to make this type of searching available by JQL or the REST API: https://jira.atlassian.com/browse/JRACLOUD-28064 https://jira.atlassian.com/browse/JRACLOUD-67454 It is possible to find issues for a…

Hi @LUIS MIGUEL DAZA MENDOZA -- Welcome to the Atlassian Community! Short answer: it is not possible to check that for any, non-specific timeframe using the built-in JQL. You could investigate marketplace addons / app to help with such queries. Using the JQL CHANGED operator, one could check within a specific timeframe,…

Hi @Alexander Ziegltrum Short answer: I recommend not trying this scenario with a Jira Automation rule. First thing, I respectfully and strongly discourage having a rule that could potentially impact the group assignments for hundreds of Jira users. There is too much risk of a simple mistake that may be difficult to…