Content
View differences
Updated by Parimal Satyal 5 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**
* There are buttons in both the Backlogs and Sprints sections of the page that lets users filter and show only specific backlog buckets or sprints.
* The two buttons use the standard [**SelectPanel**](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. The label will be grey.
* The labels will be "**Backlogs (2)**" and "**Sprint (2)**" when active, and in a darker black colour.
* The "(2)" represents a counter component.
* For backlogs:
* On click, the user sees all existing buckets (identifiable by names) + backlog inbox. Backlog buckets appear on top. Backlog inbox at the bottom.
* The title will be "Select items"
* 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.
* For sprints:
* On click, the user sees all sprints (active and in planning) available to the project.
* The title will be "Select items"
* The items within the sprints can be filtered to only show a specific sprint bucket \[e.g, Sprint 2-Discovery\] or multiple sprint buckets.
* The user has to click on the Apply button to enable filtering.
* The SelectPanel has a footer implemented at this feature level with two buttons:
* **Clear** (secondary, clears the selection and goes back to default state, submits the request and closes the panel)
* **Apply** (primary, submits the request and closes the panel)
* You do not have to implement the counter in the Apply button, we already have a feature to implement this separately: <mention class="mention" data-id="75516" data-type="work_package" data-text="##DREAM-700" data-display-id="DREAM-700">##DREAM-700</mention>
**Technical notes**
* 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.
**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**
* There are buttons in both the Backlogs and Sprints sections of the page that lets users filter and show only specific backlog buckets or sprints.
* The two buttons use the standard [**SelectPanel**](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. The label will be grey.
* The labels will be "**Backlogs (2)**" and "**Sprint (2)**" when active, and in a darker black colour.
* The "(2)" represents a counter component.
* For backlogs:
* On click, the user sees all existing buckets (identifiable by names) + backlog inbox. Backlog buckets appear on top. Backlog inbox at the bottom.
* The title will be "Select items"
* 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.
* For sprints:
* On click, the user sees all sprints (active and in planning) available to the project.
* The items within the sprints can be filtered to only show a specific sprint bucket \[e.g, Sprint 2-Discovery\] or multiple sprint buckets.
* The SelectPanel has a footer implemented at this feature level with two buttons:
* **Clear** (secondary, clears the selection and goes back to default state, submits the request and closes the panel)
* **Apply** (primary, submits the request and closes the panel)
* You do not have to implement the counter in the Apply button, we already have a feature to implement this separately: <mention class="mention" data-id="75516" data-type="work_package" data-text="##DREAM-700" data-display-id="DREAM-700">##DREAM-700</mention>
**Technical notes**
* 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.
**Permissions and visibility considerations**
* _\-_
**Translation considerations**
* _\-_
**Out of scope**
* Storing the selected values in the backend.