Content
View differences
Updated by Alexander Coles 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**
* Primerize the project create form
* Show mandatory project attributes
* Primerize the project copy form
**Out of scope**
* <br>
Primerize the Project settings -> Information
* Allow to rename a project from the Project overview More menu in the toolbar
* Changes to the Project overview
* Rename the project from the Project overview
* Change the parent project (NG select)
* CRUD project status and status description
* Project description
**Open**
* <br> Can we move the update of the project status from the Project settings to the project list and the status widget in the Project overview? The alternative would be to have a separate menu item for the project status.
* creating a project from template currently has a weird mixture of attributes shown. How should that case be handled?
**I want to** use standardized Ruby View Components and our Primer design system
**So that** the maintenance of those views get easier.
**Acceptance criteria**
* Primerize the project
* Show mandatory project attributes
* Primerize the project
**Out of scope**
* <br>
* Allow to rename a project from the Project overview More menu in the toolbar
* Changes to the Project overview
* Rename the project from the Project overview
* Change the parent project (NG select)
* CRUD project status and status description
* Project description
* <br>
* creating a project from template currently has a weird mixture of attributes shown. How should that case be handled?