 Yeah, go ahead, Yarka. Yeah, I'm just trying to hold my GDK. Okay. Yeah, we can ask, yeah, no, no. I have the page ready, Yarka, in case you want me to start first. Yeah, you can, sure. Okay, okay. Let me share my screen and then I can, sure. Okay, I hope it is visible. I have the DevTools sidebar open, so I hope that isn't a problem because I'm going to also show the workflow in case the request fails. So yeah, the demo is about this, basically a status badge that shows up next to the epic details like the author and the open date for an epic. So it looks similar to issues in MRs. And we have moved the delete action from header into the edit section. To edit any particular epic description, you would see delete action from here. Right. And clicking here would delete the epic. I would open another epic and delete that one. So for now, this close button here and here perform the exact same operation. And no matter which button you use to close the epic, it would reflect on the UI across the page. So for instance, this is open and I click on close. Then as you can see that now the badge has updated. Both the buttons have updated as well. It now says reopen epic. Same thing goes for this comment button as well. So for example, I want to reopen this epic with a comment. So I'll just say like reopening it again. And I'll just do comment and reopen epic and doing this. Well, as you can see that it has left the comment as well as updated all the badges. That's cool. This is awesome. So this is for the normal part. Now what if request fails for some reasons? I'll just make the page offline. And now if I try to close an epic. So as you can see that it goes into a brief loading portion where you would see a loading gif on the button. Then it would also show flash error like it cannot be updated at this time. And this message is very similar to what we have for MRN issues as well. That is an issue it says epic. So it is consistent across all the three places. And now if I resume the networking again and then again try to close it and then you would see that it got changed to reopen. Now we can see the workflow of delete an epic. So for example, let me create a new epic because all these epics have certain dates set because I need to test it with roadmap. So I'll just create a new one. Say temporary epic. We create it. And there we go. We have it now in the description. I click on delete and it will ask epic will be removed. Are you sure? Oh, sorry. I'll obviously. Is that new? Is that? I mean the words are new. Delete is not new, but is the is the popup new? No, it is actually using browsers native alert. The reason why I need, I have used this custom message. I was testing out something locally. Obviously I'll have to change it now. But yeah, basically it shows browser alert instead of model dialogue. And this is the case for both issues and MR as well. So I'll have to obviously in case we want to use browser dialogues like the CSS style dialogues where delete button is in, right? So that needs to be done across all three places instead of just one. So this is basically reusing the exact same thing. Okay. Even the wording is it. I'm trying to find an issue right now that I can delete. Let me show what the exact wording is. The only portion that it doesn't have in the production is my man part. Okay. That's all I wanted to see. Yeah. The issue we remove. Are you sure? Yeah. I have basically changed it in the main part. I just wanted to see if the code changes that I'm in the right case or not. Awesome. Yeah. That's great. That's great. Okay. So if I click on delete and hit okay, then it would basically delete the epic and bring user to the listing page and would show the flash error like the epic was deleted. Yeah. So this is basically the entire workflow and the last commit that I'll be pushing. So the code has already been reviewed from the front end once. I have addressed all the suggestions that are still made. So I'll sign it again for review. But from the front end review wise, it is good already. And except for that message part, any comment that Pedro, you have then feel free to mention it right away so that I can note it down and do the changes. Yeah. I think only thing we need to look after it doesn't have to do with this issue is standardizing the deletion models so that we have that confirmation not using the standard but using what we are trying to do in the future, which is to have models everywhere. Do we already have an issue for that? Because I know we have so many issues for the models. Probably. Somebody created a bunch a while back. So there was like a big meta issue of a bunch. But I don't recall seeing that one because I remember like fixing a lot of other ones but don't recall deleting because it's rare nobody ever deletes issues. Okay. So get labbers usually don't have permissions to delete. Usually they don't have the permissions to delete C E and E issue. So that's probably why nobody ever remembers it. Yeah. Yeah. I guess. I'll check it and if it's something that we can schedule so that standard throughout, I'll see how it is. Yeah. So I think we have a single which tracks basically all the places where we are using all the boxes instead of proper style model dialogue. So I think that issue is kind of it should rather be an epic right now because it needs to track all the places where we are having these other boxes. But yeah, that is the only thing that remains and needs to be done. But apart from that, the future is ready. That's awesome. Now you can demonstrate the slash command part. Oh, yeah. Actually, I don't know what happens, but the page is not loading. Although the the GTK is running. Could you just? Yeah. It's the same branch. It's the same branch. I think we could use this. Yeah. Okay. Okay. Sure. Sure. Sure. Sure. Sure. I'm sending you. We are like which commands you have to use. Okay. Sure. Okay. Close and slash reopen. Okay. So it is pretty much same as what we pass on as a state of string. Okay. So like, for example, this epic is open. Let's try to close it. Just say close and then the command applied. Okay. I think it's really to reload. Yeah. Yeah. Yes. Yes. So this is basically the case like with slash commands, we would have to listen for the changes and then reflect it across the UI. So what I can do here is that so it should be a rather simple change to make sure that whatever status updates that happen even by a slash commands get reflected on the UI. So it shouldn't be more than two lines of change to make sure that we do not change the page every time we use a slash command. Okay. That would be great. Kushal, let's let's check in a separate issue, especially since we don't have that for issues and merger costs. Let me see if that is the case. Yes. Yes. Like even in issues, it doesn't work. We have to reload it. Right. So what we, I think we tried about previously is that we would have system notes first. And so system, if you go to the epic, we have system notes for closing and reopening epic. So that's not in scope for this issue. What you and York have already done. Yeah. But having that, I think we should do that before the side panel. I mean, we could do, we could, you know, we should definitely log an issue. But we're going to have system notes. And the reason I bring that up is then then we'll have feedback for closing and opening. And we will also have feedback if you use the button as well. I mean, you're ready to do right now because it's obvious, but that will address it. But what's, I guess you said that it's, it's fairly straightforward to update the sidebar. Is that just applied to epics or because I remember we, we chat about this for issues and then I don't know who I chatted. Okay. So, so if, if what you mean is that, so for example, if I run any slash command to close or open epic, then in, in order to update the status badge as well as both these buttons like you think, as far as epics are concerned, it is, it is a very minor change. Okay. At the same time, what I feel is that not having a system notes for open and close events is something that we should prioritize instead of doing this course. Right. Right. Yeah. So, yeah. So there's a, there's a couple of things. There's, there's the, there's the badges or I mean, there's, you're right. So there's the badges, there's the buttons, and then there's a sidebar. And then I think, yeah, we should track those all separately. So maybe we, let's, let's have a separate conversation offline or maybe are you saying like all those are pretty straightforward or just, just for our knowledge. And then even like, so there's two pieces, right? There's the, there's those, there's those three places. There's, but let me repeat. There's buttons, badges and sidebar in terms of scope. And then in terms of functionality, there's at least two ways I can think of it updating. There's the way where it updates on the front end immediately or it updates in real time in the background because it's pulling and then maybe there's a third way that I don't know it and why that distinction is relevant because if I'm looking at an issue and then somebody else updates the epic or issue or MR, then those things will update like within seconds. So can you speak to all those combinations? Obviously we shouldn't do them, you know, in point four, but how much like, as far as so the case that you mentioned, like if someone has closed the epic from other place, then it, whether it reflects here on the UI, I don't think that's the case. Again, I'll have to check by actually doing that from a different browser to see how it works because polling does happen on this page as well. So ideally it should be updating, but I haven't spotted any code for this particular part, which basically listens for those polls and updates the UI accordingly. So I'll have to check on that, but as far as like updating these buttons and badges based on any user action within the page itself is concerned, then that is a simple thing to do. The reason I ask all that is I'm not sure that that's the right design because there's an ongoing issue. I don't know if Pedro knows updates because I've been watching too closely. Tate has been working on an issue to figure out like across the board, get lab, how you save and stuff like that. So I don't want us to do extra work if we're not going to use it or it's going to change very soon. So the idea, like I mentioned, like when you do an interaction on the front end, you can, if you don't have a round trip confirmation with the back end, you can do a, you can assume that it worked on the front end and update something, right? So whether you change a milestone, when you assign a label, where you change the status open, close of an object, you can do best, you can assume that worked on the back end and change the status immediately, right? And so I don't know if that's the correct design, if we want to do that or not, or do we want to wait for the round trip? And if we wait for the round trip, doesn't mean that we just noted one place, which is just wait for the polling, or do we like intentionally not poll, but just block and wait for it to return. So there's like three or four different ways to do it and then it's not clear from a design perspective, which is, which is the correct one. So I don't want to add all this complexity, at least to Epics if there's no clear design standard there yet. Does that make sense, Kushal? Like there's all this, all those possibilities? Yeah, and so that's why I was saying like, at least for system notes, I know that at least it's already polling. I think pretty sure on the, even on the Epic, so we'll quote unquote get that feedback for free when we, when we do system notes for open and close because it'll just show up once we get system notes. Yeah, but Pedro, do you know, do you have any immediate thoughts on that? Even if like the, the design feedback. Yeah, well, like on, yeah, yeah, like feedback, should it be instance feedback, should it be roundtrip and then like, and all those different cases? Yeah, I think it should be immediate feedback because most of the times we're dealing with, so for these specific cases where you're changing attributes of an Epic or you're opening or you're closing, like most of the times when people are using GitLab they already have an active connection. So I don't think they're, we're going to have that much problem with people not having like doing work offline or something like that. So we, we should just do it, but at the same time we should have some failsafe mechanism so that if the person tries to, I don't know technically how it works, but if the person leaves like closes the browser window, would it affect the, the request? And if so, we need to have some, some mechanism to make sure that. Yeah, so I didn't even think of that. So the, the experience that Pedro has mentioned, so right now in GitLab across any page that you visit, we have this reactive approach instead of proactive, like we always wait for network to come back with a response and then we update the UI. We have this intermediate state where we would show a loading animation or we would say like something but we wouldn't directly jump to a conclusion like this request completed successfully. And then for some reason if request fails like the connection dropped off for a second or two then we revert back to previous state. That isn't something that we already do. We always wait and show intermediate state like something is happening and then once response is successful, we then update the actual state. So if we want to do the proactive approach, it is more of a design decision like whether we want to do it across the app or not. I think we will still have the case of an intermediate state because intermediate state here is, let's imagine that you change the labels on this epic. Right now there are no labels, you add some labels. What we're saying is we would immediately, so like this design here, I think it's a good one, what just happened. Like the labels were immediately added even though the server is still communicating. So we're not waiting for the reply back from the server to show the labels or to... I think we are, I think we are. We're waiting for that? I'm just, well maybe epic is different. I'm looking at an issue. Labels wait for the spinner. Assignees do not. I've checked this multiple times in the past. Like the sidebar for issues is inconsistent. So that's why I've been... Let's try it out right now. I've slowed down the network. So the request should take some time. But we want to see if the labels got added on the UI or not. Yeah, it's waiting. This is the problem, right? So what we want here is to immediately show the labels, but still have that feedback indicator that it's loading. Okay, I try for epics. Yep. So epics is the reverse, right? Yeah. Because it's a view app, right? Like it's a separate view app, like you said. Or you've told me multiple times in the past. Yeah, yeah, exactly. So the sidebar implementation is entirely different. And then if you look at Assignees for issues, it's instant and doesn't wait for roundtrip. Yeah, so like for instance that, right? Right now while demoing what I did was I just turned the page offline. Okay. And then I tried removing the labels. Then it shows flash error like the label. Because that's a roundtrip. Then we are stuck in Limbo and it shows like the loading animation is still going. Network has failed. So this is like the actual problem that we already have in production. Like ideally we should help this loading animation go away and then let the labels be as it is. But we are still showing this animation in place. So yeah, so I want to do this. But I also want to wait till we have consistency. But at the same time, we're never going to... Guys continue, give me a second. It looks like what you were just showing, for some reason, because it's a view app where we have this done for the labels in Epics. Yeah. So maybe... The problem, yeah. Actually the problem is the entire structure of the Epics app needs some serious restructuring right now. Which is why these are like small places where we haven't noticed what is going on. Like for example, this one as you saw, like the animation was still showing up even if network request was failed. So this is more of a structural problem I feel because there are many small areas of code that I haven't debug through and through. So yeah. So is it something that you said it was a serious structure issue? Is it something that you want to... Yeah, so I'm not sure if you got a chance to see this particular issue. I have created one which is related to the structure of the Epics app. And it is currently in discussion. Discussing with Andre in our one-on-one as well. Like right now I have just pulled up our one-on-one document. And here I have... Let me bring this issue in the Zoom chat. Cool. And so is there... Is it possible to schedule this issue or are you still discussing how are you going to... It depends on whether Victor can allocate me working on this one partly and partly on the actual features. Because yeah, it will take some time. At least one update will be required if I were to work on it full-time. Or if I were to work it like partially along with all the features that we plan for the existing app. If we want to do this restructuring as well then it will take at least two updates. Although right now I have already started doing the groundwork for the restructuring like no matter when in the future we decide to do the restructuring. But whenever we do do it we shouldn't have much to work on. So for that I have already really started restructuring at least parts of code based on how the needs are. So for example, to do this close epic feature we had to spin out some changes like creating a global service instead of using the one bit sidebar already has. So like I have basically started laying the groundwork for it. So whenever we do decide to schedule it for any particular release it should be easier for us and it should be less time consuming because the groundwork is already there. Sorry Kushal, since I just came back. Is this for epics only? The view app? Yes, yes. It is just for the epics shell. Not the list because the epics list part is something that is not view app. It is a main hammer position and we do not even need view application here. Only portion that is view app is this view button and it is very small thing. It could be just half a day's effort to restructure this particular button drop down thing. And of course when I say like we want to restructure the thing, the roadmap and epic shell are two different things. The roadmap is in good shape or we do not need that. So your issue is, the scope of your issue is just the epic page itself. Yes, yes. Just this shell part and also like most of the portions in the sidebar are reusable. For instance this entire portion that you are seeing in the dates and radio and everything it is already created as a standalone component. So if I show you directly then in the epic the sidebar folder we have this called sidebar date picker. And this component was written from scratch based on the design that we have. And we will be reusing this file as it is. We won't be doing any changes. So everything that is written for this file be it the structure or the tests for this file will be reused as it is. The only portion is like right now the sidebar is like entirely different folder in which it has the name called sidebar app and then we have epic show and then there is this new epic. So this structure doesn't feel right to me and it basically makes our lives difficult to add any new features because the way it is written for this entire structure are quite complicated. They are really quick questions. So right now the only view app on the page is the sidebar and then in the middle is like HTML whatever Rails stuff and then what you are proposing This is the real stuff. This particular portion the description and the header part this isn't real. Those are view but they are not view apps they are view components Yeah in a way yes because the entire application lives in this single folder called epic. The whole thing be one view app is that I mean I don't think it really matters. So it is more of a file reorganization stuff where I would also be updating tests to make sure that the structure is same and scalable. So right now if you go to roadmap app then anyone who comes to do any changes into the roadmap by looking at the folder structure would know which particular file is responsible for what like for example app view is the main shell then there is this roadmap shell which renders the skeleton of the entire page. If I were to check what a typical timeline would look like then this epic item would represent a single epic item then epic item timeline would represent that blue mark. So it is more of a semantic change anyone who wants to start a fresh working on any changes of the roadmap it is much easier to understand what is going on which is not the case in case of these epic items. Awesome and so if you can go back to the issue sorry I'm just flipping it, are you sorry I came back I came late so did you revise epic page did you have something I think I asked you something there on the issue right or yeah yeah Your question was like how fast would it enable us to add new features to the epic page. Yeah yeah I've already answered like at least 50% faster because right now most of my time is spent writing the test just due to the sheer complexity of how the tests are structured not because the testing a particular feature is hard but the way the app is structured updating so for example if I add a new item within the page then I would have to add multiple files just to make sure that the entire feature gets tested the tests are structured for this particular app that is the problem but yeah if we revise the structure of the app then we would also be revising all the tests for that app and then it is much easier to do any changes because we only have one one mapping of every feature versus the test for that feature. Makes sense and so my last question there was that can you create individual issues are you saying that you want this to be one issue yeah so like even if we break it down to multiple issues what we can do is like we can create one issue for like revise the cell structure but in any case the end result would be the actual app once it is ready and the proposal as I have mentioned like was that we would have a way to toggle a switch between the older app and a newer app and for like a week or two within master both the application code bases will be living and once we have the master we can go back to dev.gitlab.org then anyone can go ahead and just toggle the switch and see how the new application performs and works. Visually there won't be any difference it will look the same just behind the scene structure of the app would be different so that was the idea so even if we break it down to multiple issues what would happen is that all those issues will get closed as soon as we hit merge on that okay oh yeah yeah so let me ask not in terms of issues but well we should do our stuff in terms of issues but are you saying that we cannot break this up into more than one merge request for merge request? no no we cannot so everything has to be done in one merge request and sorry I wasn't totally understanding you said that the two we care about this an issue you said if we have two so I'm reading what I wrote just of course if we have two view apps side by side in the code so what were you saying like would that be inkilllab.com would that be a production to have both view apps so what would happen is that obviously we won't be merging it right before the freeze day right because that would make it available on gitlab.com as well so what I would do is that I'll make sure that the merge request that we are aiming becomes new 22nd thing and gets merged by 22nd of the month so we still have like 15 days between 22nd to 7th of the month so within that time frame we do not anyway deploy code whatever that is in the master way into the gitlab.com it always gets deployed on dev.gitlab.com so that is where we get I mean .org won't have this code .org is oh yeah it is community edition so on the staging it might be but otherwise then in that case what would happen is only devs will be able to access it who will have gdk access and the reason you want to do that is just you want more testing yes that's fine we can do more testing ourselves and not too worried about that but yeah if you want to do that strategy to have two apps and then hide one and then we can test it we can get Ramya to help as well so I'm not worried about that I'm just concerned about the scope of work required and then you're saying it's one iteration is it one iteration of one person full time or is it yes so like again I'm basically giving the time frame moderately I'm not basically squashing in a lot of effort in like a certain release so I want to make sure like if something comes up be it on the portfolio management itself like last week we found out like that was not hiding for unsigned users so if something like that comes up I shouldn't be you know blogging I should be able to jump and fix the issue at hand but yeah if I were to work on this like full time with complete focus it might not even take one week itself because most of the stuff is already isolated so all the sidebar items specifically are isolated and can be reused as it is without doing much of it okay so let's do the following I think we're going too slow and that's not your fault Kushal we have two little people working on portfolio management so I've been wanting to get I've been wanting to get Andre to see if we can get more like right now on the plan team there are three front end developers so there's yourself, there's Fatih there's Constance and then like Fatih is not even here this month so I can really feel it everybody really feels it so we have like half the team you doing portfolio management and the other half the team Constance doing everything else and that's crazy to put all that all that effort on Constance to support the rest of portfolio rest of plan Fatih comes back still I think it's too little and then because we're essentially one third of the team is doing portfolio management which seems like a lot but we're still going to slow in my opinion so to me it's not the fraction it's just the base of the fraction yeah it's three and then you compare back end developers we have like six or seven so I want to understand where we are on that I think Tim was on vacation when I looked at his calendar so I don't want to keep dragging this Kushal so please keep pinging me but like let's do the following so that okay so I'm going to I'm going to take a to-do action item so paying Andre I'm writing something down so so Andre will have one on ones with Tim right so I'm going to ping the plan channel probably plan channel and I'm going to CC you so make sure that I do that like if you don't see something in the next like 12 hours hang me there again and then what I'm going to do is say Andre I think we need more you know front-end developers because our roadmap is amazing and we should move faster and especially Kushal says that we really need to fix this so I think you know whether we have a short-term plan or a long-term plan to address this I want to see if we can get more people working and so whether that's yourself working on this Kushal or somebody else I'll be working the structure because now that I already know what parts we have also so then like that that's fine I mean obviously I shouldn't care which I don't but I don't want to slow down right so yeah so so I would like love to have like an iteration even if it's a if it's a temporary one where we have we borrow another front-end developer and they're still moving ahead with portfolio management and you're guiding them but your heads down focus on the refactor like something on that I would be super happy about I want to see how possible that is and then we're still like a week or two away from 11.5 so I would love to do this in 11.5 and I'm sure that you would as well so I really want to make this happen I don't want I don't want like you and Fatih working on portfolio management and then just Constance working on plan but maybe we have to do that like that would be really crappy if we needed to do that so I don't I don't know what we'll do maybe that's not too bad because the rest of portfolio management for the year is like if you look at the 11.5 they're like continue like system notes and like other cleanup stuff so they're not super new things so maybe that's not as terrible so that you can guide the person yes so maybe that's a good strategy as we do cleanup or you're also doing refactors so it's not net new like crazy difficult new things and needs a lot of time from Pedro to review so maybe so I think we really should do it soon around later I mean for more reasons than that we don't work with that okay so yeah like keep me honest Kushal if I don't respond like in 12 hours or you can start starting messaging on but I'll definitely get to it today and then so we're we still have some time so back to the before I ran away 30 second really quick story this hurricane that was supposed to blow by my house never did so it's the one in the southeast us that you've been seeing and there's one in Asia which is affecting I don't know if that affects you Kushal but it's affecting some of my other families so it's really weird like everybody's getting blasted with various hurricanes but like this one didn't affect me it was supposed to fly by Richmond Virginia where I am at last Thursday Friday so that the town closed everybody was like off school but it was like we're like a really small town and everybody's really conservative and like oh close the schools and everything but like nothing happened so like parents bought their kids to like the museum I heard it but like the schools were closed it was really funny but then one day which is yesterday all crap went to whatever right so I can't use bad words this is recorded so like around lunchtime my time like crazy tornadoes and then touchdown at least one of them one I think when I checked the news yesterday one confirmed fatality and then like houses were like like being destroyed like for me personally I was like minimally impacted because I was working at home my wife was stuck at school she teaches at a university so she she came home like an hour late so also like that's not actually relevant to why I had to leave for five minutes but the power indirectly the power went out for like 15 minutes and then so so every like it came back on but then my wife was just going to work and then the garage door was couldn't like open because it's electric whatever so because everything was reset so then I ran downstairs and then like thankfully we got it fixed really quickly so that's my 30 second story so it was just really crazy last night I was freaking out but this is like after work like it was like crazy tornadoes and stuff but everything I think is done I've been checking on it did you get to some water bottles because I did that was that was the crazy thing last week that was the Thursday Friday where nothing happened so it was like Tuesday Wednesday the town was freaking out and then Thursday Friday nothing happened but like Tuesday Wednesday everybody cleared all the like packaged water so went to Walmart went to like a grocery on Tuesday Thursday and it was like all gone and then I went I think Wednesday night again or Tuesday night again and then reloaded and they had some so I still have a bunch of water and canned food that's that's crazy anyways so the sidebar so so what are we just going to wait for the design on Matei's thing or are we going to schedule some issues like what do you want to do Pedro from a design perspective on all that feedback and all that I think it's very if we close that issue out I know he's going to write something for the design system as well some guidelines so I prefer if we close that make sure that we because the last time I checked he didn't account for some of the scenarios like for example the error states that Michelle was just showing like for some reason you have a bad connection and it's not able to update the sidebar what happens what do we show and I want to make sure we have all of that accounted I know that he worked on some of the intermediate states so when some information exchange is happening what we show to the user but I think I have to review it because I'm not sure if we are being as aggressive in a good way as you were suggesting Victor which is to immediately show the change right yeah even if the connection is not working right we immediately show it and then we check for the connection then we check because I think it's better if we are if we make it really perfect for the most cases which is a solid connection we just show the change and then for other people that don't have such a good connection or for some reason it's an error state too bad but I think we should optimize for the best I totally agree with that but this is just to say that I don't think we should do anything right now right now but once he gets that in I think the sidebar is probably I know he wants to work on something for the settings pages like that's one thing and the other thing that we can do in the plant team once that issue is closed is then to create an issue where I can me or Annabelle we can follow through with those guidelines on the sidebar exactly the plant team covers a lot we have issues we have epics and the merger quest I assume a lot of the code is similar to issues so we should probably do it as good stewards of gilab anyways if we do issue okay so I look forward to that I also agree it's not with the system notes I'm not too worried about it it sucks but it's not like really super bad but it's also something we should fix because we've been living forever for issues and merger quest okay so that's I wanted to know about that one sorry I'm jumping around did we demo quick actions already? yeah we did so I'll watch a video if I didn't see it and then so the only thing I see remaining for due 22nd is the list views do you think we can still get those in by Friday or is that I'm not sure because it depends on the merger quest that is still in review and they are still at least on front-end side I'm not sure but on back-end side there is still database review pending and main review pending based on that we need to build the second one which still we need some reviews so right now there's only one MR or is there like two there's one MR that covers all the features except the list view and then we can't do the list view yet until that MR is merged or at least you want to know the results of what people are saying in the review and how to create it okay no that's fair so no that's otherwise that's great I think we're making awesome progress everything looks awesome and then let me take a quick peek at so if we look at our agenda and we look at I just want to see what's the rest of 11.4 so we have the view list and then the rest we have one bug which has been assigned to Chantel so it's not you too and then I don't think we have much more right we have the reigning date fields I think that's the other big one right and then we have the that's the error of the epic so I think those are the only remaining two things in addition to the view right which ones so I'm looking so let me share my screen I'm just looking at problem management issues for 11.4 so if you can so we don't have not functionality yet in the search right so I can't take away the do 22nd ones but you can filter it in your brain and so I'm just looking at what's remaining for 11.4 so this one is remaining but this has been assigned to Chantel so it's not Yarka or Kushal's responsibility at least this one is also Chantel's working on it and it's coming I think she might need some help but I haven't talked to her I just think that it's might be a bit tricky but this one okay that's fine yeah no no let's let's manage it I just want to just get a pulse on provided that these are assuming being taken care of by somebody else where like where do we stand and I think where we stand is this one do you anticipate this is like a big one Yarka or is it like it's just being blocked I think it's not a big one I think it's not a small one I think it's like something between but not too big I mean like smaller than bigger but not like small that you do in just two hours right understood yeah I'm just trying to see what's remaining so it seems like this is remaining and then this one right so there's a bug so bugs can be big or small like we found out with the attachment when it was really big but hopefully this is not too bad and then we have this one which seems big because all the auto complete stuff usually gets complicated when in the experience I've seen in the past year and then there's this one so are you folks still comfortable with the rest of the 11.4 yeah sounds fun seems okay right okay yeah no okay that's all I wanted to check in with you folks on but that's all I have anything else you want you folks wanted to discuss no alright alright so I will put this on YouTube again if there's no disagreement and other than that thank you for your time and we'll chat in Slack and I'll do that thing first because I have 15 minutes until my next meeting so I will chat in that thing go ahead Pedro just one final question so regarding that issue of refactoring that Vishal was showing I understood two things so one of them that doesn't have to do with refactoring would be to somehow discuss and talk with him about the necessity of having more front-end developers for planning right yeah yeah it's I think it's a great opportunity to illustrate to people like Andre and people who hold the keys to these things to say that you know this is really important this is an example of why we need more people yeah that in that sense it's related but if you're alluding to the fact that it's not technically related because we always need more people yes I mean we always need more people but I think a good point about it is that Vishal created this awesome issue to refactoring to restructure and make sure like we have a solid base to grow on and it should be done because even with three people if we are only focusing on new features and doing new things and not looking back and making sure that everything is okay for better growth we're not going anywhere right I think we can all agree with that yeah well we don't have to argue about that until we have to it is my response like you're saying like if we don't get the people we should still do it is what I'm hearing if we don't have it yeah I mean you're arguing that we're going that we could be going faster and that has to do with the fact that we don't have more people but at the same time even with the people that we have it's difficult for us to afford allocating someone just for the refactoring of something which I think we should do like it should be a balance and even if it's only 20% of Vishal's time I think for sure he should be doing refactoring of things that he did in the preview release or something like that and I mean that comes back to my earlier question with Kushal like can we split it up right so yeah if we can split it up then it's a little easier to manage in terms of risk right like not risk of not being done but like risk of where we're not shipping new things you know we can slowly get it in and then we're still moving forward with the product we're still getting feedback from the community we're not slowing down sales folks still can sell GitLab that type of thing but because this is a big thing there's immediate risk with it so that's why it should be managed as such but no I don't disagree with anything you're saying at the same time I think we should keep this is also to keep people happy at plan right Kushal created this issue because he feels passionate about it and he wants to have like his desk as clean as organized as possible right so one way to do it and if we if we always have to push forward because we lack people because we lack a lot of things yeah it's not going to end up as always it could be so yeah Kushal go for it I encourage you to maybe break it up in smaller tasks or something like that but have something I think it would be great I'm just saying this but Victor has that's why we're having this discussion I understand like in order to get this prioritized and presenting it from the product perspective like hey we are planning to do this refactor but in order to basically sell it it would make sense to have it broken down into multiple merge requests that can go across the releases so what I'll do I'll do the technical breakdowns the immediate thing that I can think of just thinking out loud is that what we can do is we create the shell part first instead of adding all the items in the sidebar and call it one merge request and then we do another merge request that would add all the sidebar items and then we do the third merge request that would add just the tests of the entire app and maybe break it down across three or even four merge requests and then push it out every release and on the fifth iteration what we do is that we combine it all and basically close this meta issue in a way yeah well just creating an epic I mean I can create it for you if you want to do that that's also great I mean that's better and just curious in that case would you have both apps living in prod at the same time yes because the new one will be turned off yes can we even test it in prod could we just type something in the console to turn it off yeah I'll make sure like the toggle switch is easy for anyone to just that's great that's independent of me bugging Andre for more capacity that will definitely help I think as Pedro was saying that would be great thank you yeah I want to see more I love when people like suggest like we should do this refactor or we did this on this release but it could be better I know we can do better and I love it when we have this issue so I think we should do it more and like each release have something that we are working to polish a bit more because we're not satisfied with the quality that I think that puts a high standard and it's a good example for everyone on the team and also for outside of the team to the rest of the company so thank you Kuchal yep thanks Kuchal thanks Pedro alright we'll talk next time then bye everybody bye