> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/devops/new-ui-ux-transition/whats-new.md). # What's New ## ![](https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FG5ZbxX918xOHwbAwAJ4n%2FSummary2-Small-Icon.svg?alt=media\&token=da26a67f-ff7f-47b3-8669-06be960dc2d7) Overview Flosum is proud to introduce a beautifully redesigned user interface (UI) for Cloud DevOps, built around a faster, more intuitive user experience (UX). The new UI looks and feels like the professional development tool it is, making smarter use of your screen to display more detail with fewer clicks and less scrolling. Best of all, the workflows you already know are mostly unchanged; only some buttons, labels, and navigation items have been refreshed or moved. This article gives you a quick tour of everything new, and the companion articles below provide more details: * [New UI Screenshots](/devops/new-ui-ux-transition/new-ui-screenshots.md) * [Where Did It Go](/devops/new-ui-ux-transition/where-did-it-go.md) ## New UI Rollout The new DevOps UI will roll out gradually, region by region, with days between each release, so you may not see it right away. In the meantime, you can review the New UI Transition article to familiarize yourself with the upcoming changes, even while your tenant is still on the old UI. {% hint style="info" %} #### No Data Loss The new UI is purely cosmetic. All of your existing organizations, branches, pull requests, and pipelines remain fully available and unchanged. {% endhint %} ## Sidebar Menu The sidebar menu has several changes that affect how you navigate DevOps: 1. **Code** has been renamed to **Branches**. The menu item works the same way as before, so you can continue to manage your branches from the same place using the new label. 2. **Settings** is now expanded to display each setting as a menu item. Instead of opening Settings and selecting a page, you can navigate directly to the setting you need from the sidebar, reducing the number of clicks required to reach it. 3. **Help** / **Theme** / **User Account** has moved to the bottom of the sidebar menu. You can access Account Settings, Theme (Light/Dark mode), and Log out options from the User Account menu. ## Branch UI Improvements The interface for individual branches now presents more information in more logical places, with less scrolling and clicking. For a detailed list of branch UI items that have moved, see the following article: * [Where Did It Go](/devops/new-ui-ux-transition/where-did-it-go.md) ## Pull Request Table Improvements The Pull Request table now shows more detail about each Pull Request and keeps **Closed** and **Merged** Pull Requests visible. In the old UI, a Pull Request was removed from the table once it was merged or closed; now you can select merged and closed Pull Requests to view their details. The Pull Request statuses have also been simplified to just three. **New Statuses** * **Open**: Covers all the Old UI statuses (**Created**, **Review Requested**, **Changes Requested**, **Approved**) and indicates a Pull Request that needs action. * **Merged**: Previously hidden from the table, this status indicates that a Pull Request was completed by merging the source branch into the target branch. * **Closed**: Previously hidden from the table, this status indicates that a Pull Request was closed without being merged, leaving the source and target branches unchanged. ## Code Viewer The Code Viewer has been updated for a more streamlined, powerful experience. Now, wherever code appears in DevOps, the Code Viewer delivers a unified, consistent experience across every tool. It offers two views, a single-component view and a diff viewer, that share the same design and flow. The following article takes a more in-depth look at the new Code Viewer. * [Improved Code Viewer](/devops/new-ui-ux-transition/improved-code-viewer.md) ## Tables Tables throughout DevOps are now clearer and more information-dense. Each table includes more columns with clearer labels, so you can scan it and find what you need at a glance, with less guesswork. The added density also lets you see more rows at once, reducing scrolling as you work. Together, these changes help you spend less time hunting for information and more time acting on it. The new timeline table view presents information where the order of events matters, such as branch commits or branch activity. Rather than a standard table, these items are arranged chronologically so you can follow what happened and in what sequence. This makes it easier to trace the progression of events at a glance. You will see the timeline view wherever an ordered, event-based perspective is more useful than a conventional table. #### Saved View The new **Saved View** feature lets you save a specific filter and sort order for each table. Once you have configured a view that fits your workflow, you can reapply it in one step instead of reconfiguring the same filters and sorting every time you return to the table. A saved view captures everything needed to reproduce a table's configuration, and you can create, edit, rename, and switch between as many views as your workflow requires. Each saved view stores: * **Filter selections:** Preserves the filters you have applied, so the view always opens showing only the rows you care about. * **Search term:** Retains any active search, narrowing the table to matching results the moment you open the view. * **Table order:** Remembers how your rows are sorted and arranged, keeping the layout consistent each time. * **Named views:** Give each view its own name, making it easy to recognize and select the right one. ## Moved Items Some items have moved to new locations to make DevOps easier to use. As part of the redesign, related actions and settings are grouped together more logically. If you cannot find a specific item where you expect it, it has most likely moved rather than been removed. For a full list of relocated items and their new locations, see the following article: * [Where Did It Go](/devops/new-ui-ux-transition/where-did-it-go.md) ## Buttons/Labels/Dialogs DevOps includes many small refinements to buttons, labels, and dialogs throughout the app. Labels have been reworded to describe their actions more precisely, buttons sit closer to the content they affect, and dialogs present clearer prompts and guidance. Each change is minor individually, but together they are designed to reduce confusion and give you more information at each step, so you can move through your tasks with greater confidence. ## Existing Documentation The existing DevOps documentation remains applicable to the new UI because the steps to complete a task have largely stayed the same, even though the surrounding interface looks different. As you follow an existing article, you may notice minor differences in the wording of steps, the location of buttons, and the names of some labels. The screenshots, however, are now outdated and will be updated over time as each article is revised. To help you identify which articles have not yet been updated, any article that still contains outdated screenshots or instructions will display a banner like the one below. {% hint style="warning" %} #### Written for the Old UI This article was written for the old UI. The instructions are still usable, but the screenshots are outdated. In some cases, items referenced in the instructions have moved or changed. If you cannot find an item, see the [Where Did It Go](/devops/new-ui-ux-transition/where-did-it-go.md) article. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flosum.com/devops/new-ui-ux-transition/whats-new.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.