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.

Sign up for GitHub

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

Jump to bottom

Viewing a process step without FeedView results in an infinite loading screen #8502

Closed
N-lson opened this issue Nov 29, 2023 · 2 comments
Closed

Viewing a process step without FeedView results in an infinite loading screen #8502

N-lson opened this issue Nov 29, 2023 · 2 comments
Assignees
@N-lson
Labels
kind/bug This issue represents a verified problem we are committed to solving

Comments

@N-lson
Copy link

N-lson commented Nov 29, 2023

Severity

No response

Version

2024.1

Latest Version

I could reproduce the problem in the latest build

What happened?

If a user doesn't have FeedView, when trying to open any step in a deployment/runbook process the process will show as loading infinitely.

Reproduction

Give a user project permissions minus the FeedView. Try to open a process step

Error and Stacktrace

No response

More Information

No response

Workaround

No response
@N-lson N-lson added the kind/bug This issue represents a verified problem we are committed to solving label Nov 29, 2023
@N-lson N-lson closed this as completed Nov 29, 2023
@octoreleasebot
Copy link

Release Note: Fixed a bug where the page would permanently load when viewing a deployment process without FeedView

@Octobob
Copy link
Member

Octobob commented Feb 19, 2024

🎉 The fix for this issue has been released in:

Release stream Release
2024.1 2024.1.3217
2024.2+ all releases

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

@N-lson N-lson

Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Octobob @N-lson @octoreleasebot