Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Long project names overlap on tenant variables screen #5111

matt-richardson opened this issue Nov 21, 2018 · 2 comments


Copy link

commented Nov 21, 2018


  • I have verified the problem exists in the latest version
  • I have searched open and closed issues to make sure it isn't already reported
  • I have written a descriptive issue title
  • I have linked the original source of this report
  • I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)

The bug

Long project names overlap with the "linked environments" on the tenant variables screen.

What I expected to happen

The text should not overlap - it should either wrap or be truncated and show an ellipses (...).

Steps to reproduce

  1. Create a project with a really long name with .s instead of spaces
  2. Create a project template variable for that project
  3. Create a tenant and link it to the project
  4. Click on Variables
    -> text overlaps

Relates to #5109

Screen capture


Affected versions

Octopus Server: 4.x till fixed


This is just a usability / visual concern - its not blocking
That said, options are:

  • have shorter names for the projects
  • use a different separator to allow the browser to wrap


source: community slack


This comment has been minimized.

Copy link

commented Nov 22, 2018

Release Note: Long project names no longer overlap the selected environments on the tenant variable screen


This comment has been minimized.

Copy link

commented Feb 20, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Feb 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
2 participants
You can’t perform that action at this time.