Danut M _StonikByte_ Atlassian Partner

Hi @Luke Wirth, O solution would be to clear the Resolution field or not set it, unless the issue is really resolved. You can do this by altering the transitions fork your workflow. Another solution, would be to use a reported vs done gadget that does not use the resolution field. Our Great Gadgets app offers a gadget that…

Hi @Sara Volden, Is it about manual testing, performed by QA/testers as part of the issue workflow? If yes, you could simply extend your issue workflow with a status named "In Testing" and then add a new column to your Kanban board named in "In Testing" and map the newly added "In Testing" status to it. This way, your…

Hi @Michael Burns, This happens to me as well. Apparently, this report is not yet supported by the gadget in question. As an alternative to that, you could use a Cumulative Flow Diagram (CFD) gadget, like the one offered by our Great Gadgets app. This article might be of great help for you:…

Hi @Bikram Agarwal, There is an endpoint in the GreenHopper API, but unfortunately it doesn't work on Jira Cloud. Only works with Jira Server or Jira Data Center. /rest/greenhopper/1.0/rapid/charts/scopechangeburndownchart A better and simpler solution for you that will save you a lot of work would be the Sprint Burndown…

Hi @Sajal Mukherjee, I'm afraid that you cannot do this by using Jira's default reports or gadgets. But fortunately, this can be easily done by using the gadgets offered by our Great Gadgets app. Here is the complete solution. For example, you could configure the Cycle Time Control Chart gadget to calculate the cycle as…

Hi @Lalarukh Mukhtar, This can be easily done by using the gadgets offered by our Great Gadgets plugin. This display this info as numbers, your could use the Issue Filter Formula gadget, or the Advanced Issue Filter Formula gadget. This gadget allows you to display percentages and other metrics. All you need to do is…

Hi @Ashley Roberts, Try the Work Breakdown Structure (WBS) gadget offered by our Great Gadgets app. This gadget can display the issues from a filter / JQL in a tree structure, in form of Initiatives > Epics > Stories > Sub-Tasks along with their status. All you have to do is to configure this gadget to use a filter / JQL…

Hi @paul, Take a look over these gadgets offered by our Great Gadgets app. This will the ideal solution for you. For #1: Cycle Time Reports - this app offers 3 gadgets that allow you to track the cycle time in various ways: * Cycle Time Control Chart gadget - displays the issues by their cycle time, lead time or time…

Hi @Vincent Massa, This can be easily done, without being necessary to alter your agile board, by using the Sprint Burndown Burnup Chart gadget offered by our Great Gadgets app. This gadget allows you to set multiple statuses as done. So all you have to do would be to add your Passes QA status to the list, like this: And…

Hi @Victor Gutierrez, Another possible way to generate a velocity chart per team, would be to use the Kanban Velocity / Throughput Chart gadget offered by our Great Gadgets app. In this case, there is no need to create new boards for each team; all you have to do is to configure the gadget to use a filter or JQL that…

Hi @ravalman, As mentioned already, in Jira, only the last board column is considered as done. So one solution would be to map all the done statuses on that column, in the agile board's configuration. Obviously, this solution is not ideal, because it forces you to have a single "done"-category column on your board. But, if…

Hi @Suma Kustagi, Take also a look over these articles on how to create powerful dashboards for your Kanban team, as well as for the global release. * https://community.atlassian.com/t5/Jira-Software-articles/Building-a-powerful-Kanban-dashboard-in-Jira-with-Great-Gadgets/ba-p/1664331 *…

Hi @PokitPal Customer Support, This gadget looks at the Resolution field of the issues. Even if the issue was moved in a resolved status like Done or Resolved, if it does not have a resolution set, it will not be counted by the gadget. So make sure to set a resolution via workflow transitions or screens when issue is moved…

Hi @Kristina , An easy way would be to use the Advanced Issue Formula gadget offered by our Great Gadgets plugin to display the numbers on a Jira dashboard or Confluence page. This gadget can apply from simple (SUM, COUNT, AVERAGE, etc) to complex math formulas against the issues from up to 6 filters. Hope this helps.…

Hi @Susie Barber, Perhaps the sprint Start Date was a bit ahead, and those issues appears as being done before sprint Start Date. Look also at the table under the burndown chart from the report, to see what happens with those issues and the dates. Also, as an alternative to this report, you could try the Sprint Burndown…

Hi @David Rawlins, If you have our Great Gadgets app installed or if you consider it as an option, you could use the Team Wallboard gadget that it offers. This gadget displays the contents of an agile board. Due to the compact size of the cards displayed, it will show more issues than the Jira's board, so no need for…

Hi @Bryce L, This could be possible by accessing the link in the original email from Jira where she was asked to provide feedback. Entering a new score using the same link should overwrite the original score. Hope this helps. Danut 

Hi @Pineapple To determine the gadgets usage in your Jira Server / Data Center instance, you can run this SQL query on the Jira database: SELECT portletconfiguration.gadget_xml, portalpage.pagename, portalpage.id, portalpage.username FROM portletconfiguration INNER JOIN portalpage ON portletconfiguration.portalpage =…

Hi @Kelly Burns, Apparently your estimation method is not a "standard" one because those fields Estimated Working Days and Days Remaining are not the standard time fields of Jira. They look like two different custom fields (please correct me if I'm wrong) and I'm afraid that no Jira gadget/report or even a 3rd party add-on…

Hi @Isabella Musial, Please contact our support team at support@stonikbyte.com and someone will get in touch with you right-away. Thank you, Danut

Hi @송화영, This Jira gadget looks at the Resolution field of the issues. So, for an issue to be considered "done", it must have its Resolution field set. If you want a "Reported vs Done" gadget that looks at statuses instead of Resolution, then take a look…

Hi @George Abdo, If in the whole you have these values: 10, 1, 1, 1, 2 the average will be 15 / 3 = 5 But if in a group you have: 10, 2 => average is 12/2 = 6 Danut.

Hi @Isabella Musial, Counting sprints, most likely, will not be possible. But, if you have sprints of a fixed length, you could divide this by a number representing the number of sprints that fit in the 33 days (if your sprint has 2 weeks, you could divide by 3 instead of 33), thus obtaining a "per sprint" velocity instead…

Hi @George Abdo, Perhaps one of the module has some issues with a much higher age. And taken in the context of a module where are less issues than in your global filter, this increases the average. Be aware that there are alternatives to this gadget. Take a look over this…

Hi @Monica Ivanova, In this case, you will have to use COUNT formula (instead of SUM), which returns the number of items from the specified filter. No field will be necessary in this case. Variables a = COUNT of "Filter all tickets" b = COUNT of "Filter resolved tickets" Displayed data: a b b / a * 100 For further…

Hi @Todd, You mentioned the Issue Filter Formula gadget; this means that you have our Great Gadgets already installed. Be aware that our app offers some additional gadgets that will address your need. For example, the Cycle Time Trend Chart gadget will display the average time to resolution for your issues, grouped by time…

Hi @S Jena, You could have a project in JSM for every region and one for Global team. Or, you could have a single project in JSM for everything, and use the Component field or a custom field (like Team or Region) for assigning the ticket to a specific team. In this case, you will need filters for each team by that specific…

Hi @Peter Thomas, If an add-on could be an option for you, be aware that our Great Gadgets app offers a WIP Aging Chart gadget that displays the issues from a board by their age (time-in-column, or time-in-status, or time since creation, configurable at your choice). It works with any type of boards, is highly configurable…

Hi @Erica T_, You can do this type of calculation by using our Great Gadgets app. It offers an Advanced Issue Filter Formula gadget that can calculate math formulas base on the fields of the issue from up-to-six filters. The result is displayed on your Jira dashboard (or in Confluence). So you can use this for calculating…

Hi @omrili, If you consider a payed plugin as a possible option, try the Work Breakdown Structure gadget offered by our Great Gadgets app. This will display the issue in the structure that you want: Initiatives > Epics > Strories > SubTasks. All you have to do is to configure the gadget to use a filter or JQL that returns…