Content
View differences
Updated by Jens Ulferts 21 days ago
**Acceptance criteria** # Acceptance criteria
workPackageValue:71883:"Acceptance criteria" The existing Backlogs view (/backlogs) is re-newed using Primer components.
**Layout**
* The setting to define in which column a version shall be displayed, remains. So there can be a two column layout
**Tables**
* Use BorderBox component
* There will be no inline editing functionality for now
* The header:
* is collapsible (use CollapsibleSections)
* contains: Version name, start date (optional), end date (optional), the story points assigned to it (current behavior)
* Has an ActionMenu with the currently existing functions
* The menu is extended by an option "edit"
* The rows:
* contains: The WP displayed simliar to how it is done for Meetings or Relations (WP info row with title below)
* At the end there is an invisible menu button with an option to
* edit
* Move to top
* Move up
* Move down
* Move to bottom
* At the beginning, there is an icon indicating drag'n'drop
* Sorting is as before (by date first and then by name)
**Behavior**
* Editing
* is triggered by a specific button (see above)
* opens the WP in split screen  (like in Notification center). Editing can be done there.
* Creating:
* When clicking "New story", a dialog opens (like in Relations)
* Drag'n'Drop:
* Rows are draggable within and between tables (as before)
* When moved to another table, the version of the WP changes
<br>
**Figma**
workPackageValue:57688:Mockups
## **Out of scope**
workPackageValue:71883:"Out * Functional changes to the Backlogs module
* Inline editing
* Other pages of scope"
the Backlogs modules
* Task boards
* Burndown charts
* Creating new components (in this iteration we only use what we have)
<br>
workPackageValue:71883:"Acceptance criteria"
* The setting to define in which column a version shall be displayed, remains. So there can be a two column layout
**Tables**
* Use BorderBox component
* There will be no inline editing functionality for now
* The header:
* is collapsible (use CollapsibleSections)
* contains: Version name, start date (optional), end date (optional), the story points assigned to it (current behavior)
* Has an ActionMenu with the currently existing functions
* The menu is extended by an option &quot;edit&quot;
* The rows:
* contains: The WP displayed simliar to how it is done for Meetings or Relations (WP info row with title below)
* At the end there is an invisible menu button with an option to
* edit
* Move to top
* Move up
* Move down
* Move to bottom
* At the beginning, there is an icon indicating drag&#39;n&#39;drop
* Sorting is as before (by date first and then by name)
**Behavior**
* Editing
* is triggered by a specific button (see above)
* opens the WP in split screen &nbsp;(like in Notification center). Editing can be done there.
* Creating:
* When clicking &quot;New story&quot;, a dialog opens (like in Relations)
* Drag&#39;n&#39;Drop:
* Rows are draggable within and between tables (as before)
* When moved to another table, the version of the WP changes
<br>
workPackageValue:57688:Mockups
workPackageValue:71883:"Out
* Inline editing
* Other pages
* Task boards
* Burndown charts
* Creating new components (in this iteration we only use what we have)