Content
View differences
Updated by Parimal Satyal 17 days ago
**As** a team member in a scrum project
**I want to** be able to select and view small or large sets in my backlog bucket and sprints bucket
**so that** I can view a specific backlog and sprint at a glance.
<br>
**Acceptance criteria**
* On the Backlog and sprints page, there is a button on the backlogs side that triggers a multi-select SelectPanel:
* The button is titled "**All backlog "**Backlog buckets"**
* On click, the user sees all existing buckets (identifiable by names) + backlog inbox. Backlog buckets appear on top. Backlog inbox at the bottom.
* The buckets within the backlog can be filtered (using the text filter) to only show a specific backlog bucket \[e.g, Low-hanging fruit\] or multiple buckets.
* On the Backlog and sprints page, there is a button on the sprints side that triggers a multi-select SelectPanel:
* The button is titled "**All sprints"** "**Sprints"**
* Clicking on **Sprints** means the user can view all existing sprints grouped by buckets.
* The items within the sprints can be filtered to only show a specific sprint bucket \[e.g, Sprint 2-Discovery\] or multiple sprint buckets.
* Only active and in planning sprints are available for selection.
* Selections made in the above selectors are reflected in the URL. Sharing URL url will carry the selected sprints and buckets to the new page load.
**Technical notes**
* The two buttons use the standard [**Select Panel**](https://qa.openproject-edge.com/lookbook/pages/components/select_panel) component. component without any custom code.
* The initial label on the buttons will be "All backlog buckets" and "All sprints" when no filtering is applied; and "Backlogs (2)" and "Sprint (2)" when active.
* The "(2)" represents a counter component.
* We're going to with the approach where we have footer has an Apply additional 'clear' button to submit that doesn't come with the filtering.
* The SelectPanel has a component but which the component allows. So the footer implemented at this feature level with includes two buttons:
* Clear (secondary, clears the selection and goes "Clear" (secondary): Goes back to default state, submits the request state (none selected) and closes the panel) panel.
* Apply (primary, submits "Apply" (primary): Applies the request current selection and closes the panel) panel.
* You do not have **Note:** Adding a counter to not implement this apply button with counter, we already have a feature for this: <mention is out of scope, will be handled within the component in <mention class="mention" data-id="75516" data-type="work_package" data-text="##DREAM-700" data-display-id="DREAM-700">##DREAM-700</mention> data-text="##SDS-700" data-display-id="SDS-700">##SDS-700</mention>.
**Permissions and visibility considerations**
* _\-_
**Translation considerations**
* _\-_
**Out of scope**
* Storing the selected values in the backend.
**I want to** be able to select and view small or large sets in my backlog bucket and sprints bucket
**so that** I can view a specific backlog and sprint at a glance.
<br>
**Acceptance criteria**
* On the Backlog and sprints page, there is a button on the backlogs side that triggers a multi-select SelectPanel:
* The button is titled "**All backlog
* On click, the user sees all existing buckets (identifiable by names) + backlog inbox. Backlog buckets appear on top. Backlog inbox at the bottom.
* The buckets within the backlog can be filtered (using the text filter) to only show a specific backlog bucket \[e.g, Low-hanging fruit\] or multiple buckets.
* On the Backlog and sprints page, there is a button on the sprints side that triggers a multi-select SelectPanel:
* The button is titled "**All sprints"**
* Clicking on **Sprints** means the user can view all existing sprints grouped by buckets.
* The items within the sprints can be filtered to only show a specific sprint bucket \[e.g, Sprint 2-Discovery\] or multiple sprint buckets.
* Only active and in planning sprints are available for selection.
* Selections made in the above selectors are reflected in the URL. Sharing URL url will carry the selected sprints and buckets to the new page load.
**Technical notes**
* The two buttons use the standard [**Select Panel**](https://qa.openproject-edge.com/lookbook/pages/components/select_panel) component.
* The initial label on the buttons will be "All backlog buckets" and "All sprints" when no filtering is applied; and "Backlogs (2)" and "Sprint (2)" when active.
* The "(2)" represents a counter component.
* We're going to with the approach where we have
* The SelectPanel has a
* Clear (secondary, clears the selection and goes
* Apply (primary, submits
* You do not have
**Permissions and visibility considerations**
* _\-_
**Translation considerations**
* _\-_
**Out of scope**
* Storing the selected values in the backend.