 And I think, yeah, I don't have anything other than just wanted to see where we're at on 11.4. Anything else? I just put that link in the agenda. Anything else we need to talk about? Not for my end, no. Okay. So, yeah, so if you click on that link, it's just those issues there. Did Kusha or Yarka, either you get a chance to get started on any of those things? Yeah, so right now we're working on the button support for closing and reopening epics because that is like the baseline before we can work on any other related features. So we are almost done regarding the backend part of it. So like right now I've added the bad support to represent whether the epic is open or not. We're working on adding the close button under the comment form to represent whether we want to open or close epic. So fully by the end of the day tomorrow the MR should be in the ready state at least for front interview. Anything you want to add Yarka to that? Yeah, for back and to I'm just finishing some tests that I will push hopefully today. And are those after that I will continue with the API and with the quick actions. Cool. But I will use the functionality from this MR, so the next two MRs will be dependent on the first one. Right, right, right. And then Yarka and Kusha, are your work in separate MRs? Are they in the same MR right now? What's the plan? It's the same MR because Kusha needs backend. Okay, so you're both working off the same branch right now for so for 70, I'm looking at the list, 7340s. Will even the API be in the same MR Yarka or are you planning to do a separate MR for that one? Yeah, I just entered the MR. You just slacked it, you said? Okay, no, yeah, my question was, is the API going to be in the same MR as the backend support? Okay, that's going to be separate. Okay. Okay, so yeah, maybe I'm not too worried. Maybe next week we can create a different issue if we need to just to track it. But since it's so early and that we don't maybe have to track it as close, hopefully, I'll be then done. So it sounds like close epic back in an API and then close and reopen epics with buttons will be together on one MR and then view open, close epics in this view. So that'll be totally separate, right, Kusha? Oh, sorry, the API will be in different MR than Barton. Will be in the same MR, you said, Yarka? Different. Okay, okay, so the API will be totally different MR. So should I, why don't I just create a separate issue then? So just for API, right? I take the, actually take the create backend plus API, we can just rename it actually, I think. Right, so right now, because backend implementation is already part of the close using buttons. Okay, I see what you're saying. So you mean I should just rename the close, reopen epics with buttons or include the scope there for backend, and then the one that is close backend and API just reduces scope that one, just so move scope from one to the other, right? Yeah. Yeah, yeah, exactly. Okay, I'll just do, I'll take a note to do that. So move. And also for the second issue, which is view open and close epics in the list view, that will also be a different MR. It is more like, so from the backend side, it could be merely a controller for your team. Right, I'll add the tabs. So that's a different MR as well. Yeah, because there is some backend work with the, like we said that we might want to do the counts as well, right? So that there might be some backend work there. Yeah, no, that's, that's all I wanted to check in. We can, let's see. So anything else that we should be talking about? I haven't looked really far ahead or just heads down more. Do we want to talk about anything that's any questions that might be lingering for the the other issues after due 22nd? Sure. If there are any questions, I didn't see any, I mean, I saw the button placement question, but that was the only one I saw. Anything else? Kuscha or Yarka, or if not, Pedro, if you have, you want to discuss it. So not, not related to this one, but like something in the afternoon. So while I was waiting for some changes, what I was, I basically tried debugging the Safari problem because that you mentioned where the sidebar icons during showing up the popovers once you click on the icon. And it turns out that it is a Safari bug itself. Like, so what happens is that the focus event that happens in different anyways is supported in all the browsers except for Safari. Safari doesn't, basically it cannot differentiate between click and focus for certain types of things. So I'm looking more into that. So most likely we'll have to add some browser specific fixes on that one. And yeah, if I get a chance within this release, I'll sneak in that change as well. Okay. Is it like, I think I, like I said in the issue, it's, it's not high priority, but like, I don't want to stop you from doing anything that you want to. So that's obviously that is something that I'll focus only if I have an hour or two. Yeah. And speaking of like issues that I don't see in 11.4. So that one, I think I just put in backlog somewhere. So yeah, if you want to look at it, I'm not going to stop you obviously. The, all the other bugs where they all merged already, which is really, like I'm going to 11.3. And I don't see any bugs in, I mean, the image attachment thing that Yarka has been working on. But like there were like, weren't there at least like one or two bugs with the sidebar? And then like Kushal, did you already merge all of them? Forget regarding 11.3? Yeah. Yeah. Yes. Yes. We did got everything that was scheduled for 11.3. If there is any issue that left out to be closed, just feel free to ping me. I'll make sure. Because as far as I know, I believe regarding the sidebar date related changes, it broke it down into multiple issues. Right. Right. Right. So I was just talking about bugs. Like I remember, I mean, I remember you, you saw one bug right away and you logged it. And I think you already. Yeah. So those are all closed. Those are all closed. Right. Yeah. I just wanted to double check. Yeah. That's awesome. Okay. Yeah. Anything else? Pedro, you want to talk about like future designs and stuff like that? Since we're in the call, we don't have to. Yeah. I was looking at the issues that we have for the rest of 11.4. You mean? Yeah. For, I mean, for 11.4, they look, I think everything's pretty clear. I was just, wondering if anyone had any questions, so we could use this time to talk about anything that was still pending, but I think they're fairly straightforward. Yeah. And in the roadmap we're doing, the close epics is one thing that we're focusing for the next, this release and the next, I believe. Right. And then afterwards, looking at the roadmap, we have the moving forward and backwards in time. Right. Which we haven't really dealt with yet. And then the flexible work breakdown. So those are very far ahead in the future. Yeah. From my end, I don't have any, any questions, particular questions, but if you want to talk about something specific. I'm looking at 11.5 right now. There's like way too much stuff there as the first class. But yeah, let's talk about that like next time or, or well, maybe if we're making good progress on 11.4, maybe we'll be able even to pull some stuff in. So we definitely don't know if that's possible until at least next week, if not later. Right. So there's still a lot of stuff for your 11.4 scope currently beyond due 22nd. So, but yeah, let's, let's, let's keep checking in. All right. If there's nothing else, we don't have to just stay here forever. Okay. And this will be a short one. Okay. Thank you everybody. Talk to you next time.