Content
View differences
Updated by Henriette Darge about 1 year ago
**As a** Ruby developer
**I want to** use standardized Ruby View Components and our Primer design system
**So that** the maintenance of those views get easier.
**Acceptance criteria**
* Create a new component based on the existing OP Primer Status Component that allows the user to select a Project Status.
* That component is used in the project settings form
* Changing the status, directly changes the form (no additional "save" needed)
* When something prevents the save, an error messsage is shown (e.g when a required CF is missing)
* When the save is successful, a success message is shown
~~**Open discussion**~~
**Open discussion**
* ~~Project Project Status is not a required field. What should we display when it is not selected?~~ selected?
* ~~Should Should we still map to semantic colours?~~ colours?
**I want to** use standardized Ruby View Components and our Primer design system
**So that** the maintenance of those views get easier.
**Acceptance criteria**
* Create a new component based on the existing OP Primer Status Component that allows the user to select a Project Status.
* That component is used in the project settings form
* Changing the status, directly changes the form (no additional "save" needed)
* When something prevents the save, an error messsage is shown (e.g when a required CF is missing)
* When the save is successful, a success message is shown
~~**Open discussion**~~
* ~~Should