Bill Sheboy Expert

Hi @Michael BESSAN -- Welcome to the Atlassian Community! I believe that is Atlassian's interpretation of a control chart, and here is the documentation link for it for Server/Data Center version of Jira: https://confluence.atlassian.com/jirasoftwareserver/control-chart-938845628.html It should be available as a built-in…

Ping...any word back from the DC/Server team if there are plans to support this feature for automation? Thanks!

After a re-read of that article (emphasis is mine below), please note this function targets Jira Service Desk: You can now play around with timestamp fields by adjusting fields at hour level. For that, you have two new functions in your pocket: plusBusinessHours and minusBusinessHours. We wanted to take business hours…

Hi @Pedro Hernandes If that does not fix it with the suggestion from @Alex Koxaras -Relational- please try this: * after the action for LookupIssues, add an action to write to the audit log with the number of issues returned: Number of issues returned = {{lookupIssues.size|0}} * post an image of your audit log from trying…

Hi @Brian Pelton That is curious, and I suspect you are correct about time zone and the hours/day and days/week setting impacting this. You could try to force to your time zone first and see what happens, such as this using the reporter as the "anchor" time zone. Perhaps log both with and without the increment to see what…

Hi @Deepanshu Natani You need some way to uniquely identify the task, and then use a scheduled trigger rule to find it. For example, let's assume you always created this task with the summary "Our Team Weekly Task". Your scheduled trigger could use JQL to find an open task with that summary, and then close it. A more…

Hi @Kyle Keefer Yes, that is possible, and... Automation for Jira for the server version is an addon, and there is a free (Lite) version and a paid (pro) version. Please discuss with your site/instance admin which option may be available. Here is some documentation on automation to help: *…

Hi Garry, For a company-managed project, you have a few options... * use a quick filter is a fast way to show/hide the values * adjust the "Hide completed issues older than" setting to drop the older stuff * adjust the "Kanban board sub-filter" to have more control over what is displayed. This filter layers on top of the…

Hi Alex, As you note about performance and usage limits, I wonder: how often do you need this information updated? Just-in-time updates are awesome when the benefit justifies the cost. If you could live with accuracy of perhaps once-per-day, the rule could be converted to use a scheduled trigger. And the rule could be…

Hi Erin, For testing cues, we put information in the imported issues' summary and description. For example when we made rules to measure process times and Age of WIP, the summary helped the tester know which status values to pull an issue into (and the order) from the board. The description contained what we expected to…

Hi @Erin Quick-Laughlin Change management is definitely an area to improve automation rules, and here are a couple of backlog items along those lines. They are in the Code Barrel backlog, so unfortunately we cannot vote for them. * Support for rule configuration versions https://codebarrel.atlassian.net/browse/AUT-471 *…

Hi @Pedro Hernandes Adding on to what Alex suggests and your automation rule image: As implemented with the scheduled trigger with JQL, this will post a message for each issue found. If you would prefer one message with the list of issues, consider using: * a scheduled trigger with no JQL * the LookupIssues action with…

Hi @Brendan Gray Would you please describe: * how your team is working (waterfall, Scrum, Kanban, something else); * which features of Jira you are using (company-managed projects, team-managed, roadmaps, addons, time keeping, estimation, etc.); and * what you mean by "behind schedule" or "ahead". For example, is the idea…

Hi @Vignesh Jayagopal One way to do this with built-in Jira features is with a scheduled automation rule in a project, although it could get a bit more complicated if you need many of the issue fields. If you only need a few details, you could use the LookupIssues action with JQL, gather the results in a created variable,…

Hi @Olivier Mollies In addition to what Alex and Jack are suggesting... Smart values are case-sensitive, so ensure that your value matches the capitalization of your custom field. When that still does not work, you may reference the field by its custom Field ID value. To find that, please use the information in this how-to…

Hi @Ganesh Adding to what @Piotr Zadrożny _Eyzee_ suggests for automation: when needed, you could modify/add to the existing description rather than only setting the value when it is currently empty. For example, you could set the value with: {{issue.description}} Some added information Best regards, Bill

Awesome! I am glad to hear that helped. __Bill

Hi @Administrador Mesa de Servicios -- Welcome to the Atlassian Community! You appear to be using the free Jira Cloud license. Is that correct? If so, the the cloud version is continually being updated to the "latest" version, and the only differences are as the updates are propagated throughout Atlassian's cloud…

Hi @joe stewart Please see Time Tracking Admin to configure the settings for working hours/day and working days/week: https://support.atlassian.com/jira-cloud-administration/docs/configure-time-tracking/ Of note, this is a system-level change, not for just one project. Best regards, Bill

Hi @Ryan Freckleton -- Welcome to the Atlassian Community! Full disclosure that I am not currently using any webhooks with our instance, and here is some information I found that might help you: * REST API call to find the failed webhook…

Hi @Kyle There is an open suggestion to find users by name from within an automation rule: https://codebarrel.atlassian.net/browse/AUT-725 As a work-around (albeit a slower one) you could use a webrequest to call the REST API with a user search to get the account ID, and use that for assignment. Here are some references if…

Thanks for that additional information, Piotr. If you are using Company-Managed (CMP) and Team-Managed Projects (TMP) that you want together, consider creating an independent CMP to host the aggregate board. TMP has enough issues with field and status replication that you may need the extra CMP features to manage it, such…

Thanks for clarifying, @alia.burale I'm not certain there are any "best practices": perhaps only better and "worser" ones, as teams learn, experiment, and improve. :^) I noted dashboards, and there are also built-in Jira boards to use with multiple projects, roadmaps, and some calendar views. If you look at the marketplace…

Hi @Aaron Pieros Whatever approach you choose for automatically purging old information from Jira and JSM Cloud, I suggest you investigate, build out, and test a backup/restore capability first. That will provide some protection against errors in your purge process. For more information, please look…

Hi @sheikh-spear Atlassian has several sources to help the community add your own gadgets, including a developer community. Please take a look at these sources: * https://developer.atlassian.com/cloud/jira/platform/extending-the-user-interface-with-connect/ *…

Hi @Colleen -- Welcome to the Atlassian Community! For automation-related questions, it may help to post images of your rule and the audit log. That will provide the community context to offer ideas. Would you please add that to your question? Thanks! And...that audit log error may indicate custom fields are either missing…

Hi @Lewis Cook To be clear, is your scenario that there was a Story Point value and it was later cleared? If so, I recall a couple of open defects related to JQL (and so probably the API) for that scenario where the empty logic isn't quite correct yet. My suggestions: * get this to work however you can (e.g. if/else), and…

Hi @Shams What problem are you trying to solve with automatic time tracking? If this is an issue of reducing repetitive tasks, please investigate the built-in Automation for Jira rules. Such automation rules would allow you to log time based upon status changes, as you note in your use case. To learn more about this…

Hi @sudarshan Please consider reviewing the following for more information: https://scrumguides.org/scrum-guide.html#daily-scrum Best regards, Bill

For this specific sprint with the problem: if you believe completed count is correct, review that with the team to help with future planning... One value to get from this is to ensure your planning is completed before starting the sprint...including checking the start/end values for the sprint configuration.