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

Users with scoped EnvironmentView can't filter task by Environment #4850

Closed
pawelpabich opened this issue Sep 3, 2018 · 3 comments
Closed
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving tag/permissions
Milestone

Comments

@pawelpabich
Copy link

pawelpabich commented Sep 3, 2018

Users with scoped EnvironmentView permission can't filter tasks by Environment. The UI code asserts the user has access to all environments instead of asserting that the user has access to at least one environment.

What I expected to happen

User should be able to filter tasks by environments they have access to.

Steps to reproduce

  1. Create a user that has EnvironmentView permission scoped to an environment.
  2. Go to task page.
  3. Environment filter is not displayed.

Screen capture

image

Affected versions

4.0.0 - 2018.8.0

Workarounds

The only way around this problem is to give the user unscoped EnvironmentView permission.

Links

https://secure.helpscout.net/conversation/651579309?folderId=909879

@pawelpabich pawelpabich added kind/bug This issue represents a verified problem we are committed to solving area/modelling tag/permissions labels Sep 3, 2018
@pawelpabich
Copy link
Author

@octoreleasebot
Copy link

Release Note: Fixed a bug where environments filter wasn't shown on the tasks page for users with scoped EnvironmentView permission

@lock
Copy link

lock bot commented Dec 2, 2018

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 Dec 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug This issue represents a verified problem we are committed to solving tag/permissions
Projects
None yet
Development

No branches or pull requests

2 participants