 Welcome. This is the Jenkins user experience special interest group. It's January 4th, 2023. Happy New Year. Topics that I've got on the agenda. Security reviews for UX poll requests. User feature flag status report. I don't know without Vodak here if we'll actually do that one. I'm going to move it to the end in case Vodak doesn't make it. Yahoo UI removal. Tim, is it okay if that one's on the list or would is there anything you want to put there? Nothing to add. Okay. All right, so take that one off. Feedback on UI on UI UX regressions was a topic last month so I brought it forward. Keyboard usability was a topic last month but I wasn't sure if there was anything we needed there. And then I assume what's next in UI and maybe we should have should we have a topic that is what's happened recently in UI. Because we got a bunch of interesting poll requests merged in the most recent weekly. Any other topics that you want on the agenda? Okay, then let's go ahead and get started. Are these topics okay? Are they any that you would recommend someone wants to recommend? Hey, drop that topic from the list. Okay, then let's start with the list. So security reviews for UX poll requests. Tim, this has been an ongoing question we ask each month as we meet. How is it going? Is it working? Do you have any insights you want to share there? I think it's going okay at the moment. There's just one waiting review at the moment. Only one that is a waiting review. Okay, good. So the security team is keeping up and it's not, there's not a large backlog, particularly with the end of year holidays. Having one sitting in review is not terribly surprising. Okay, good. Anything else on that topic? Okay, then let's go on to the next. How to collect general feedback on UI and UX regressions in the last session. The discussion had been around. Let's see where was it. Maybe I'm off base and even creating the issue. Oh yes. The question was JIRA issues, new issues with appropriate labels and cleaning up old issues. Any comments from those in the in the session about about the topic is we're currently using the regression tag or regression label to flag all regressions right so whether they're UX or not. The only issue that I've seen has been adding the regression label before something has been triaged. So the most efficient process that I've seen has been to, if you're reporting a regression to also triage it at the same time and find the original commit that introduced the regression. And also to comment on the original change. So that kind of starts the process of discussion and resolution as quickly as possible. But when that isn't, when the original changes and known, there's some work to be done to discover it. And so the, I think what I've been doing is using the untriaged label the UX untriaged label to indicate, you know, hey, there's more bisection that we need to do before we can identify which change caused the regression. And, and are you finding that's working I'm a little worried that the UX untriaged label may have quite a queue. Certainly, if the submitter does the bisect, I can see why that's the most efficient that then lets others immediately say oh, what shall we do about this. Whereas if somebody else has to bisect it's there's real work to do the bisect. Yeah, there's real work either way. So, it's just a matter of finding the time to do it, but it's it's important to be it's important work to do. Okay. Any other any other I'm not sure what more to go with there will continue it sounds like we'll continue using the UX untriaged label will continue encouraging submitters to do the bisect themselves. So that we identify which exact commit. I guess the other is we continue encouraging people to use small commits, so that the target of a bisect is is a relatively narrow scope change that if it had to be reverted could be reverted without major damage to other things. I thought back I had offered to provide help with people who are interested in learning how to do by section more efficiently. So over the last few months I've come up with a process that works pretty well for me at least. For example, you know I skip compiling the tests because you don't need to run any tests when you're bisecting so I figured out kind of how to make that feedback loop as tight as possible. So if there are, if there are people that are struggling with, you know, learning how to do that I can definitely help people out. I think that would be a good thing for the docs, Kevin, Kevin, I wonder if, Basel do you think that's something if you and I did a session or you and I and Kevin did a session. We might consider asking Kevin to do some writing to describe the process and put it in the developer section. That could work. I'd be more than happy to work on something like that that sounds like a great addition or that something that would be really useful going forward so. All right, thanks. Okay. Anything else on the general feedback on UI and UX regressions. Okay, next topic then was keyboard usability and I think this was Christina, and Christina is not with us today so I'm prone to move this to the end of the list are there any others who had topics on keyboard usability that they wanted to discuss. Okay, so I'm going to take that out of the list then. Next topic then was what's happening recent what's happened recently in UI improvements. And here the thoughts that I had where we could look at the, the most recent change log from Jenkins.io and see quite a number of places where where there have been improvements added. Are there any things Tim that you would like to highlight. Do you want to show your ones first. Well yours are more truthfully yours are more valuable if you've got anything you would like to share I would rather go to yours first mine are just looking sort of at the history. Yep. Let me just check weekly. There's some plugin updates. Looks like someone's been too quick updating plugins. Just give me one six if I've got. No, I don't have it quite ready. See what else I can give a reason and give a quick demo. Okay, so I'm going to stop sharing will let you switch in and take up the demo. Okay, so. I need to allow zoom to get to my screen, which probably means after rejoin. Okay. Okay, can you see weekly.ci that you can start. Yes. Cool, so. Okay, so a few things when the last couple of releases. One of them is that console log and a few other pages have now got a read crumb. So it goes all the way over to console output rather than finishing here. So it's over a number of pages. But that's kind of a prominent one to show. The advanced button has had a facelift. So you first show. See I do you can say. So this is on the LTS version. It's only advanced here. I just create a dummy freestyle and delete it. Okay, so here you got this advanced button here with the dot dot dots. And if you'd modified a field and then saved it and then reloaded it, you'd also get a little. Okay, in some cases, you get an icon next to it that showed that's the fields inside have been modified. So in here, just to show them. It's changed from advanced dot dot dots to advanced with a little arrow, which changes depending on what state it's set. And then there's a little icon that goes next to it when you've modified the value says edited here. The total tip. Nice. So now I can I can go. I can hide advanced again. I can hide advanced whereas before I had no way to hide it except to save the page and return. Yep. Yeah, exactly. And then the button will stick around and then you can hide and reopen file upload has has been styled. So rather than the default browser styling, there's now a style to look like a rest of our buttons. And there's a new jelly component as well to wrap that up. Management links have now had badge items icon support added. So if you have any plugins, if someone hadn't been so quick updating plugins, there'd be a little badge here showing telling you how many. Sorry, does anyone on that one might not be merged yet. I think they want still open. Yeah, okay, yes, one of them still open. So it's not managed not on the badge. So on the management links page badges now a component previously it was added. definition just for managed plugins. Now it's a component extensible component that anyone can use on the managed Jenkins page. So it's currently used for managed plugins and for manage old data. There will be a count up here and a tooltip. And there's a request which also adds it to the managed plugins page on the right here with accounts showing how many available plugin updates and also makes badges available in the context menu. And so it's not just in the plugin manager it's a it's part of our task so anyone using our task can also add a badge as well. So, so on this page for instance would it be within your, your idea of how things should be if the installed plugins had a badge that said how many plugins were installed or how are there some things you can highlight of ways. We should be considering using these badges to make the experience better. Yeah, some guidelines in here. So, yeah, don't overwhelm it just use it where it makes sense. So wouldn't put badges on everything, but just say like, if you've got an admin mantra up here there's already an example of a badge like concept, which shows you like a notification count. So, so it would probably not be wise that implied labels plug in puts up the count of label implications that have been defined that's not actually that helpful. This should be things that are that are quite valuable to the user before we put them on a badge. Yeah, there's a in the prototype there's a few examples and of some badges as well on the builds card. So here's like a kind of different sort of badge concept but kind of shows where the pushes came from so just the shows that it was a push from GitHub. Whereas this was a build triggered by myself. Yes, that's a different sort of concepts. Not sure if there's any others. No, I think that's the, that's the only one. Apart from that, there's a couple of bugs fixed. When you apply changes no longer prompts you saying, are you sure because you've already saved it. And we've reverted the label destructive buttons dismiss as the with the current button design the admin the admin monitor contrast just couldn't really work with with the buttons needs a some sort of tweaks or button changes. But there's no there's no small fix that we could see previously just a couple of minor fixes that have been open for a while we when you collect collapse the build queue so build executed widgets. It was this was completely misaligned so just such a recent bug fix it used to touch the side probably still does on CI if you collapse this pain here. So just touching the edge so the recent but recent bug fix fix that. I think that's about all that's came in recently was two weeks ago. There's now symbol AP symbol Java API for declaring symbols for using symbols and Java code. So I think really is using that in his plugins. So you probably saw here that I was using. Well in the design library you would have seen that I was using the search bar component. It's very nice just when you come in here so files not in there yet but so there's there's now a search component that you can use and sports icons as well. To rather than scrolling all the way to the bottom of the page. I think it auto focuses as well so soon as you arrive on here is tight validation. So that's a new component which is also being used on the managed Jenkins page. It's registered on this keyboard shortcut so you can just type log and go to that page. Okay so the that that search I had not experimented with yet the search on the manage Jenkins page is looking at all the things in that context. So if you type load statistics it would write okay so it chooses those items. Yeah, yeah. Nice very nice. Yeah, and there's also possible improvement for later is maybe drop some of these configure words as well as we noticed when developing this is a lot of configure. And I could probably just be changed to system tall global security credential providers. Look at that later. I think so that's just going back through the last few weeks releases. The typical request was finally merged. I don't know if we mentioned that in the last one, but so it's no longer using the. I think it was probably Yahoo UI. It was. Yeah, so so the tipi murder the tipi JS replacement of Yahoo UI for tool tips right. Yeah. Yeah, so that's been merged to choosing to be everywhere. Just quite nice bit of placement. And there's an API in that as well so you can, there's a couple of knobs that you can tweak as well if you want to have like an interactable menu so you've got the warnings. So if you had any of these that had any coverage, maybe in core. I don't know if this uses a there we go back on page. Let's go to know. This one here. So you. So this is a widget that was in G users. So this is LCS farm. See when I hover over this doesn't just straight away disappear. So that's what's known as interactable. So you can. You can set the interactable element if you want to better hover over text without disappearing. It's like a data data actually you can see it. Yeah, so I think that's about it unless anyone remembers anything else. Great results. Amazing. So the breadcrumbs the breadcrumbs changes were one that that came that just arrived in 385 where a number of places that didn't have breadcrumbs before now have them. Yeah, yeah. And also. Yeah, so there was a while back but in to dot. Yeah, 2.375 the breadcrumbs were reworked into more modern ones. And a couple of releases ago we restored highlighting the last breadcrumb, because it was missing and quite a lot of places in the API is not the best. But in to dot 385. Yeah, a whole bunch more places I've got breadcrumbs added to configuration page Aaron. Thanks Tim. Thanks very much. So any other topics that people want to want to highlight on on the what's arrived recently in UX improvements. I could look at the I could show the change log if that will help. I'm not sure that it tells us anything more than what Tim has already shown us. We did get I guess HTML syntax is now available for node descriptions. And there's a hide values and tables edition that was added that's part of the user experience. Oh, so I mean to show that. Did you want to show that Mark or no if you if you want to show it I would I would certainly prefer it if you show it it's much, much more effective when you show it than when I show it. Yeah, so I missed that one. Cool. So yeah. So a new change new kind of security enhancement change was released in the last release. It's not a security fix as such but it's kind of just nice to have which helps prevent shoulder surfing and or even just if you're sharing a screen and possibly putting something into a video or whatnot and you want all these values to show up. So you can click so all system properties and environment values are hidden by default. The other thing actually mentioned before is the system information pages now in tabs rather than rather than one huge page would normally scroll quite long. But here it's just, it's been tabbed. You can click these to show them click them to hide them and then you can copy them just fine as well. And if you're copying text it won't change. I won't click show hide here because I don't know what's here. Yeah, so you can you can show and show and hide all or reveal individual values looks fairly safe but I'm not going to click it on video. So, so that that transition to tabs also happened in 385 or or. Yeah, I think it was 385. Good. The other thing I was going to add is, yeah, I managed so I managed to close down a lot of requests over the New Year's break. We were at about, I think 35 open web UI pool requests. And we're now down to 19 with, I think, I think, I think 16 of those are ready. Yeah, 16 of those are ready PRs. I think less. Yeah, so 16 of those are ready, ready PRs and three of them are in draft. Thank you. Thank you for that. Nice, nice merge. Thanks very much for so many. That's great. Any other topics that we should highlight. I was just saying most of the remaining ones have issues that need fixes is probably only three or four of them that are ready in the current state that with minus changes. Great. Thank you. The next topic was what's coming in UI improvements Tim that's a that's a common place we've looked to you are there any things you would like to share or highlight. Hey things that are in progress I've seen more progress and in Yahoo UI removal if I understood correctly. So the next one is the changing the changing some of the context menus to use tippy instead of Yahoo UI. So that's that's the one that's waiting on security review at the moment. I think that one is going pretty smoothly. I don't think I have. Yeah, so yeah, exceptions test is passing on alternate. It all looks all looks good. The only issues we found last week was some keyboard issues which were fixed for accessibility. Great. So yeah, just waiting on security review and then you'll be able to replace that I don't think it's all of the context menus. The button drop downs haven't been changed in some places, but it's just keeping it as a smaller simple PR. But it looks quite nice. You can the screenshots on. I'll send a link if you want to open it. Oh, great. Thank you. Yes. Okay, so here. Nice. These are these are the screenshots that Jan has placed here are using tippy not using Yahoo UI to do the do the work. Yeah. Yeah. Thank you so much. That's looks looks marvelous. Thank you. So this is one need security review. Great. Thank you. Other items you wanted to highlight I noted that you went to and it looks like the site is still running the prototype site you'd use to show show possible vision for the next next for a future Jenkins UI. Would you be okay if I embedded that URL here or maybe you could share the URL or is it something you're, you're not really ready for a people to look at and think about what's the future, what might the future be. Yeah, it's fine. The links been posted and get her in. Oh, it has. Okay, good. All right. Anything else you wanted to highlight on what's coming in UI improvements. No, not at the moment. So I've been seeing pipeline graph view improvements arriving that seem seem to be steadily making progress. Anything that you wanted to share there. Yeah, so I think it's a whole bunch on that month so ago so in November quite a lot of work was done. Improving that. I'm not sure. See it probably works on CI. You can start. I'll just check the base version. Yep. Yeah, so I don't think I should have all that. Yeah, I've, I confess I've turned off blue ocean. I'm not using blue ocean anymore I'm just using pipeline graph you on my CI instance and I'm thrilled with it it's working very well. Yeah, I can show that quickly. Okay. Yeah, see this is on CI. There was quite a lot of fixes done to the, what the algorithm was reworked. So it works a lot more like blue ocean so most cases I think we may be seeing a different screen share I'm seeing get a GitHub page. Yeah, that crew Google Chrome window. Got it. Now it's now it's pipeline graph you. So yeah the algorithms been fixed up so it's very very limited cases that don't work. It's mostly matrix these sort of things I think and quite weird cases but yeah in general it works fine. Pulled in the card design from the prototype. So so there's a couple of cards and then you can expand it. And using Iona cons and keyboard and everything to expand and so integrates here with GitHub projects and just pulls in some information from the details card. Yeah, I love that details card because on a pull request it shows me the pull request title. It's amazing how helpful that is for me when oh what what what was the 4891 or 595597 gives me no information it doesn't give me nearly enough information whereas pipeline graph you showing me that in the in the tab, or on that card. Select builds by display name that Matt that means something to me. Yeah, so you've got repo, probably not too relevant in this case branch PR commit. And then when it started time has been in queue and how long the build took. So thank you this is showing one of the cases where it doesn't quite work. So what's going on there. And so that was that card there and there's also some buttons here, you can rebuild and then for I think simple pipelines, you can also go to the configuration page. And this is a quite a lot of work and styling done so no longer overflows using kind of a cleaner design highlights highlights the active step. And then you've got some you've got some step information here as well. If anything failed in a build it should. So you can go to overall stage as well and get stage information. And in the stage information, there'll be a link to any failed steps. So you click the link to get any failed steps. And there's an algorithm based on pollution as well to automatically open the open the failed step if anything failed. Along with being able to rebuild from this page without leaving and going to a different page. I think there's a little bit of so also that got rebranded from like pipeline graph view to being called like as a pipeline graph and pipeline console and they've got new icons. And from the job page it's called stages. And a little bit of work. I think maybe a little bit of cleanup was done here and there's a PR that I haven't finished. Which reworks that page to use card layout as well. I'm not sure how far along I got on it. So would we work the stages page to use card layout. Nice. Yeah, I think I think so it was just to bring in more information so you can have a details card on that page. And then you could expand it. Right and was this page here just continuously polls currently. I just turned off because I didn't have time to implement it but it was pretty annoying. And this is so this is this goes to a different page. It doesn't pop out a model. So then you get a full page view of it. So I think it was I think the reason I didn't merge it was I wanted to add a bit more to this page. Like a details card or something. But that's not sure it didn't. Maybe I just wanted to review. I don't know. It was a while ago. Get back to it at some point. Cool. That's all those. Thanks Tim. Thanks very much. So those were the all the topics we had for today. Unless somebody's arrived who wants to talk to feature flag status or a keyboard usability or other topics are there other topics to be brought up. I'll go ahead and stop the recording. Thanks very much everyone for being here. The recording will be posted within the next 24 hours. Thanks a bunch.