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

Project settings is not accessible if there are no environments present #3484

Closed
1 of 4 tasks
Dogacel opened this issue Feb 28, 2024 · 0 comments · Fixed by #3572
Closed
1 of 4 tasks

Project settings is not accessible if there are no environments present #3484

Dogacel opened this issue Feb 28, 2024 · 0 comments · Fixed by #3572
Assignees
Labels
bug Something isn't working

Comments

@Dogacel
Copy link
Contributor

Dogacel commented Feb 28, 2024

How are you running Flagsmith

  • Self Hosted with Docker
  • Self Hosted with Kubernetes
  • SaaS at flagsmith.com
  • Some other way (add details in description below)

Describe the bug

If no environments exist in a project, the project settings menu says

Oops!
It looks like you do not have permission to view this environment. Please contact a member with administrator privileges.

Steps To Reproduce

  1. Create a new organization
  2. Create a new project
  3. Delete the default environments
  4. Click on Project Settings

Expected behavior

Project settings should be accessible

Screenshots

No response

@Dogacel Dogacel added the bug Something isn't working label Feb 28, 2024
@kyle-ssg kyle-ssg self-assigned this Feb 28, 2024
@kyle-ssg kyle-ssg linked a pull request Mar 6, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants