You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most settings for each resource need to be set in the resource itself, but some belong in the account tab. E.g. the license of a Space, or deleting a resource. This epic is to create a consistent approach for all resources, so users know where to find them. Furthermore, we've recently added functionality to change the visibility of VCs and Template packs, and to share them in the store or not. This also needs to be more consistent and clear to the user.
Goal
Consistency, clarity, complete functionality
Hypothesis
What is your hypothesis on the success of this Epic? Describe how success will be measured and what leading indicators the team will have to know if success has been hit.
Must have scope
Overview of all settings that all resources have, and where they belong: in the resource or the account
Design for consistent approach for changing these settings
Stakeholders
Describe who needs to be kept up-to-date about this Epic, included in discussions, or updated along the way. Stakeholders can be both in Product/Engineering, as well as other teams like Customer Success who might want to keep customers updated on the Epic project.
Design
Figma file: Comments are highly appreciated. When commenting in Figma, please also leave a note in the comments box below this issue to notify us
The text was updated successfully, but these errors were encountered:
Description
Most settings for each resource need to be set in the resource itself, but some belong in the account tab. E.g. the license of a Space, or deleting a resource. This epic is to create a consistent approach for all resources, so users know where to find them. Furthermore, we've recently added functionality to change the visibility of VCs and Template packs, and to share them in the store or not. This also needs to be more consistent and clear to the user.
Goal
Consistency, clarity, complete functionality
Hypothesis
What is your hypothesis on the success of this Epic? Describe how success will be measured and what leading indicators the team will have to know if success has been hit.
Must have scope
Stakeholders
Describe who needs to be kept up-to-date about this Epic, included in discussions, or updated along the way. Stakeholders can be both in Product/Engineering, as well as other teams like Customer Success who might want to keep customers updated on the Epic project.
Design
Figma file:
Comments are highly appreciated. When commenting in Figma, please also leave a note in the comments box below this issue to notify us
The text was updated successfully, but these errors were encountered: