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

feat: Application Permissions not working if no Environment is selected #5400

Closed
2 tasks done
akshatsinha007 opened this issue Jun 28, 2024 · 2 comments
Closed
2 tasks done
Assignees
Labels

Comments

@akshatsinha007
Copy link
Contributor

akshatsinha007 commented Jun 28, 2024

📜 Description

If an application contains only build pipelines and no environment pipelines or deployment pipelines we do not allow user build in that application until the access to All Environments is provided to the user.

👟 Reproduction steps

👍 Expected behavior

👎 Actual Behavior

☸ Kubernetes version

EKS 1.28

Cloud provider

AWS

🌍 Browser

Chrome

🧱 Your Environment

No response

✅ Proposed Solution

No response

👀 Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

AB#10084

@akshatsinha007 akshatsinha007 added the bug Something isn't working label Jun 28, 2024
@vikramdevtron
Copy link
Contributor

vikramdevtron commented Jul 9, 2024

@akshatsinha007 You have to provide specific environment or ALL from the drop down while giving permission, this is current expected behaviour.

@akshatsinha007 akshatsinha007 changed the title Bug: Application Permissions not working if no Environment is selected feat: Application Permissions not working if no Environment is selected Sep 16, 2024
@akshatsinha007
Copy link
Contributor Author

Same as #5612

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants