Substitute status areas with drop areas when issue is dragged

Description

This is a follow-up issue of

.

Description:

Scrolling while dragging is not supported by Dragula.js, therefore ESJF-107 introduced a script that allows to scroll while dragging an issue, but it requires weird “pushing” mouse movement to work.

We should consider changing how this works to eliminate need of scrolling at all. This can be achieved with substituting status areas with about 200px high “drop-zones” when the issue is dragged, so it can be easily placed in the desired status. This solution is very similar to how Jira handles it.

A/C:

  • Dragging issue hides issues in columns and instead “drop areas” are shown.
  • Remove “scroller” from board.ftl script.

Linked issues

relates to
Issue Type Icon ESFJ-938 Share board selectors improvemment for e2e drag and drop tests Priority: Medium
Withdrawn
Issue Type Icon ESFJ-107 Allow issue transition on board by column statuses Priority: Medium
Done

Activity

Automation for Jira 26 February 2024, 12:10

Hello @Piotr Haraburda,

Please merge code to dev branch.
This is the best moment to add more information that can be helpful to prepare release notes.

  • Can you prepare short overview of change that can be used in release notes?
  • Please provide short GIF that showcase feature.
  • If GIF make no sense, can you provide image that highlights feature that can be used in release notes (cropped & annotated)?
Parsa Shiva 26 February 2024, 12:10

@Piotr Haraburda Improvement implemented - QA environment.

Automation for Jira 15 February 2024, 14:14

Hello @Piotr Haraburda ]

This is the best moment to add more information that can be helpful for tester.

  • What areas are affected?
  • What are potential edge cases?
  • Was it checked for XSS problems?
  • Does change affect security, is new data exposed?

Please attach - Before / After screenshot if possible.

Automation for Jira 9 February 2024, 09:06

Hello @Piotr Haraburda,
Change was reviewed and approved.
Task is ready to be deployed to QA.
Once it is deployed to QA please move ticket to "To Test"

Thank you!

Automation for Jira 9 February 2024, 01:26

Hello @Krzysztof Bogdan,
Task is ready for review.

@Piotr Haraburda please make sure reviewer
have easy access to contend to be reviewed.

If this is code change. Please make sure PR is created.
If this is new documentation, blogpost, etc. Please provide link to page.

Automation for Jira 19 September 2023, 13:22

Hello @Krzysztof Bogdan

This is the best moment to add more description, wire-frames, comments.
Why we doing this?
What is expected result?