Hey Alexa scare, so I'm looking to okrs how they keep you implementing get lab, um and the current proposal is having two new workout types: an objective and a key result living within projects within issue list. So um we already have tests and issues that live within the issue list and a few other items. But these are the most relevant and then that would mean we would also have an objective and a key result object with an issue list and then we would have epics or sub-ethics at the group level within the epics list.

So that's kind of like the state of things with the proposal so I'm trying to think through that and um what that would mean for kind of the value of these different items or like what are the rules between these different item types and when one would use one versus the other so um hold that in so. For example, if we have an objective work item type right when my user um use that to track objectives versus something like an epic for example, or when might they use an objective, workout type versus an issue?

And why right like? What is the value of using an objective versus one of these two? um What is the difference between the two types of things? What is our kind of vision there, um and then you know I'm going to further think about how they would link together as well and then kind of same for key results so like when would I use this key result, work item versus something like an issue or maybe a task. Even why would I use this instead, like?

What is the value here to use this key result versus something like an issue, a task or can I just track okrs through ethics issues and tasks, and if I can't, why not? um And how will these work items solve? That problem is kind of what I'm trying to visualize and then, like I, said after the relationships things like that um and somehow related to that. Maybe more granular. Is you know?

If we have these work items types of a key result and objective, then uh we would also have different attributes with them within them that are, at the moment very similar to things like uh issues, for example. So, let's say: I am within a key result and or an objective and I need to say when we're working on this. This thing right, when is this goal, uh maybe going to be uh what is a due date or what is the time frame?

So the current proposal is to use milestones, so what I'm, trying to figure out is like okay? How does that impact our current experience, then, if we have things that are more kind of goals, um not really trackable or like tactical work necessarily, but they are kind of at the same level and used similarly to uh work items like issues that would be trapped within a milestone, and you know you're looking at how they burn down, for example. So how would including things like objectives and key results um within a milestone uh impact?

Our current experience would it make sense to use Milestones to track these more goal-based things like objectives and key results? um Should it be really its own time box like? Should we have a time box list of like okr uh time frames? What does that mean, or do we Define? What a quarter annual uh goal is things like that? So um you know certain attributes like Milestones labels, uh if we use those for things that are slightly different than our current work items that are more tactical. What does that mean? Some?

Thank you through all that right now, I think. So let me know with your feedback.