 Okay, yes. Do you have anything you wanted to talk about first, Kusha, before we get to talking about what Yarka put on the agenda? No, the only thing that Yarka mentioned me was that why the close epics from using UI got delayed because it was waiting for the reviews from the back end as well as like all the points she already mentioned. Okay, and it should get merged today itself because most of the reviews are done. All the comments from Alexander, sorry, Douglas have been addressed already, but since Douglas is in the different time zones once he wakes up, he'll approve the MR and then we should be good to go. Great, and so all those were back end comments on the MR? Yes, yes. Just curious, who do you usually assign to front end for review? So the front end review is already done for this one. So like front end has been reviewed and approved by last week. Does that it involves some migrations because we were introducing a status, it required DB reviews. Yeah, I was just curious, like is it just a random pool for front end or is there, do you have like dedicated, do you always go to the same person? Okay, so personally what I do is that I assign someone who is closer to my time zone. Okay, that makes sense. It becomes easier for me to address the comments as quickly as possible. Right, right, right, right. Okay, I was just curious how that goes usually. No, that's great. And then she said there's this follow up issue, which I just saw was created six hours ago. We added comments but there's no auto complete. Yeah, yeah, so this is something that we realized while the UX was being reviewed with from Annabel. So what was happening is that in Epics, if you put slash in the comment field, you wouldn't see any command loading into the context menu. It would just show you the load and spinners and we didn't have any commands there to begin with. So it was implemented from the backend side. Although that feature is a user facing feature where a user would be seeing those commands. The entire wiring of that command, like what are the commands available for a given context and how to pull it up is all done via backend or the front end. Okay, it's interesting. The only thing that front end does is that it ensures that if there is a URL to hit to pull in the command, it would just hit the URL. Okay. But in our case in Epics, URL wasn't available because we didn't get to implement it and which is why the auto completion is not available. Although the commands like slash close and slash open do work. Right. There won't be seeing those commands as a context menu user types in the slide. Right. You mean you have to type in manually and hit enter in your whole work. Yes. Yeah. So that is that is something that Yarka said that we can implement as a different MR and then get it merged before seven. That'll be great. 20 seconds. Yeah, yeah. No, I agree. That'll be great to get that in. So I know we have like a bunch of issues. I don't know where we put them, but stuff for like assigning a label to Epic with a quick action and stuff like that. So this will at least, it'll be one step closer with this change. Right. So at least it will basically lay the foundation to, you know, let's run the command. Then we can add options like label, unlabel, assign and assign in case we want to use a thing. And then like, like dates and stuff like that. So there's a lot that we can, we can do. Yeah. Yeah. Okay. And then show epics by statuses open MR review. Oh, that's the list of you. Right. Is that? Yes. Yes. So this is something that again has the related MR already in place. It is currently working progress. So if you look at the second MR, which is currently in open state. So this one is basically waiting for backend to available. So what we wanted to do was that we wanted to ensure that the original feature which the status to the epics gets merged into the master. And then we is this particular MR against latest master. And then the pipeline would pass and this feature would be right away. Cool. And so this is waiting on a backend review you said? No, no, no. This is waiting for the original MR which introduces statuses closing epic or opening the epic because we want that feature to be available before we introduce the tabs to filter out epics. Right. We will be going tabs for open and closed epics along with all epics. Right. Okay. Oh, yeah. Open MR review after the first one is merged. Right. So I was asking seven four to four. Is that is that already done pending review or that's not started yet in terms of So from the review perspective, not yet because we just wanted to get the backend be merged into the master. So we wanted to know if the feature works or not. Okay. So once the tabs are functional, like if user visits the epics page and sees all the tabs and like returning is everything is working, then we can assign it to me. All right. Sounds good. And then the last one is supporting short references. Okay. Yeah, this one. Yep. And then so this one is good and she say or you can say. So this is basically for within the issues in the comment field. If you want to add a particular issue to an epic slash command, it's just really bad. All right. And then so this is under development as well. Yes. Yes. Okay. Yeah. So it's just like, yeah. You're a page or commented yesterday, 21 hours ago. Oh yeah. No, this is, this is great. So I'm just looking at the outstanding issues for 11.4. Hopefully we're using that. Yeah. Yeah. It's a really good question. Dev, Dev thing. Yes. Yes. Like all the MR's like, I know that two issues were purely front end changes. Right. One was basically renaming the portion of the pages where we were using plans. And we wanted to start date and new date. So that is something that the MR is already open and I have currently assigned Docs team to review all the documentation pages. Awesome. So I'm not going to be pinging that particular MR in our portfolio management channel. Okay. So yeah, this one. So this is currently waiting for Docs team review. Pedro has already gone through this MR once and has spotted a few places where we missed out on replacing the string. Okay. So that has been covered. Once I have the approval from the Docs team, I'll assign it to maintainer because the changes are small. And those are mostly string changes. So it won't be long. Okay. And then you said, okay. Sorry. I was just opening slack. You said this is, has to be reviewed by the documentation team? Yes. Yes. Because we have updated two Docs pages as well. So basically I am following the process that GitLab bought suggests. Like if you look at the pipeline for this particular MR, then there is one job that has failed, which is a danger review. And it mentions like if you have updated any markdown files on the user documentation, then it better goes through the documentation team for review before it is assigned to maintainer for review and merge. Okay. Okay. So yeah, so there's a lot of Docs changes here, but there is some code changes, right? This is where we're adding the to the. Yeah. So it is basically just a string replacement like all the places even in the review application site. Right. We are using plan start date and plan finish date. I'm just replacing it with start date. Oh, right. Right. Right. So yeah. Sorry. I got confused. So this is not the one where we, where we add the dates to the, to the hover, right? You know what I'm talking about. That's a different one, right? That is entirely different. Okay. Okay. So, okay. Yeah. So I didn't want this one to be like held up by Docs team if they're busy with other things, but this is purely Docs. Okay. Yeah. Understood. Yeah. And the issue 7307, which is like add missing Docs link for milestone dates integrated into Epic. So the pop over thing is already merged and completed last week. Awesome. Okay. Yeah. I didn't even see that. Thank you. Yeah. So it was, it was purely front end and it was a small change. So got it merged earlier. Great. That is purely front end that remains to be merged is this rename thing. Okay. Great. So I'm looking what else is open and is anything else that's that hasn't been started yet as well. I mean, we have like a century two weeks. Yes. So, so that is what I also wanted to bring up. Like if we want to squash in any small item within the cities, then we have a bandwidth because as you know that the closing ethics part is already about to merge. Then the tabs thing where we will be having open and closed tabs on the ethics list page is also waiting for that main merge request to get merged and reviewed. Right. And then there's this quick actions part, which is work in progress. So if there is any pure front end thing, then I'll keep an eye on that. Like there are a few bugs, which are probably front end that I'll see if there are any in the back. I'll cover it within the release. So anything else that you want me to cover it as a high priority. I can take it. So, so I tried, I'll try to keep just going forward. I told the team, I'll try to keep everything up to date. For like the next couple of milestones. So we can always look at 10, five, which I switched to or 11, 5, 10, 10. And then what I haven't done is do the do 22nd, which I may do, or maybe just put it on the board. Because that one, I can work closely with you folks to set the current expectation. But it also means that. So why don't, why don't I do that? Why don't I spend a little bit of time putting like do 20? Well, you said Yarka might not be done, done. And then you'll probably be freed up earlier, right? Is that what you said? Yes. Yes. Okay. Because the quick actions thing. I'm not sure how much from the back inside that it has. Right. Although if you look at that issue, it has front end label, but as far as front end is concerned, it is minor verification part only. Okay. That's command is entirely handled. Right. Right. Right. So yeah, no, I'm just looking at 11.5 and finding the looking at which one is front end only that we can basically pull into 11.4. Right. Right. Right. Right. And then I'm looking at the, the sort thing is that is also back in right. So direction for. I think we, we got it done in one of the release. Okay. Okay. Initial sort. Not that sort. Yeah. Yeah. This is different. Like we wanted to introduce a sort direction as well. So that is the. Yeah. So is that something that we can do that doesn't require back in? No, it does require back in because we would have to pass ascending or descending as a query. Okay. Okay. Okay. I see. I see what you're saying. So this is not, so we, we have to dig up something else. Right. So I'm just looking at the list and everything looks like it's just in this. Yeah. Like all the items that I see only first one that is epic issue list and issue list design. Flatten row. So that is something that doesn't require back in. But again, it is something that is like ideal for a release from the start instead of, you know, pulling it in. Right. So, so are you looking at 11 five? Yes. So I'm looking at the same filter. So I have these labels applied to the. Yeah. For the management and front end and then milestones at 11.5. Right. Right. Okay. Yep. Yep. I'm looking at that too. Yeah. I just felt an upfront and, um, and then epic attribution. Why did that get pulled to them? I'm sorry. The second one I thought was being more fun by Sean. Or was this another one? Oh, right, right. Okay. That's fine. Okay. Um, did, uh, did, did, did you talk to, um, uh, Andre about the refactor thing? Uh, so I spoke with him, uh, like how we want to break it down and he said like, uh, yeah, sure. Like, uh, and basically we, as we discussed in our call as well, like we want to plan it for 11.5. So now that I have all the 11.4 items out of the way, I'll create an epic to refactor the epic and then we'll put in all the issues, uh, based on how we want to break that entire refactor into multiple, uh, portions. So yeah, I'll open the epic, I guess later today or probably tomorrow itself and then, uh, we can discuss it, how we want to go about it. And then I can even start working on that within this video is like, I can at least push out a small MR just for the shell part and, uh, get it out of the way. Obviously it would just live in the code base or 11.4. It wouldn't be alive anywhere. Like, uh, I would have it behind the flag and anything. Right. That's exactly, that's exactly what I was saying. Like, do you think that's a good. Yeah. Yeah. So that is something that, uh, we can shortly start on 11.5. Yeah. I keep muting myself as my kid. Um, no, I was saying, do you think, um, like, is that a type of work where you can just keep running? Or is that like, there's the initial planning. So you have to do a lot of weight. So like everything is already, I have, uh, it's like, like how I want to begin. Okay. So it's on your brain. Yeah. So it is, it is basically not formulated in any issue or epic. So that's what I'll do, uh, to create concrete issues so that we can understand like, okay, this issue covered this much scope. And then we can open MRs and do that. So I'll open those multiple issues and that umbrella epic to hold all those issues tomorrow. And then I'll start working on that, uh, groundwork part and open an MR. And then we can, we'll see if we can get it merged within 11.4. So at least the code gets into the master plan. Yeah. Yeah. That's perfect. Let's do that from like a project management perspective. Let's have you create the epic. And then, um, you said create those issues and then you, yeah, please go ahead and start working on it. And then we can sort of retroactively assign whichever issue to 11.4. Um, that you think we can get done. And then the rest we'll schedule for later. Um, and then this is Tuesday. So by next, next week, we should probably with her, hopefully Yarka can make the meeting next week. Um, next week we should talk about 11.5. Um, scheduling. Um, but, but I mean, like I said, I already have everything here. Right. So, but it's also like maybe representative of like, there's no front and only thing. So there's a lot of dependencies here, but, um, yeah, before we leave, when you're looking at 11.5, so yeah, switching topics quickly back and forth. Um, okay. Yeah. So, uh, so, so the, the refactor, please go ahead and do it. Let's, I think that's a great use of time, um, for the rest of 11.4. And then for 11.5, when you glance at this list, um, is there, is it, do you think it's immediately, there's, there's too many things here. Um, no, I think, I think, uh, it is moderate like, uh, so all the items, although those are like mixed up both front and back in, but if you look at the individual items and those are minor ones, so collectively I think we can surely cover it. Okay. Or is the, issue list and the issue list design pattern row. So again, as I can see, like the rest of the four items. So I have, uh, let me share my screen. Okay. Yeah. Okay. So I think, uh, I've just upgraded to Mojave and I don't see any options in the zoom and it is just asking me to upgrade. So, uh, no, basically I'm looking at, uh, this issue filter as we discussed, like, uh, I have two levels applied for management and front end. And my stones set to 11.5 and I see five issues. Uh, the first one is the epic issue and issue list design. Uh, and the rest are like sort direction for epic and road maps show actual dates within tool tips, uh, epic sort of complete issues and MR and epic auto complete milestone. So the last four items are like, uh, more of a back end heavy rather than front end heavy. Uh, although they do require some front end effort, but those aren't, uh, like, uh, it isn't much effort, uh, individually for all those four items. Okay. The first one itself is front end heavy because again, it is purely front end. It isn't back end. So I think, uh, uh, I'll be able to cover those five along with the re-factor issues that we might plan for 11.5. Okay. So, well, I also have to be careful. Um, so hold on, uh, can you look at which one should have front end? Because I'm looking, if you take off the front end label and so by portfolio management, I think the last one promote issue to epic should have front end label, but it doesn't. Okay. Okay. Let me open that. Okay. It says promote issue in a project to epic and road. And we even have a design yet. So that, that's, that's a problem. So I will. Yeah. Yeah. So I, okay. Okay. So I understand what, uh, what it means is that it basically, uh, wants to have, uh, basically a license flag in place before. Right. Yeah. So I think only that part. No. And this one probably needs to be broken down further. Anyways, there's a lot. This one's pretty big. So, um, yeah, this might not do 11.5 or if we do it, it will be very like, uh, uh, maybe something like, Oh, only promote title or something like that. Right. So, um, I'll ask Pedro to take a look at this one. Um, okay. Yeah. So I think this, I think this we need to, we need to break this down a little further, but I'm just looking at the other ones. Like you're saying they're back in heavy, which is good. So, you know, hopefully we can squeeze in more of the refactor in 11.5 as well. Uh, and then at the same time, I'm looking at all these issues. There are like, they're not new features, right? Like the only new feature is promote issue to epic. And even that is like, sort of like, it would be great to have that, but it's not like a new, new feature. All the rest are like sorting and notifications. And we're still working on that. Like if you remember, I told you folks that. Yeah. Like let's aim to finish that by the end of the year. And then, and then hopefully, well, not hopefully I expect Hannibal to have really good designs for us really soon, like in the next couple of weeks. And then we can start talking about that. And then they'll be like, it seems far away, but it comes fast. Like it's September. Oh, next year we're going to start it. No, it comes fast. So, so I really, really hope that like by, but we're in September, right? So like mid October, you'll be staring at like sub epics and then you'll be like, Oh, how the hell did I implement that? That's really weird. And it's going to be like, we have to do all this back and work. I'm going to go and I'm going to be like, no, I don't want to do all this refactor again. But I want to force us to have those conversations really early as you're wrapping up these things. So I'm looking forward to that. But anyways, yeah, that's really good. Good. Yeah, go ahead. Do the refactor stuff. Keep everybody up to date on the channel. I'll do exactly the same for the promote issue to Epic and stuff. Pedro for designed and stuff like that. Great. Anything else on your side? No, that is. Okay. Awesome. Thank you. I'll talk to you later. Yep. Sure. Bye. Bye.