Danut M _StonikByte_ Atlassian Partner

Hi @Smitha Joseph, First of all QA and DEV should not estimate separately - this is still the old mindset from waterfall. You have to estimate the size of story relative to a base story, considering the entire effort DEV + QA. But this is another discussion... If the estimation is between two Fibonacci numbers, go with the…

Hi @balan, #1 Create a filter in Jira that returns the issue created or updated in last 6 months: created >= startofday(-6M) or updated >= startofday(-6M) Then configure the Issue Statistics gadget of Jira to use this filter and display statistic type by Project. As a result, you will get the list of projects used in last…

Hi @Mike Oragwa, This article might be of great help for you: https://community.atlassian.com/t5/App-Central/An-effective-dashboard-for-Service-Desk-and-Customer-Support/ba-p/2360369 As you will see with the Kanban Velocity / Through gadget offered our Great Gadgets app you can track the velocity of your team, in term of…

Hi @Prajakta Marotkar, An easy way to visualize the aging of tickets is by using the WIP Aging Chart gadget offered by our Great Gadgets app. This gadget can display the tickets from the columns of an agile board or filter (horizontal axis) by their age (vertical axis). Hovering an issue in the chart will give you details…

Hi @Rathnayake, Malshani, Jira's Filter Results gadget is the best option for what you're looking for. Take also a look over this article on how to improve your JSM dashboards: https://community.atlassian.com/t5/App-Central/An-effective-dashboard-for-Service-Desk-and-Customer-Support/ba-p/2360369 Danut. 

Hi @Chris Leonidas, I would suggest creating a Jira dashboard with all the necessary gadgets for tracking the metrics you mentioned. And then share that dashboard link with the project stakeholders or export it in PDF. The advantage of using dashboards is that they are highly customizable and let's you centralize the info…

Hi @Sindhu, I think that what you want can be easily achieved by using the Filter Results gadget of Jira. All you have to do is to configure it with a filter that returns that issues from the sprint(s) that you want to track. Something like this: sprint = "Sprint 1" or sprint IN ("Sprint 1", "Sprint 2") And then to display…

Hi @Oliver Stutz, A better alternative to limited Burndown Insights chart of Jira is the Sprint Burndown Burnup Chart gadget offered by our Great Gadgets app. This gadget works with any type of estimates: story points, time estimates or any numerical field. So you will be able to select Story Points even if you are in team…

Hi @Dheera Chaturvedi, My advice is to create a dashboard in Jira with all the necessary gadgets in-place and then share it with the executives. Dashboards are highly customizeble comparing with reports and have the advantage that you will have everything centralized in one-single page. Our Great Gadgets app offers all the…

Hi @Santosh Narayanan, Jira offers some useful gadgets, like Issue Statistics gadget, Two Dimensional Filter gadget or Pie Chart. These are good to display metrics in term of number of issues from a filter. Complementary to these gadgets are Issue Filter Formula gadget, Advanced Issue Filter Formula or Pivot Table & Pivot…

Hi @Smitha Joseph, This is not possible with the Jira native gadgets; its sprint burn-down gadget displays only the active sprint. But you can easily do this by using the Sprint Burdown Burnup Chart gadget offered by our offered by our Great Gadgets app, which allows you to select any past sprint. This is how the gadget…

Hi @Floreana Di Trapani, I just checked on my test system and those options don't seem to be available on Cloud. The article you mentioned is for Data Center, not for Cloud... But, instead of this limited report, you could try the velocity gadgets offered by our Great Gadgets app. The Team Velocity gadget let's you select…

Hi @Luke Niccolls, A good solution for you would be the Work Breakdown Structure (WBS) gadget offered by our Great Gadgets app. This gadget displays the issues from a filter or JQL by their hierarchy: Epic > Story, Task, Bug > Sub-task along with their status. All you have to do is to configure the gadget with a JQL that…

Hi @sumaiya.parkar, Not sure if you will find a bar chart for this, even with addons. But, if this helps, you can have this as an actual number displayed on your dashboard, in real time. By using the Advanced Issue Filter Formula gadget offered by our Great Gadgets app, you can easily calculate and display this metric.…

Hi @Amanda Hoyt, The article that you mentioned is applicable to Jira Service Management. I can confirm that the "New report" option is only available to service management projects. But instead of a custom report, I strongly recommend creating custom dashboards. Dashboards are highly customizable, shareable, and you can…

Hi @cdparmeter, The reports are specific to each board, so they should not depend on the parent board. Please double check. If you don't manage to figure it out, be aware that a possible solution would to use the burndown charts offered by our Great Gadgets app. The app offers sprint burndown/burnup, release…

Hi @Tatyana, The main difference in my opinion is that Epic > Story is at a higher level than Story > Sub-tasks, which means that Epic > Story is meant for defining, planning and tracking the work to do (at a higher level), while Story > Sub-task is for planning/executing the work within a story (at micro level). Some…

Hi @Jon, Our Project Team app allows you to create advanced user profiles by adding user custom fields of various types. With this app you will be able to add all the fields that you mentioned. You could start with 1-month free trial. If you have any questions, feel free to contact us at support@stonikbyte.com. Hope this…

Hi @Nacho Cortes, What you actually need is a team velocity chart that displays all these number of you. Unfortunately Jira does not offer a velocity gadget. Our Great Gadgets app offers all you need to track these numbers, as well as many other metrics. The Velocity Chart gadget offered by our app lets you visualize the…

Hi @Josep Romera Andreu, The Jira reports show a limited number of sprints. Be aware that a better alternative to these limited reports is our Great Gadgets app, which allows you to visualize all the past sprints. It includes many useful gadgets, but especially these two will solve your problem: Sprint Burndown Burnup…

Hi @Selva Praveen Elango, This can be easily achieved by using the Advanced Issue Filter Formula gadget offered by our Great Gadgets app. This gadget applies math formulas on the fields of the issues from up-to six filters and displays the result as number(s) on your dashboard. If you configure the gadget like this: ...…

@Lucas Ferreira Yes, you are right. But I'm afraid that this cannot be achieved by a JQL. The JQL always returns the current story points; you actually need the story points at the start of the sprint, which is not possible with JQL. For this type of info you could use gadgets like Team Velocity or Sprint Burndown Burnup…

Hi @Lucas Ferreira, If you need historical data (for past sprints) use the Team Velocity gadget; it does not require a JQL, you just select the board instead. If you want these numbers for current sprint, try something like this: For committed (actually, current scope) - you need a JQL that returns all the issues from the…

Hi @Anuj Kumar, This can easily done with the Pivot Table & Pivot Chart gadget offered by our Great Gadgets app. You just have to configure the gadget with a JQL that returns the issues from your epics: parentEpic IN (DEMO-1, DEMO-2), display the pivot table by Status Category and Epic Link fields and calculate by…

Hi @Bryan Urias, This seems complicated and requires a lot of work. Just be aware that this can easily done with the Pivot Table & Pivot Chart gadget offered by our Great Gadgets app, without any manual work and complicated settings like the ones in that article! You just have to configure the gadget with a JQL that…

Hi @Ali Raza, Such report can be easily generated by using the WIP Aging Chart gadget offered by our Great Gadgets app. This gadget displays the issues in real time by their age (hours or days in board column). The gadget offers a Data tab with a detailed report that can be easily exported in CSV format so you can open it…

Hi @Christian Jordan, Have a look over this article as it might be of great help to you: https://community.atlassian.com/t5/App-Central/An-effective-dashboard-for-Service-Desk-and-Customer-Support/ba-p/2360369 As you will see, our Great Gadgets app gives you all you need for tracking cycle time, lead time and age directly…

Hi @Theresa, One way is to use the Filter Results gadget of Jira to display the issue you want. But for this you'll need to create filter that returns the issues to display with a JQL like this: project in (Project1, Project 2, Project 3) AND "Start date[Date]" > "2024/06/17" AND "Start date[Date]" < "2024/06/21" Another…

Hi @Qin Chen, In Jira this is possible only with company-managed projects; the team managed projects do not support this. So one option would be to switch to company managed projects. A solution for displaying priority on a team-managed project board, would be to use the Team Wallboard gadget offered by our Great Gadgets…

Hi @Lucas Ferreira, Yes. Both gadgets can calculate the SUM of Story Points for the issues in a filter. The Advanced Issue Filter Formula Gadgets allows you to calculate percentages for issues in multiple filters. For percentages like the one you mentioned, you could also use the Pivot Table & Pivot Chart gadget and…