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

Usability of tenant variables page with a lot of variables #3813

KennethBates opened this Issue Sep 21, 2017 · 5 comments


None yet
6 participants

KennethBates commented Sep 21, 2017

If you have a large number of project variables (100+) that need to be defined for each tenant, this Tenants > [Tenant Name] > Variables page becomes massive. It's not very user-friendly in this scenario. A filter or search option on this page could be a good addition to address the usability of this page.

Possible workaround to having to manage such a long list of variables: reduce the number of needed variables by managing them as JSON or XML, and store the entire set for each tenant as a single variable. This would resolve the large number of variables, but it depends on whether you can modify the process to work with this.


@MJRichardson MJRichardson added this to the 4.0 milestone Oct 3, 2017


This comment has been minimized.

MJRichardson commented Oct 5, 2017

Ensure tenant variables page is usable for large numbers in 4.0.


This comment has been minimized.

pawelpabich commented Nov 9, 2017

This is not going to be done as part of v4. Correct if I'm wrong @MJRichardson.

@pawelpabich pawelpabich removed this from the 4.0.0 milestone Nov 9, 2017


This comment has been minimized.


This comment has been minimized.

egorpavlikhin commented Mar 22, 2018

The issue is not just in a large number of variables but in any amount. Everything on the page is large, except the input fields. Which only support 60 symbols per variable. An average connection string can easily be 100+ characters.


Consider how AutoStoreTerminal:Guid is repeated 3 times for no good reason.

An option for compact UI would also be helpful.

Right now variables in Octopus do not support anything but the simplest scenarios.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment