Danut M _StonikByte_ Atlassian Partner

Hi @Charlene Freeman, Jira does not offer a burndown chart for Kanban. Your best option here is our Great Gadgets app, which offers a Release Burdown Burnup Chart gadget that allows you to create a burn-down chart for you Kanban team with a few clicks. All you have to do is to configure this gadget to use a filter / JQL…

Hi @Ramu, Confluence does not have a native Burndown Chart macro, but you can import the gadgets from Jira as macros in Confluence, including the Jira's Sprint Burdown gadget. This requires some administrative work in Confluence, see Registering External Gadgets. For advanced burdown/burnup charts take a look over the…

Hi @Selena Farris, You could use the gadgets offered by our Great Gadgets app to display the sum of Kanban Points for your board. Issue Filter Formula gadget Advanced Issue Filter Formula gadget There are some other gadgets offered by the same app, that could help you with this, for example the Cumulative Flow Diagram…

Hi @ataranenko, If this happen in Jira Cloud, please try re-install the app by following these steps. All the existing app data will be preserved. * Go to Apps > Manage Apps * Click “Settings“ on the bottom of the page (under the apps list). * Check both option options Enable private listing and Enable Development Mode…

Hi @Garn, Your best option here is our Great Gadgets app. It offers a Cumulative Flow Diagram Chart gadget that can calculate data by Story Points, exactly as you want. See more about this gadget and the many others offered by this app in this…

Hi @Centro de Excelecia TI, There are better and easier ways to track the time between statuses or the age of the issues, as well as highlighting and easily identifying the issues that took/take longer than expected. This article might be of great help for you:…

Hi @Jatin Jalwan, There might be multiple causes here. Which line is flat, more exactly? Some screenshots would be useful. You could also try building a powerful dashboard for your Scrum projects by using the gadgets offered by our Great Gadgets app. See this…

Hi @noa einhorn, First , create a filter that includes the issues from all projects. Then, create a board based from this filter. My advice is to create a cross-projects dashboard in Jira, with all the necessary gadgets that use this newly created filter or board, for tracking your projects globally. This article provides…

Hi @noa einhorn, You could create a dashboard in Jira for each project, with all the necessary gadgets in place. This way, you will have the project status in real time. This article shows how to create an "Release Overall" (or Project Overall) status dashboard for one…

Hi @이정인, Not sure if this Jira report can be configured or adjusted in any way. But, if a payed add-on can be an option for you, you could try the Sprint Burndown Burnup Chart gadget offered by our Great Gadgets app, which has an option for excluding the weekends. Thank you, Danut Manda

Hi @Márcia Croce, You best option here would be our Great Gadgets app. It offers a Cycle Time Control Chart gadget that you can easily configure to display the Lead Time Scatter Plot that you are looking for. And everything will be in real time, without any manual work. The gadget can be used in both Jira and Confluence.…

Hi @Tony Mansour, The solution is to add swim-lanes in your board configuration. If you want your Kanban board displayed on a dashboard or in a Confluence page, you could use the Team Wallboard gadget offered by our Great Gadgets app, which has an option to display swim-lanes by priories. See…

Hi @김상현, A solution to this would be our Great Gadgets app, which offers Sprint Burdown Burnup Chart gadget, Release Burdown Burnup Chart gadget as well as Team Velocity Chart gadget that have an option to include the sub-tasks in the calculation. So, a complete solution that will solve your problem. The gadget offers a…

Hi @srmrunner, If you manage to create a filter / JQL that returns the issues from your Feature and then you configure the gadget to use the filter / JQL, it should work. Try a JQL like this... parentEpic IN (FEATURE-1) ... where FEATURE-1 is the ID of the Feature that you want to track. Danut.

Hi @Nick Nader, Check the configuration of your agile board and make sure that the "Done" status is mapped on the last column of the board. Jira considers the issues as done, if they are in the last board's column. If this does not help, you could also try our Great Gadgets app, which offers advanced burndown/burnup charts…

Hi @Christine Aucoin, For 1st point, to get issues from the next sprint, try this JQL query: filter="The name of the filter of your agile board" AND sprint in futureSprints() Sorry, not sure about the second one... Danut.

Hi @Dan Driscoll, Thanks for contacting our support! It turned out that the issue in question was specific to your Jira instance and a workaround was applied successfully. Danut

Hi @Harry Layton, This looks like a burnup chart with forecast by Maturity field. Such a chart can be easily generated in Jira by using the Release Burndown Burnup Chart gadget offered by our Great Gadgets app. It supports calculation not only by Story Points, issue count, etc but also by any numerical custom fields. If…

Hi @srmrunner, You can easily create an epic burndown/burnup chart by using the Release Burndown Burnup Chart gadget offered by our Great Gadgets app. No manual work in Excel is necessary, you will have the chart displayed with a few clicks! All you have to do is to configure the gadget to use a filter or JQL that returns…

Hi @Mathieu Hebbrecht, You best option here would be our Great Gadgets app. It offers all the gadgets you need for tracking you project by any numerical custom field. With a few clicks you will get: Sprint Burndown Burnup Chart gadget Release Burndown Burnup Chart gadget Besides these great burndown charts you'll get Team…

Hi @Bijal Shah, Your request looks like a "corner case". I'm afraid that you will not find such a chart that will fully-fill your requirements. But something helpful could be the Team Velocity Chart gadget offered by our Great Gadgets app. This shows: - Initial Scope - the total Original Estimate at the start of sprint -…

Hi @Doug Schmidt , Try using the Filter Statistics gadget of Jira. It will display the number of issues (count) for each label. All you have to do is to configure it to use a filter that returns the issues from the 3 projects and to display statistic by Labels field. If you want a "per-project" labels statistic, then use…

Hi @Robert Campbell, Jira does not have a gadget that allows you to calculate percentages in the way you want. But a good solution could be the Advanced Issue Filter Formula gadget offered by our Great Gadgets app. With this gadget you can calculate the count of stories, sum of their estimate and percentage of work done…

Hi @Jeff Murray, The Kanban boards display the number of days in column. This is enabled by default, but apparently this info is only displayed for the issues that are in that column for more than 1 day. See https://support.atlassian.com/jira-software-cloud/docs/customize-cards/#Using-Days-in-column. Another easy way to…

Hi @James Gould, I could offer these details in a private discussion. Perhaps the via the LinkedIn chat. Please sent me an invite. Danut Manda

Hi @James Gould, To integrate the testers in the process, we have a testing column on the team board. So our board has these columns: BACKLOG | IN PROGRESS | IN TESTING | DONE Then, we ensure that the user stories are small enough in order to be fully worked in a sprint (developed, tested, and bug-fixed). So make sure that…

Hi @James Gould, It uses Jira's issue hierarchy (Epics > Tasks, Stories > Sub-tasks). But if you also have the Atlassian's Advanced Roadmaps app installed in your Jira instance, it displays the extra levels (Initiatives) added with this app on top of the Epic level. Danut

Hi @Claire Profenno, It could be due to the fact that your issues do not have the Resolution field set. Please note that there are better and easier ways to track Time to Resolution in Jira. See this article, which might be of great help for…

Hi @James Gould, The process you describe looks like "waterfall in sprint" (or in multiple sprints). You still have separated development & testing phases and testing is totally decoupled from development, which is not what agile recommends. Agile testing means that development and testing happen as a single process,…

Hi @[deleted], The Cumulative Flow Diagram report of Jira could be helpful for you, so take a look. Another option would be to use the Cumulative Flow Diagram gadget offered by our Great Gadgets app. It is highly configurable and easy to use. The only limitation would be that it does not group data by hours, it can only…