 all right so we are recording and so any updates on 11.4 before we oh sorry the demo stuff but let's do that first I can do it first I have it prepared this time so yeah screen here so I will first share the autocomplete commands for epics so right now here I'm in some epic come on yeah okay and now when I click slash I get some commands that are supported for epics so I can try to change title to title and additionally I can close the epic and you can see when I reload the epic is closed and the title is here so that's simple and second one is the short references we have sorry yeah do you have system notes showing for closing no that's out of scope for that issue okay okay we have funded for next release I think okay thank you and then the second one I have to switch branches okay so I have to go to issues now it's really cool so yeah sometimes it's slow okay finally so now I go to some issue and you can see that I can use just short reference here and that links me to the to this issue now not on to this issue but to issue 5 in the same group slowly again but you can see here that's the same group epics and it's epic 5 if I write the whole URL it will be rendered as short reference again and I can also use it for assigning this issue to an epic so it's it's been added to this epic yeah and that's it and this is the notice created on the other side as well yeah that hasn't been changed so it should be if not then we have all bug there but let's check yeah it's awesome yeah and then there's a bug that was when I bug I don't know if it's bug that's been fixed to the that the link on the other page that you were just at your chrishanta I think it's that one right that that being a link was this link yeah this link is wasn't a link before or it's not a link in production it's no link yeah yeah yeah you can see the first example like the first system notes there a week ago yeah yeah yeah exactly yeah so that was change merge recently so that's great okay so awesome one side if you don't have any questions any anything else from you kasha or should we move on to look at the point for stuff so no the epic that I created to do the refactoring I already mentioned it in our channel like I broke the entire effort down into four issues and I have scheduled the very first issue for it in 11.5 so what we'll be doing is that we'll be creating the shell part and I've already discussed the approach of how we want to architect it with Phil because as you mentioned both me and Phil in the issue where the sidebar concern was there like we are not having a unified sidebar across all three contexts so the idea of during the epic refactoring is that I'll be creating a shared sidebar that can be reused for both issues and MRs at later point but at least we'll get the foundation late for it so that we have a sidebar to begin with and then later when we do schedule the refactoring of sidebar for issues and MRs we can reuse the component as it is so that is the only update so I already started working on that shell part and as a part of the first issue I'll be doing that develop develop a flag as well which would basically allow anyone to test the new app locally obviously it will be turned off by default at least for 11.5 and once we have the entire thing ready then just sucking the overlap that's great that's awesome thanks who shall so yeah no let's revisit that when we talk by 11.5 in two seconds but really wanted quickly to confirm this is Chantel was having some trouble with this so I asked her just to talk to Sean so I don't think it's for you or she might have talked to you already Yorca but don't worry about this one so this one these two you just demoed is that correct Yorca is that what these two are oh no this one this one not right but this one you just demoed this one so this will be closed when the code is merged right you're mute Yorca so I demoed both of them the quick question to add a shoe yeah and the support auto compete for epic script commands as well okay all right this one is the when you do the slash and then yeah exactly yeah and then you did more for this one so that's great well we got some stuff for free so that's awesome well I didn't do anything it was just for free okay but so so you don't see any problems of these being merged in six days okay cool so we should be able to wrap up for that's great so let's moving on to 11.5 I put some do let's look at let's look at the first half first so this one let's see let's look at you have this in the board view or yes I don't have it right away so but I think we should we should use the board view so we feel the the plane it's necessary yep I oh I don't have it in this one but I can create a new one right away but let me double check okay okay if you don't have this it's okay specifically for portfolio management yeah that's what I was saying no but we can do this right so we can filter it yeah yep cool so really good okay and then we also have this but yeah so these are the due 20 seconds not much order in the priority order but a big yeah especially since we're a small team but anyways so this one's really straightforward and they're closed up X with closed in markdown so this is back end I believe notifications is a pretty big one yeah I would suggest moving item notification or promote issues to epic to the out of the due 22nd because both both are quite big both are quite big right okay so so this one I would rather keep I would rather move this out of the 22nd okay okay so let's do that okay so this one involves yeah so there's a lot in this one right so there's closing and reopening and then right now yep and then also the custom yeah and then there's API so the web so there's a lot here okay so that that's that's this one that is now I'm not here anymore that's fine and then we have system notes that Peter just mentioned we have to fix we have and then we have this one and the one after so let's talk about that secondly and then so we have promote so promote we have a lot here and so if you look at the so there's a lot of things to do right for promoting so what we want to do is just the very thin slice which is just to copy the title description and activity thread so I'm hoping that this can be very light on the front end so there's a there's an ongoing discussion about the design so one really basic design is just to reuse this for promoting and then if we do this then there's hopefully very little front-end work and it's mostly back-end work well there's going to be a lot of back-end work regardless right because you have to do all this but then the front-end work is we're talking about how that can be done so I'm thinking we can maybe do this as a first iteration and then change a styling later when we do like sub-apics and stuff like that but we could we have ongoing design discussion there so so that's that one so let me let me pause there Yarka is this like a as a like back-advised is this like what do you think about this one I don't think it's that complicated but I think it will take some investigation was the best way to do it and to actually do it and because it will probably be new services and new I don't know if API is actually in the scope of the issue no no okay so yeah I don't think it will be that complicated but it might involve a lot of discussion during the review and also there might be some unexpected things because of group versus project context so right right okay make sense yeah I'm just looking if we have API we don't have any have API here yeah like the same thing goes for the front-end part as well like as you show that the button would reveal two options that is moving to a different project or promoting as an epic so to have to see how much of the sidebar implementation that we already have can be used for the view app that we currently have right so again requires investigation I'll have to see how the sidebar has it okay yeah I definitely don't want to get bogged down with the sidebar or the front-end in general for this one because we are well if there's like if Pedro and Enable are able to come up with something that they're comfortable with that we can reuse like for sub-epics and like I don't know right so that that's why like I don't want to like spend a lot of time creating something that we will change very soon so like if it's literally just another button that here that says promote issue I think that's good enough for this iteration and then and then we make it awesome later on so let me let me tell you what I'm saying here so like if you look at this this is how sub-epics may look or will look or whatever right so there's this there's all this stuff in the middle right which is you know it's gonna meet or that's something of this right so you know save a little bit more room but you know basically the meat of the design is is this stuff in the middle but one thing that Enable design is also the stuff on the side so you can see your parents right so if you can see your parents to me this is very similar in concept to promoting so like if you have this and then you have no parents maybe you can reuse that or like how does this look in relation to having buttons here that's a move issue or promote like to me it's all related when you have this type of view and then you have an act you have a button that will essentially change this so to me there needs to be a lot of design consideration in that and so if that cannot be because I even if we come up with something great now I'm sure as we implement some epics it's we'll realize some things as we get feedback as we use it ourselves so that's why I don't want to spend like time making it perfect and then and then having to to rip it out again so that's that's just my high-level thoughts on that yeah I think I think we should do it this considering what we want to do for the future as well and that tree if we're going with the tree as well I'm just really not comfortable with putting that button down there if we're going to put it there it might as well we might as well just have a quick action because I mean we're going to do the quick action probably so to add a new UI element that we have to test and that it's really I think it's a really shitty solution in terms of like hiding this awesome feature down that button which you have to click to even discover that it exists I'm yeah I think we still have to to work on it but but yeah I agree with you that we should do this in a way that if when we're going after the child epics and parent epics and all of that tree we should do this more or less knowing what we're going to do we can do so would you rather just do quick action we can just throw this all out I mean we haven't started it yet we can still do we can still do everything here if you look at it right we can do everything here like the first issue has UI on it right now because that's like the first thing I thought of but we can change this to a quick action and everything else has this has no impact because these are just like backend things that change right maybe we have a banner somewhere right but yeah I mean that I think the the quick action is something that we probably do so I'm saying that let's do that first something that is sure right okay and but even what I'm trying to say is that's because the the milestone oh okay I see what you're saying because if we have we make this quick action then it's he waits to this and all of that let me talk with let me talk with Annabel about it today and see if we can come up with a solution for it if we see that we still need more time to think about it the quick action is something that we know works you know right so let me know sorry go ahead Pedro no no no I was yeah go ahead no no okay yeah let's how about we just decide that this is a quick action now and then if you come up with a design alternatively then we can say okay let's do a button instead that's a better experience blah blah more discoverable you know quick actions are pretty discoverable now as well but you're right like having it down there is like as non-discoverable as a quick action I mean I I even think you have a slightly larger resolution than I have so even you had to scroll to see that oh yeah yeah and and it would be hidden behind the drop-down and and yeah it just doesn't make sense to me it's it's like a boring solution in the sense that we are using something that is sorry there but I think that we were using something that is already a bad solution you know I mean so when you compound that bad solution I think yeah so unless exactly let's we come up with let's give credit to Pedro no it's it's fine unless we come all thinking about with better web UI solution now let's do quick action for this issue so let's let's go so if we do this then there's no front-end right is that is I correct your and Kushal like if he just exposed the promote part as a slash command is it yeah yeah in that case a front-end wouldn't be changed because the back-end commands are pulled and exposed to purely via back-end so it would just be an addition to the list of existing commands that we support for any issue so that would obviously won't be impacting front-end in any way right and then everything's well-defined they always have to think about these with ethics in that the parent parent issue parent group is well-defined for issues and not the reverse so promote issue and project to epic and group you can promote only to mirror blah blah blah so button UI so quick action using quick action maybe we could also change the title oh it's already been changed so yep so this goes like this yeah cool thank you old UI so great so everything is safe we have here okay so that no that's good I like that idea so then that's makes a little bit less scary oh a lot of things disappeared I don't know if that was correct this one got okay that was weird blah blah blah and then this one we have until what time okay we have no okay so this one should be only front-end is that correct uh kushall yes yes it is it is purely styling change okay and then I think so so I read a couple of issues so Pedro did you want this to be okay I remember so you said you wanted related issues to be orderable later on right yeah yeah to use the same to use the same component or whatever like to make it easier but but right now for for this issue let's let's not do that let's just to the okay the front-end and okay so we can yeah we can discuss that separately if we need to make it I don't think anybody's asking for it to be orderable though right so that that's my point but we can discuss no but no but nobody's asking for it but what we thought I mean this is this is open to the discussions yep still because we we're not going to work on it right now but it might even not make that much sense code wise to maybe they won't share anything I don't know okay what what what do you think kushall do you think related issues and epic issues being both draggable and and reorderable is something that is better front-end wise does it help somehow to reduce code or not so in epic so obviously reordering the issues does make sense because in that way we could prioritize which items to be first based on the order of appearance but in case of related issues where we open any issue and then add a bunch of issues which are related to that particular issue I don't think people are considering any kind of order there they just add based on whether they recall whether this particular issue is somehow related to this correct so but at the same time appearance of both the ui's within the epics and within the issues is exact same I wonder how users would perceive it because if they are able to drag and drop issues to reorder in epics but if they couldn't do it in issues list and it would be confusing for them like it looks exact same it is exactly the same but I'm able to reorder it in one place and cannot reorder it in the other place yes so what we're what we're arguing is that in terms of experience it we don't lose and anything so it doesn't hurt the experience that both lists are sortable even if people never use that feature for related issues it's there you know it's something that I mean it doesn't hurt but we what I'm asking is for in terms of front-end would it help that it's also sortable or would it actually create more codes and more logic just to make related issues sortable no as far as quality front-end is concerned I think it makes sense to have consistency in both the places because we'll be able to share exact same app in both the places right now I believe that we still do like the exact app that is used to show the list of related issues be it epics or be it within issues it is exact same but I think due to lack of back-end support in the issues side of things we have turned off the reordering part because chances are that API doesn't support reordering at all which is why we don't have the ability to drag and drop issues within the related issues list but yeah if API supports it for the issues back-end then we might as well enable it for once and then have the consistency okay so yeah essentially what this looks to me is that it's basically a conversation that I mean UX wise I'm up for anything so if we can make it consistent it's it's great if not okay it's not that terrible of a loss but I think it's a conversation that mainly needs to happen between front-end and back-ends because if from front-ends you are arguing that for you it could be easier to maintain just a single component for both epic issues and related issues what would be the effort from the back-end side if it's if it's a really big effort to maintain the sorting for both lists maybe it's not a bridge that we have to cross right now I don't know we don't we don't have to decide on it yet we can discuss we can discuss yeah we definitely have a space to discuss on the issue of this one the follow-up ish I know sorry on the follow-up issue here for this one so we can discuss there yeah but yeah but Pedro I want to I want to get the discussion further beyond related issues and epic issues and I think the issue or the discussion should be about this right mm-hmm like how does this look so that's why I'm anxious for these designs to proceed and have you an animal drive that because to me that that's that's obvious what you just said but it will change again or we should know the design and the intention and so for example promoting issue like I just mentioned there's a stuff in the tree that's not clear how that should look this is like we have some confidence that some epic should look like this but what happens with some issues and what happens with blocking issues I don't even know if it's linked here if it's not that sucks I should make it yeah but it's here right so we have some issues and blocking issues which like we don't have any designs for that yet mm-hmm right now in theory each issue could be have three types of relationships related blocking and parent child and so do we want to keep all three how does how should that behave and then that will super impact the design of this so I think if we have some clarity on that then I'll be a lot more confident to say like oh like how should it how should it you know move stuff around so I'm interested in that as well because I think it if it could all look like this somehow that'll be great and then you can just drag it around I'm in a system but I don't know if that's like my immediate design would be like you would have like three tabs like you would have like like children issues you would have blocking issues and then you would have related issues right but maybe that's a bad design and they should be ram together so how that would work go ahead so I had I had one quick question like when we show this kind of free in the nesting way is there a limit on which how much depth would help there's well I think I think animal wanted limb constraint here I think right now our current thinking is that we just show one level deep and so you would only show this one this one and this one and you have to click further to go down I think that makes sense because then it's scalable and stuff like that and then maybe you have a button that says expand on but like as for me it's a safe first implementation is you always show the first layer with the Chevron and then you click to get to the deeper layers but again that's like the type of discussion design discussion we should be having now upfront so that we can we can always be aware of like stuff like this moving around because it's super relevant like like can you move this whole thing around right you can move like we were I was thinking about moving like parts of a tree and then you move trees around and then you have like AVL trees or all these stupid computer science trees where you have balancing and stuff like that so you can get to some pretty crazy use cases so we need to know those designs up front and talk about them yeah that's how I wanted to bring up but yeah back back to like next iteration is definitely just this one which is great and then what's next we set promoting is a quick action and then we have some more I think cleanup work mostly which is great we still don't have the logic operator so it's hard to see but if I'm looking at this we talked about this one we talked about notifications and this one Pedro said we should do so it's should definitely do this I'm assuring the dates here so fully that's that's not a big one and then before we talk about auto complete what is this one I get this is too confusing but this one right so this is auto complete on the epic itself so we don't get this yet right Yarka this is like we have to do this well I think someone else from the company will be assigned to it because all issues that I'll be working on are assigned to me already so okay okay but we don't have it yet and I think it shouldn't be that complicated but okay yes okay yeah I know just wanted to double check if we're missing anything but sounds like that's good so yeah no no just double check you're already assigned yourself these ones that's great and then so there's this one needs some so there's a lot of messiness with this yeah and so do you mind you mind updating this one whenever you can yeah provided the the other issue has been the design has that's maybe we should link oh right okay oh it isn't because it's exactly the same image so I thought it was the other one yeah exactly so okay yeah so we don't even know if this is done yet so it doesn't even look so the order issues merge requests I don't know I don't have any idea if it's being done or not I haven't been pings in any requests for it it's like it's Andre working on it right but but even I mean I don't mean we were in that discussion we're just talking about the icon and it doesn't mean anything so even if even if we implement the wrong icon so to say we can change it so it's not that bad so but I don't see any activity here in terms of development I don't know okay no that's fine so I think we can proceed with this one then because they're independent like we have this as long as we have this consistent design and I think this one doesn't add the back end support yet or the back maybe yes we have this one for epics and roadmaps and then yeah so right now in epics we don't have direction right we have just right we have just one direction and then this will add both directions okay so that's great and then this will save it to the backup okay yeah no that's great that we have this one scheduled all right that looks good to me any any gotchas there Kushal and Yarka for this one you see any problems with that no okay and then so this one and this one Yarka said well another back-end person will be assigned as well as this one is there back in is there front-end work for this one or is this only back-end work that is front-end work yes okay and so so Yarka you've assigned whatever you have capacity for and then it's up to Sean to schedule the rest or assign the rest yeah exactly okay great thank you and then Kushal for you I don't think there's anything that's not deliverable this one this one isn't not this one's not not deliverable for full management there's a couple bugs and stuff again that these have already been assigned to okay so there are sorry there are some non this is a migration this is additional work that okay so this is this is more of the same that's great auto complete same thing so Yarka you assign yourself to one of them and not the other one epic attribute we talked about that one already yeah this is the other it's another one I think it's the same thing thought this was 11.4 but whatever do you go ahead Pedro sorry I'm yeah I'm just sorry are you are you going to put the deliverable issues or no no it's still in consideration yeah yeah these are these are non-deliverable the ones that are non-deliverable are non-deliverable again I can filter on non-deliverable so that sucks but there's like maybe three or four that are non-deliverable and then I think I'll leave them but I guess the question is for Kushal is there too much too little here and I don't think I thought you said you you did schedule or it's we're missing some labels on the you said you had at least one right for the oh it's this one right oh no it's not this is back in a Kushal didn't you say you had one for the sidebar refactoring yes but I haven't scheduled it for 11.5 okay so you're gonna go ahead and do that right you're gonna have one of them so the one that I have scheduled should be listed in this portfolio management list already let me share the link directly to the issue which I have already scheduled for 11.5 okay because that will be taking some time and the sidebar thing is something that I wouldn't schedule it but would still try to cover it halfway through if it is possible and have the branch pushed into the GitLab instead of you know getting it merged into the master because if I have the bandwidth once I have finished all the e-deliverables for the release I can focus on that one because I don't want to prioritize the refactoring over the actual right right that's fine yeah yeah of course of course but but at the same time do do schedule it to 11.5 so that yeah so that you know managers can contract it Andre and Sean so so anyways these are your work and then that's your crucial is this like too much this is a quite a bit right well I mean no they're they're all here they're all under this one so is this too much too little I don't think you're gonna complain that's too little is this is this too many issues or are you comfortable with this I think it is doable okay we have this thing where like for back-end I would definitely yeah yeah no no I assigned myself to issues that I am comfortable finishing and other issues Sean has to Sean will do yeah yeah okay and then did you is that what you linked this one sorry my turn okay okay no no that's great so okay that's good so with 20 minutes left okay any other topics before we close just wanted to show you nothing urgent okay so so I wanted to always show this more or less every time so this is where we're sitting at and so we have we have if you look to the end of the year this is where we're at promoting issues there's all those things there so that's why the reason it's taking so long because I put one issue in each milestone essentially so we'll have the feature hopefully after this iteration and then we'll be cleaning it up I mean that's a terrible way to put it but we'll be improving it step-by-step this one is gonna take some good design but I wanted to highlight as well this make easier to use one so let me okay no no this is this is almost done that's great but this one this one I wanted to alert people to because I'm putting it here for 11 7 right now so this is basically when you have an epic you just click this button then you add an issue right so you can just type the title and click add but this is exactly what I didn't think about previously because when you're in at the group level and you want to create an issue you can't you have to you have to specify a project right so this is exactly what we have for a group board so I thought this would be like super easy but it's like not super easy great because if you have an epic here you can just click new epic and then click that and then add it to the epic right but for for create issue like inside the epic itself you have to also specify the project so there's like then you have to know the project and then you have to load a list of projects from the group so it's not really really straightforward in the sense that it's sorry let me show you what I mean we have this feature here which like this right so you can choose a project and then click that and then that will do this right so I would like something like that but for for make it even easier so so a better example is the board so such rating board sorry so if you look at the board if you look at any board you can do this right now right so select the project type the title and then submit issue and then that would create it and then attach it to this board by pre applying the label so we want to do that for at the epic level so I wanted to mention that is in my opinion you know what would be awesome is to go ahead Pedro or you're coming in and out you just said you know what would be awesome and then you put us sorry my internet is really bad my internet is really bad so I'll say it I don't know if you hear me or not but would be when you're typing in that title input instead of just typing the title you could type the title and then you could put labels and milestone and whatever like quick actions and then you press enter and it has all of those attributes that's actually how I use my personal task management tool which is remember the milk and they have this awesome like why put where you can type everything and you type it like with parameters but like you would do in the command-line interface and they just create the tutus for you with whatever being so and if I want now I was just going to say that if I want to add a description to my task what I do it at the end I do double slash and then I start typing after the double slash and so essentially you have this command line interface in a single input that allows you to do to add issues really easily and it will be awesome to have that not only in the boards but also for example in this list of issues we are having to go inside of an issue just like type enter and then it's automatically created so essentially have a very fast way for us to create issues we are having to go through this interface similar to what we do with chat ops and things like that yeah I just wanted to say this yeah that's great yeah that's what I was mentioning like when we create issue or MR we can use description field to put on all the slash commands that we support like instead of opening the labels drop-down we can just while writing the description we can use slash label and add all the necessary labels that we want to use for that particular issue along with milestones or assignees or weight because all the slash commands that we support in typical comment field are also available in description field as well so in that case we would basically just remove all the knobs and buttons and would replace it with a particular text area where everything can be used by a slash commands is that what you perceive Pedro no what I was saying is actually have just one input so we wouldn't have to switch inputs and it wouldn't be like a text area it would be like if you type a title and then for some reason you mentioned someone that would be the assignee it will not be a man if you add a label there in that in that single input it would be added as a label it would not be text rendered in the title you know what I mean so essentially you type the title first and then you start adding all of the attributes that you want in the same wine yeah no I I totally agree with you Pedro I really hate this page and I want to get rid of this page the page you see on the screen if you if you can still see our screens Pedro but the new issue page I think it's a horrible I can see this with the delay right yeah yeah it's a horrible page in that it's there's a lot of friction people have to read a lot of stuff it's also a very powerful page so it's one of the reasons people won't let us remove it but I think what you're saying or what's resonating with me at least is that when you create an epic it's the easiest thing in the world because the only thing that's required is a title and same for an issue but we haven't implemented it for the issue at the project level but I really like the design of an epic creating epic is literally that's all you need so to me it's we need the simplicity of this but with the power of like this right the actual issue page and like what you describe one design like you describe this having one text box and you can enter like slash commands or quick actions as there's supposed to be called so I think I think we need to do that and figure that out so if you have great ideas of how to just get rid of this new issue page or a better way to do it very in various places I think we should do it but for the for the context of adding an issue to an epic what I don't like is having to select a project along the way to do so so if you have a great design to get rid of that or make that really less annoying that would be great I can't think of one you still have to select a project when you create a new issue at the epic level when you click on any epic and you want to just add an issue to it really quickly you can't so I don't know what to do so maybe it picks a project for you and then you can move it or I don't know but it's just annoying that you have to pick a project I mean it's good that we already pick the less selected projects in the issues list so that's last bad but I also don't know how to solve that without relying on people remembering the which which is the the the path name exactly the project slug and things like that if you if you check that link that I put in the chat it would quickly show you what what I was sharing and how it works it has like all of these steps like the first one is the title right and you can add the do they priority and then all the way at the bottom you see how everything can be done yep yep this is great this is just yeah so this is combining the slash command into the title field itself I mean that could be like a yeah and then just press enter and it's done the task is added this is what I always do and I actually use this with Alfred plug-in so it's it's like similar to spotlight so anywhere I am in whatever app I just open and it's connected to the API so I create tasks for myself using that kind of yeah no this is this is this should be a feature request and if this and there should be a so support quick actions in title field so in epic's issues MR support quick actions just like this app use case sometimes in good lab you can create an object without the description box so we should support I'm just gonna log this issue I don't think yeah right away there as well I don't think we can do it right away well I don't know maybe we could but there's like we should just log these ideas in general okay anything else before I think a big yeah sure no no this is I think this is a good idea I like it because I any any way to get rid of or to to get people to stop relying on that new issue page which is a pain like another concept I have is that when you create a new issue it's like it loads and then there's too much crap here like making this hidden or like making this not a new page or like when you click this it's like a modal pops up or anything like that would be would be better than right now this is like a horrible experience I think it's the only place in the plan team if you think about it where it's its own page because since we don't do merger quest anymore we don't have to worry about the equivalent merger quest but if you think about in the rest of plan like if you're in the plan team which people are on this call look at all the things that you're responsible or we're responsible for there's not a lot of pages where we have a new form or like an edit form and the places that have this are issues labels and like milestones right so so with labels you have this really horrible thing where you do like this I hate this page like why why do we need this page right and then milestones are marginally less bad because you can you can there's content in the mouse on itself right so usually you can't get rid of list page so but you have this and there's content so it's less bad but this is a terrible page as well so we have like only three of them which is not that bad there's the label there's the milestone and then there's the the new issue one because we got rid of the edit issue one if you think about it right so that's also awesome right and we also we never had the edit we never had the edit epic one so there's no edit issue page right we just have this which is super awesome right so any ideas to get rid of those three legacy horrible experiences will be great because then like I think merger quest merger quest definitely has and it's a lot harder for merger quest to get rid of it because there's like four or five states with crazy merger quest with like branches and stuff like that and then there's all these horrible settings pages and I don't know the rest of the lab well enough to know like those things but I really hate these edit pages because it's not it's not a web app it's like a website which which sucks okay so I'm done my rant any anything else stop sharing if not I will talk to you folks next time you thank you