Story
As a product manager, I need to know the intended purpose of instances running on Cloud, in order to understand use cases better and make strategic decisions.
As an instance manager, when I create an instance, I must provide information on its intended purpose.
Acceptance Criteria
- Before a new instance is created for an instance manager, they need to describe their current intention of using this instance (see wireframes).
preliminary figma mock
- In each question, the user must choose exactly one option of the answer. If nothing was selected and the user tried to click "next" or "create wiki" the redio button group that's missing an input should display the native error state.
- If they choose the option 'Other', they must provide an explanation (non-empty, below 200 symbols).
- If the user chose the option that the wikibase is temporary/disposable, show an additional notification that says
Please make sure to delete this Wikibase when you no longer need it.
- When the instance is created, the response is persisted for it in the database (preferably as enum, to facilitate analytics and implementation of further stories where users can change their answer in the dashboard later).
Note
- This story is for instance creation workflow only. There will be separate stories for viewing and updating the purpose in dashboard UI.
- We use the following code names for the purpose and temporality internally. It would be convenient to have them saved in the database as well:
In the order of answers:
- purpose: data_hub / data_lab / tool_lab / test_drive / decide_later / other (+ additional string is stored for 'other')
- audience: narrow / wide / other (+ additional string for 'other')
- temporality: permanent / temporary / decide_later / other (+ additional string for other)