Dear upvoters, can you share more details on your use cases, how would this feature be valuable? How would you use it, how frequently? And what would be your next 1-2-3 actions after seeing these PRs in the Dashboard?
We’d like to have a cohesive understanding of the use cases before building it.
Blue Goose
•
Aug 5
There’s multiple use cases for me:
just to see all tracked runs in a list (with their status, just like the stacks view practically), where you then can filter on repository, project root, space, state, etc …
when I have an PR open which is attached by multiple stacks (e.g. multiple workspaces / regions), it would be great to, in Spacelift, easily see the list of proposed runs of all those stacks in one view
For the latter, we kind of can see this in the pipeline view of the VCS, but having the ability to have this in Spacelift would be a big advantage.
Ovidiu Moise
Team•
Aug 7
@Joost Polley for your first bullet - isn’t this already achievable in the Runs screen, if you select grouping per stack? On the left you have your stacks, and then you have each run and their status. You can also group by repository, space etc. Feels like exactly what you said.
As for the second scenario, did I understand correctly that it would be a UI flow starting from a PR → the stacks it is affecting → the Runs, and then as details to see the changes brought by that PR? Anything else here? And what would you do next after seeing this?
Ovidiu Moise
Team•
Aug 7
@Joost Polley is this the same idea basically like the one here?
@Ovidiu Moise indeed, I think those two requests are talking about the same problem.
The run screen: yes, this is kind of achievable in the runs screen, but the runs screen is really cumbersome at the moment to deal with. An ideal situation would be a runs screen, but that has the look & feel of the stacks view (where you see stacks running based on your filters, their state, the pending changes, etc …).
Log in to comment and vote
Comments5
Ovidiu Moise
Aug 5
Dear upvoters, can you share more details on your use cases, how would this feature be valuable? How would you use it, how frequently? And what would be your next 1-2-3 actions after seeing these PRs in the Dashboard?
We’d like to have a cohesive understanding of the use cases before building it.
Blue Goose
Aug 5
There’s multiple use cases for me:
just to see all tracked runs in a list (with their status, just like the stacks view practically), where you then can filter on repository, project root, space, state, etc …
when I have an PR open which is attached by multiple stacks (e.g. multiple workspaces / regions), it would be great to, in Spacelift, easily see the list of proposed runs of all those stacks in one view
For the latter, we kind of can see this in the pipeline view of the VCS, but having the ability to have this in Spacelift would be a big advantage.
Ovidiu Moise
Aug 7
@Joost Polley for your first bullet - isn’t this already achievable in the Runs screen, if you select grouping per stack? On the left you have your stacks, and then you have each run and their status. You can also group by repository, space etc. Feels like exactly what you said.
As for the second scenario, did I understand correctly that it would be a UI flow starting from a PR → the stacks it is affecting → the Runs, and then as details to see the changes brought by that PR? Anything else here? And what would you do next after seeing this?
Ovidiu Moise
Aug 7
@Joost Polley is this the same idea basically like the one here?
https://feedback.spacelift.io/p/non-stack-based-prmr-view I’d merge these two.
Blue Goose
Aug 10
@Ovidiu Moise indeed, I think those two requests are talking about the same problem.
The run screen: yes, this is kind of achievable in the runs screen, but the runs screen is really cumbersome at the moment to deal with. An ideal situation would be a runs screen, but that has the look & feel of the stacks view (where you see stacks running based on your filters, their state, the pending changes, etc …).