•  
     
    story #6789 be able to multi- select items in the Backlog and move them to the top
Summary
Empty
be able to multi- select items in the Backlog and move them to the top
Empty

General behaviour

Multiselect:

  • I hold ctrl + click to multi select tasks (as it's done in a file explorer)
  • Selected tasks are highlighted
  • I can drag'n drop the selected tasks
    • For performances reason, only one of the cards will be seen as moved but a small inline message will be shown while we drag to inform users about the other selected items that will droped too
    • Display a fake stack of cards when moving n cards (with n > 1)
  • When I click ESC it deselect all
  • Limitations:
    • We can only multi-select "siblings",  aka items that are next to each others:
      • Backlog items (eg. stories or requests) on the left pane of Planning
      • Content of one milestone (eg. stories or requests)
      • Children of one element (eg. tasks of a story)
    • It means that we should not be able to:
      • Select a User Story and a task children of another story
      • Select one User Story in Release backlog and another User Story already scheduled in a Sprint
      • Select one User story in one Sprint and another User Story in a different Sprint
  • In case of error:
    • if (error) { display error && keep current selection; }

Move to top:

Empty
Emilio Palmiero (empa)
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#6789
Patricia Carrasco (pcar)
2016-01-27 16:05
2014-04-28 22:13
4859

References

Follow-ups

User avatar

During the development, we have spotted a strange behavior due to Dragular, the drag n' drop library. Here it is:

When I select several backlog items, drag one of them and drop it at the same place:

  • If the next backlog item to the dragged backlog item (direct next sibling) was a selected backlog item, change is saved in backend and dragged backlog item may disappear but if you reload the page, it reappear and data are consistent
  • If the next element to the dragged item wasn't into the selected item, nothing is done and all the selected backlog items are deselected

For the time being, because this behavior occurs only when a specific drag n' drop is done, we propose to not handle this edge case and see if it often occurs.

User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
Currently when a new item is created, it is placed at the bottom of the Backlog. Need to move one item at a time to the top. When you have a big backlog, this is annoying

  • CC list set to Emilio Palmiero (empa)