Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Web] Batch Actions for Spaces #8267

Closed
exalate-issue-sync bot opened this issue Jan 18, 2023 · 0 comments · Fixed by #8268
Closed

[Web] Batch Actions for Spaces #8267

exalate-issue-sync bot opened this issue Jan 18, 2023 · 0 comments · Fixed by #8268
Labels

Comments

@exalate-issue-sync
Copy link

exalate-issue-sync bot commented Jan 18, 2023

Description

tbd

gist:

  • utilize Spaces list in admin settings to a) disable and b) delete spaces

User Stories

  • As an Admin I want to edit multiple Spaces at once, so that I dont need to edit every single Space one-by-on.

Value

efficient management of spaces

Acceptance Criteria

[x] Batch actions are

  • Disable
  • Delete
  • Enable
  • ~~Change Quota~~~
  • Edit (opens right sidebar)

[x] Mixed status: If Spaces with different status (Disabled + Active) are selected, all batchactions that are applicable for at least 1 selected item are displayed.
[x] Show count in Batchaction The Batchaction shows how many of the selected items would be affected by the change [Delete (4)] [Disable (2)] (c.f. scribbles)
[x] Show count in Dialogs The dialogs for "delete", "disbale" and "enable" show the count in its Title (c.f. scribbles). Up to you: we can show the count also in the button - see scribble. unsure if this is useful. decision is up to you.
[x] Selection after executed batchaction the selection remains unchanged after an executed bactchaction, but the counts in the batchaction buttons get updated. reason: sometimes the user wants to perform follow-up batch actions (ex. disable->delete).

Definition of ready

[ ] everybody needs to understand the value written in the user story
[ ] acceptance criteria has to be defined
[ ] all dependencies of the user story need to be identified
[ ] feature should be seen from an end user perspective
[ ] user story has to be estimated
[ ] story points need to be less then 20

Definition of done

  • Functional requirements
    [ ] functionality described in the user story works
    [ ] acceptance criteria are fulfilled
  • Quality
    [ ] E2E Test
    • Background: Create 10 Spaces (2 disabled).
    • Select 8 items, incl. the 2 disabled Spaces
    • Select "Disable" batchaction, confirm dialog.
    • then: 8 items are still selected, all of them are disabled; No "Disable" button is available
    • select "Delete" batchaction, confirm dialog
    • then: 2 Spaces are remaining in the list

[ ] code review happened
[ ] CI is green
[ ] critical code received unit tests by the developer
[ ] automated tests passed (if automated tests are not available, this test needs to be created and passed

  • Non-functional requirements
    [ ] no sonar cloud issues
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

0 participants