Danut M _StonikByte_ Atlassian Partner

Hi @Oscar Alfredo Chui Aguilar, Esto puede ser difícil de lograr sin una aplicación. Si cambias de opinión y quieres utilizar alguna aplicación, dímelo. Puedo recomendarte una aplicación que proporcione el informe que necesitas. Danut

Hi @João Correia, It is OK to use a single project, but you will need the Components or the Team custom field in Jira for assigning the tasks to each team. This field should be required/mandatory in Jira issue screen. You can use a single board to maintain the backlog, You could add Quick Filters to the board; a quick…

Hi @Nonla, I'm afraid that the Jira boards cannot be customized to display the entire hierarchy that you implemented. Try eventually the advanced planning features of Jira Premium: Advanced planning guide in Jira Also, for reporting purposes, a possible option would be to use an app from Atlassian Marketplace. If you…

Hi @Colleen Stone, Jira does not have a native velocity dashboard gadget. You could eventually try the Velocity report, instead of a gadget. If you prefer a gadget, you could search on Atlassian Marketplace for an app (plugin) that provides a velocity gadget. In case you decide to use or try an app, our Great Gadgets…

Hi @Gregory, As far as I know, on Cloud, the sprint reports data are not available via REST API; this works only on Server & Data Center, but not on Cloud. But why not using the Sprint Health Gadget of Jira? I think it exposes all the info you need. Danut.

Hi @Eran Roiter, You could use two Jira gadgets side-by-side. I would recommend the Issue statistics gadget (the Two Dimensional Filter Statistics gadget could be also an option), configured with a filter that returns the issues from each quarter. But if you need something more advanced and easier to configure, you could…

Hi @akhilaa.susheela, Indeed, the Jira's burndown chart drops only when the issue is moved to Done (last column of board). Apparently it does not count the amount of work logged; when the issue is marked done it drops with the amount of time set at Original Estimate. It behaves as in the case of story points, the only…

Hi @Petru Simion _Simitech Ltd__, Not per issue type, but in this case you can use the available options for status categories. To measure Lead Time (from creation to resolution) you should set: Cycle starts: When the issue was created Cycle ends: When the issue entered a status that has category Done Category "Done" means…

Salut Petru, Not sure if you got the chance to look over our Great Gadgets app. It offers some gadgets that lets you measure Cycle Time, Lead Time or time between two different stages/statuses of the workflow, as well as the Time in Status. These gadgets offer full flexibility in setting-up the start / end of the cycle. So…

Hi @Beatrice Cudd, This is not possible with the Jira's default reports or gadgets. A solution would be to search for an app (plugin) on Atlassian Marketplace that is capable to generate such diagram. If you are willing to use a plugin, our Great Gadgets app offers a Cumulative Flow Diagram gadget that can be configured to…

Hi @Danilo Simic, If by "vendor management" you mean also tracking metrics specific to that "vendor", our Great Gadgets app might be the perfect choice. Have a look over this article to make an idea: An effective dashboard for Service Desk and Customer Support teams in Jira Service Management Danut.

Hi @Helen Snowball, That gadget seems to be introduced by Xray app. So maybe it could be a good idea to ask the Xray Support Team about this. I am not familiar with Xray, but if this app stores its data in Jira in form of issues, custom fields, etc, you might be able to achieve what you want by using the Pivot Table &…

Hi @Kaladin Stormblessed, I'm afraid there is no good and easy way to determine this with Jira reports. Try looking on the Sprint report, Burnup Chart report and Burndown Chart report as these might help in some extent. Otherwise, a solution would be to search on Atlassian Marketplace for an app (plugin) that offers a…

Hi @[deleted], Jira reports cannot be added to dashboards because the Jira dashboards use gadgets. There is no one-to-one parity between reports and gadgets, but there are some gadgets )(like Burndown Chart) that show similar info like the reports, but in a more compact manner. Unfortunately Jira does not have a Cumulative…

Hi @Vera Valshonok, The solution offered by @Jack Brickey is great, being based on the Jira native's functionality, but if an issue is resolved and after a while is reopened and resolved again, the calculated time will also include the time the issue stayed in the first resolved status... For more accurate data, you could…

Hi @Wattson Helpdesk, As mentioned by @Dan Breyen, the Organization field is not supported by the Jira's gadgets. A possible solution would be to search on Atlassian Marketplace for a plugin that offers gadgets with support for Organization field. If you consider the idea of using a plugin, our Great Gadgets app offers a…

Hi @Vera Valshonok, Take a look over the Jira's native gadget Filter Counts. With the appropriate JQLs you could display the counts for previous month and current month, for example. If you need something more advanced, my advice is to look for a plugin on Atlassian Marketplace that offers a report of gadget that is…

Hi @Fox Campbell, Instead of that report, you could also try using some dashboard gadgets. Jira offers two native gadgets that can be helpful: Created vs. Resolved Chart gadget and Recently Created Chart gadget. But, both might not work properly if your resolved issues does not have the Resolution field set. If you need…

Hi @Mathew Kuruvilla, Do you need this report based on the time logged by the users, or by the time the issue stayed in each status (time between the the moment the issue entered in a status and the time that issue exited the status)? In both cases you will need a 3rd party app, so my advice is to search on Atlassian…

Hi @Admova, Welcome to the Atlassian Community! Unfortunately this cannot be achieve by using Jira's native gadgets. A possible solution would be to search on Atlassian Marketplace for a plugin that offers gadgets capable to do this type of calculations. If you are willing to use a plugin, then our Great Gadgets app could…

Hi @Jyoti Singh, I'm afraid that this is not possible to do with Jira's native reports or gadgets. My advice is to search on Atlassian Marketplace for a plugin that offers a report or dashboard gadget that supports this type of calculations. If you consider the idea of using a plugin, our Great Gadgets app offers a Pivot…

Hi @Vera Valshonok, Unfortunately this cannot be done by using Jira's default reports or dashboard gadgets. My advice is to search on Atlassian Marketplace for a plugin that offers such functionality in form of Jira report or dashboard gadget. If you consider the idea of using a plugin, our Great Gadgets app offers a Time…

Hi @Bob Bandsuh, Jira does not have a native Cumulative Flow Diagram gadget. A solution would be to search on Atlassian Marketplace for an app that provides such gadget. If you consider the idea of using a plugin, our Great Gadgets app offers all you need for creating a dashboard like the one you mentioned. 1. Cumulative…

Hi @Rafał Skrzeczkowski, Indeed, with the Jira's default gadgets it might not be possible to achieve this. But there are many apps on Atlassian Marketplace that offers gadgets that can help you display the info you want, including YTY statistics. So why not considering the idea of using an app/plugin? An example of such…

Hi @Shyamal Ghosh, My advice is to use Jira dashboards instead of reports for this purpose. They have the advantage of being highly customizable and displaying all project metrics in one central place, easily accessible by anyone interested. Using native Jira gadgets in combination with gadgets introduced by apps/plugins…

Hi @Rodrigo Coutinho, The Jira Velocity report only displays the commitment at the start of the sprint. So it will not reflect the commitment if you added stories right after the sprint start. An option, other than re-creating the sprint, would be to search on Atlassian Marketplace for an app that is able to display the…

Hi @Raj, Your end-goal is to have the epic progress displayed on the Jira dashboards. Not sure if this can be easily done by using automation. My advice is to search on Atlassian Marketplace for an app that provides dashboard gadgets capable to do this automatically (with no administrative work). An example of app capable…

Hi @Parto Hamidi, You cannot use the board name in JQL filters. But, you can use the board's filter name in your JQL, which produces exactly the results that you expect. Here is how: * Identify the filter of your Data Migration board, from Board Configuration > General tab * Then update your JQL to use the filter, instead…

Hi @Marija Simic, I'm afraid that there is no way to do this in Jira. You could try the Control Chart report, but I am not sure if it will fully fill your needs. A potential solution would be to search on Atlassian Marketplace for an app that provides this info. If you consider the option of using an app, our Great Gadgets…

Hi @Sean Blezard, Have you already tried the Cumulative Flow Diagram report of Jira? If not, take a look. If you need something better, then my advice for you is to search on Atlassian Marketplace for an app that provides a better report or a gadget that is capable to provide the info you want. If you consider the idea of…