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

Review the impact of pre-filling tenant tags #4166

Closed
NickJosevski opened this Issue Jan 16, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@NickJosevski

NickJosevski commented Jan 16, 2018

Recent changes in on the release screen mean tenant tags are pre-filled, but there are 2 camps of users, those who do want, and those that do not want.

The pre-filled tenant tags, results in a selection of tenants that will be deployed to, and if the tag selection area is expanded, the tenants that will be deployed to will likely be off screen (requires scrolling).

The most recent change to this went out in 4.1.8 and is documented here: #4112

We'll need a solution that caters for both, and doesn't result in the users who were used to not pre-filling deploying to an unexpected number of tenants.

Ideas

Use explicit action Include all applicable Tenants. This will allow us to start with an empty list which makes Camp 1 happy, but also allows to pre-fill data with just one click which should be acceptable for Camp 2 happy. Pre-filling is magic as users don't know the rules so it would be good if we can avoid it.

Customers

Prior discussions

  • #3336 - Ability to exclude tenants when creating multiple tenanted deployments

@NickJosevski NickJosevski changed the title from Review the impact of pre-filling tenants to Review the impact of pre-filling tenant tags Jan 16, 2018

@pawelpabich

This comment has been minimized.

pawelpabich commented Mar 29, 2018

Include all applicable Tenants.

We already have that. @NickJosevski does this means this can be closed?

@NickJosevski

This comment has been minimized.

NickJosevski commented Mar 29, 2018

I think I raised this issue because it was my support week, I don't speak with authority on it, would need to check with @mayuanyang

@mayuanyang

This comment has been minimized.

mayuanyang commented Mar 29, 2018

No body else raises the similar issue, i think should be fine to close @NickJosevski

@pawelpabich

This comment has been minimized.

pawelpabich commented Mar 29, 2018

Fixed in 4.1.8 #3951

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