Everyone- it's kenan from the product management team here, to talk about portfolio management in 12.9 to hop into our planning issue. So, first off from our validation process, I'm gonna continue working through what we're calling setting strategic initiatives or strategic planning. This is the idea that somewhere inside of the tool, businesses, companies, teams, groups, organizations should be able to set themes, goals and initiatives at a high level and then map what work is being done. That is moving the needle against one of those initiatives or goals.

You can think about this as a way to connect issues and epics up to a business level goal and then track metrics at a more aggregate level, such as total weight committed to a goal, total time tracked or overall cost, maybe or health status across multiple initiatives over time. So we're talking to a bunch of customers, we'd love to hear, have more interaction inside of the comments, so I'd love.

If anyone watching this takes a jumps in there and gives us your feedback, an opinion, but that's what we're gonna continue to move through our problem, validation, phase from solution, validation, standpoint, we're gonna continue looking into how we're representing progress for epics both on the epic itself.

You know something like this or in the epic list anywhere that we have a representation of an epic. We want to see where it's applicable to show progress towards it, so we're doing something somewhere on the roadmap. But the idea that in the maybe, in the epic view itself, we could show something to indicate progress against against the plan. Work now design priorities, kind of mirror that a little bit we're actually looking into the epic creation process in general. You know right now. We don't have the same flow that you have for issues.

So that's one of things we're looking into or even the idea that, when you're looking at looking at an epic, you don't have the new epic button up in the top right, like you do with issues. So that's something we'd like to replicate and we're going through some design review to figure out the the best way to make that an easy flow for users now for features to implement. So one of the you may see mark talked about in the certified kickoff video.

We started to collect better metrics and ideas around velocity and how much work we can actually get done in a single milestone. With the current team, it seems like we've, actually overcommitted and we've stacked up too much work causing some slowdowns in some bottlenecks. So what we're doing through 12.9 is we're not actually moving any net new projects into the development flow, but we're instead gonna focus on getting top priorities.

Priority items out in 12 that 9m as quick as we can so some of the ones, the top of stack ones that we're gonna focus on and do our best to get done or waiting progress. Information in the roadmap, which we've talked about for a couple milestones being able to expand an epoch on the roadmap to see the hierarchy, issue, health status being able to set needs attention on track or at risk.

In an issue and have that bubble up to the epic view and an ability to filter issue list by an epoch, which is something we've had a lot of requests for. So these are the four ones we're gonna do our best and really put our weight behind getting it across the line to deliver those in 12.9, which does mean that some of the other items that we have in the work flow will probably land in 12.10, confidential, epics.

Viewing start end dates on roadmap, as well as showing milestones it's unfortunate, but at the same time we need to be realistic with what we can get done on the right timeline, and we want to be transparent about that. So, as always, if you have any questions, you can find me in the tool at K O'keeffe. You can leave comments in the video here or in the individual, epics and effuse themselves. We love to hear your feedback and discussion and let us know how we can help you more. Thank you.