Bill Sheboy Expert

Hi @Jim Strange Please take a look at this article to see if it explains your situation: https://confluence.atlassian.com/jirakb/burndown-reports-showing-different-story-points-than-other-reports-949763911.html The burn charts "are calculated as point in time, rather than the actual sprint or issues." The sprint report…

Hi @Brynn Lieberman Thanks for the info. Two more requests to help you: * Would you please post an image of your full column configuration for the board, showing all columns and status mappings? * Would you please go to your backlog view, collapse the Open list using the caret, and then post an image of that view? Here is…

Hi @Hanif Remtulla My recommendation would be to identify a small set of use cases for your target audience based upon what they need to accomplish. Then create a one-page doc showing the use cases and steps, provide links to your Jira instance, and include the Atlassian provided user-guidance links. You could create this…

Hi @Brynn Lieberman Would you please post an image of your board configuration, including which status values are mapped to which columns? That will help in determining what's up. Thank you. Best regards, Bill

Hi @Randall Hoff When I think of supporting the work of an enterprise as a series of interconnected workflows, it may make sense to have a board for the delivery team and another board (in the same project) as the upstream discovery steps. The discovery board could be Kanban (or Scrum) and the delivery board Scrum or…

Hi @Shahkar Ahmad What problem are you trying to solve? It seems like you want both project and team-level views of progress. Is that correct? Perhaps if you show the workflow (status values and columns) on the two boards to clarify the situation. As noted by @Kris G _Alacriz_ above... In one project with multiple Kanban…

Hi @kalyaani What problem are you trying to solve by having a story with sub-tasks that are worked on in different sprints? For example, when there are dependencies between teams on a shared work item, consider instead making independent stories to manage the separate work...and each of those could be completed in specific…

Hi, @Monique vdB Thanks for the information. My suggested improvement is that vendors indicate their affiliation at the beginning of apparent how-to articles, particularly when the article eventually ends up pitching the vendor's products. It appears that some of the vendor affiliations are buried quite a bit lower in the…

Thanks, @Danny Zuccaro I'll try that route. __Bill

Thanks, @Simon.Wilson If you need a more immediate, non-Jira solution... you could always export your version-specific work and make a product burn chart in Excel. I have been doing that for years when tools like Jira, Rally, V1, etc. cannot yet provide the work-support info for teams I help.

Hi @Simon.Wilson You may want to suggest using historical velocity for the release burn chart as an improvement to Jira. According to the help info, using the velocity history for the specific version (release) is the intended behavior for how the report…

Hi @Nick Wallis Maybe this is an order of precedence issue in your filter. Try adding some parenthesis to ensure the processing order. For example: (project = "PROJECTNAME" AND cf[12103] = "1026") OR (project = "PROJECTNAME" AND issueFunction in epicsOf("cf[12103] = 1026")) ORDER BY Rank ASC Best regards, Bill

Hi, @Gestor MaisVida Thanks... I recall the burn chart works using the idea that the leftmost column is "todo stuff" and the rightmost column is "done stuff", with everything between as "in progress stuff". When issues reach the rightmost column, burn up occurs. Looking at your boards' status types and positions on the…

Hi @Gestor MaisVida Are these two Scrum teams with different sprints on the same backlog, or two Kanban teams on the same backlog, or something else? Just to confirm, your workflow has these statuses, correct? * "todo" status values: Todo, Fail, Looks Good, Bug A Corrigir * "in progress" status values: In Progress, Send to…

Glad to hear it. We tuned our sub-filter to show open work, and stuff completed in the last couple of weeks (that hasn't yet been released). (resolution = EMPTY OR resolutiondate > -14d) AND (fixVersion in unreleasedVersions() OR fixVersion is EMPTY)

Hi... Which of your status types are "todo", "in progress", and "done" types? When an issue is moved to one of the "done" column types, it could lead to the item showing as completed and so "burning up".

Hi... Two things to check out: Are you using the backlog feature with your Kanban board? If so, items in the backlog status would not appear on the board. Only the ones in a "selected" and later status in the workflow would show. Have you checked the sub-filter for the board? (bottom of the page on the Board Settings,…

Hi Kanban board users, I submitted a suggestion for Atlassian to add column collapse/expand as a native feature of Kanban boards. Please see this item for details: https://jira.atlassian.com/browse/JSWCLOUD-17698 Best regards, Bill

Hi @Patrick Cartier ! Thanks for the information about your product. Not to takeaway from the market for marketplace add-on options, collapsible columns seems like a pretty obvious missing feature for software versions of Kanban boards. Hopefully it will get added in the future to the out-of-the-box product. Best regards,…

Hi @Sebastian Baehr If you still want to collapse columns on your boards, consider submitting a suggestion for Atalassian to add the feature, similar to column collapsing in the tool Kanbanize. Best regards, Bill

Hi Luis, I seen no answers for JIRA other than to buy add-on products to enhance filtering functions. Best regards, Bill

My perspective is that there are no best practices; only better ones. Assuming the tools we use are the *only ways to solve problems* seems team-limiting to me. I would rather use flexible tools which allow teams to start where they are, and gradually improve. That includes when a team needs multiple levels/sizes of work…

Hi... As different people work in different ways, it makes sense that the behavior could have better configuration, allowing pop-up, side-panel, or opening in a new tab when selecting an item for more details. Please see this suggestion made to the Cloud instance for a start in this direction:…

Hi... The requestor appears to ask how to find issues which have carried over from one sprint to another. That is, committed to in one sprint, not finished, and then committed to for another sprint. As noted by others, it is possible to find a carried over issue which is also in a current or future sprint, but it is not…