Suboptimal use of dashboard screen estate

trond's Avatar


21 Feb, 2018 10:54 AM

We have fairly long project names in Octopus, which are namespace-derived. As you can see, the newest version of Octopus has a few issues here:
1. Although theres ample amounts of screen estate available, Octopus line-breaks the projects
2. The line breaks are not done on the "." character, which makes it unnessecarily hard to see the names

Is there a plan to fix this?

  1. Support Staff 1 Posted by Nick Josevski on 22 Feb, 2018 04:25 AM

    Nick Josevski's Avatar


    Thanks for getting in touch.

    The most important reason the column is fixed width is for customers who have multiple project groups to ensure all the groups align.

    There's no plans in the near future for any changes to the dashboard. It's been quite difficult to balance all the demands for the dashboard. We've had to factor in many various scenarios to accommodate different configurations. Customers with short names, others with very long names and no characters to break on, others may use hyphens, or slashes or any symbol not just full stops to break apart names, so it's not feasible to split on every possible setup people may have.

    Here's the issue we had and it was a larger usability problem with it all misaligned:

    Do you depend on the projects being named that way for other code/processes to find them? Could you rename them with spaces instead of full stops, and if there was code to find them adjust it to also use spaces?


  2. 2 Posted by trond on 23 Feb, 2018 09:04 AM

    trond's Avatar

    We definetely don't want to rename them just to make the deploy gui happy. The namespaced names are used throghout are pipeline.

    I totally understand that it's difficult to cater to every single need. Still, this wasn't a problem in Octopus 3.0. Something like "if there's a lot of screen estate, expand the left column" should be possible to implement?

  3. Support Staff 3 Posted by Nick Josevski on 23 Feb, 2018 11:04 AM

    Nick Josevski's Avatar


    We did make some big improvements in 4.0, we understand and have had feedback where people liked things how they were in 3.0, but overall the feedback has been good as there's a lot more consistency now, at the cost of some things like this being not ideal.

    There's no short term work on the dashboard that your request can be attached to for further consideration. So all I can suggest is add a comment to this issue which will be a large piece of work sometime in the future to add additional functionality to the dashboard, include the screen shot you added here.

    If you are curious as to what our current priorities are for the product they're outlined in this blog post

    It's tricky to say "not at the moment" to reasonable requests but we do get a lot of requests for adjustments to the application, there's many things that they need to be prioritized against, from working on our big ticket features listed on the road map to bugs that stop people doing work.


Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Already uploaded files

  • Screenshot_from_2018-02-21_11-52-26.png 119 KB

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac