New UI now available for opt-in!

Hi Kate,

Just wondering if those blue progress icons are based on average job time or last job time?

If not, could the team could look into adding progress bars based on last job time or average job time? It would be really good to look at the workflow and know roughly when it will be done.

Kind of like Jenkins.


1 Like

Thank you! There should now be a pop-up in the bottom right-hand corner (unless you have pop-ups blocked) where you can leave feedback, or feel free to post again here.

Regarding too much whitespace, we are hearing that feedback quite a lot and getting it changed in the next week.

Regarding estimate of previous build step, this has been a common request but is more difficult than we hoped to implement. It’s still something we want in the new UI but won’t be a short-term addition at least.

The blue progress indicator simply indicates a job in a workflow that is still running as opposed to failed or successful. It’s binary rather than percentage and the icon always looks the same.

However, having some kind of indicator for how close to done it is would be an interesting idea. Doubt we can get to it short-term but good to hear for the long-term.

Can you provide me a specific situation in which you want/need to know when the workflow will be done?

I’ve tried the new UI but I just want to say that it feels kind of unacceptable that the new UI is making my Chrome browser use 20x the CPU compared to the old UI (even when having the live log open). My macbook burns up when I have the tab open (using like 50-70% CPU on a Macbook Pro i7 2015), whereas the old UI seems to linger at around 3-5%. This is not only uncomfortable when having your computer in your lap, it also totally kills your battery.

Didn’t know where to report this so figured this thread is as good as any.

Thanks, Jishi!

We haven’t seen this before. Can you link us to what page you were on? Was it a jobs page or a pipelines page? We’d love to run it on our end and get it fixed for you.

It’s both when listing the pipelines (I guess?) and when watching an individual job, when a job is running:

This is the CPU graph between the new and old ui, when watching a job and having the console expanded (during the same phase), top one is old ui, bottom one is new ui:

1 Like

New UI is missing so much information it’s really hard to give feedback at this point(configuration, parallelism, context, etc, etc).

The new step output boxes appear to be recycling DOM elements. This is preventing searching into the output with the browser search and is a real step backwards in utility…

I can say the new UI feels way less inspired than the current UI. It feels like a very generic Atlassian interface from confluence or something.


I’m not seeing the feedback pop-up because of pop-up blockers. I looked for a link to something like this discussion in the (mostly empty) “new look” sidebar, then went hunting manually.

I keep flipping back to the old UI because:

  • the tests panel on the new UI doesn’t give me as much info as i’d like. “all passing”, great - how many? when doing initial CI bring-up, i want to validate that it’s actually recording all my tests. the “slowest test” bit was also missing.
  • the redirect blip is distracting. i’d rather land directly on the ui i need to see than go somewhere, then go somewhere else, then finally get to see the build results.

Thanks for the feedback! We’ll work on getting the test numbers back in. Slowest test will likely come later from our team working on our new Insights API.

The redirect blip will definitely go away in time once we’re ready to switch everyone over to the new UI.

Keep the feedback coming, we appreciate it!

Thanks for voicing this, it’s great feedback. We’re in the midst of overhauling our UI and making it action simple/intuitive/inspired is important to us.

Would you be willing to do a user experience session with us to share more thoughts? Happy to share a $50 gift card as a thank you:

Hi, how do I opt out of the new UI? I can’t find it at all. I’m getting 404 pages left and right.

1 Like

Sorry to hear that. We did have some issues yesterday with AWS, hopefully it’s all squared now?

You can always opt-out from the left-hand navigation where this arrow indicates:

The new interface gives me the error Error: GraphQL error: Cannot return null for non-nullable field Job.branch.. I’m trying to opt-out right now. Is there a link that I can follow? The site is unusable right now.

@zaerl sorry to hear that! Did you try refreshing the page?
We will add an opt-out button to the GraphQL page to solve for this. If your work is blocked in the interim please contact support and we can maneuver on the backend to opt you out.

Unfortunately I tried everything. The page /gh/{org}/{job}/{index} generate the error (in the /api/v1.1/project/{repo}/{index} XHR the field “branch” is nil).

I will contact support, thanks.

@zaerl can you link us to the build that you are seeing this error on? We will get to the bottom of it on our end immediately.

Can I write this in private? The job contains the name of one of our customers and I don’t want to share this information publicly.

1 Like

Of course, email me at my first name @ @zaerl

Should those last two screenshots be available to users that are currently enrolled in beta participation? I’m not seeing them.

The two things I miss most from the old UI are 1) workflow map, and 2) “rerun from failed”. I also really like that visualization of individual step progress.

1 Like

Hey! The screenshots use circles vs. squares to differentiate running vs complete. In the public opt-in for Jobs, they use these weird cube outlines w/ a blue/green that is brutal for colorblind people. Hopefully this is slated to change? :slight_smile:

1 Like