> For the complete documentation index, see [llms.txt](https://docs.xto10x.com/product-okr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xto10x.com/product-okr/incoming-feature-requests/drag-and-drop.md).

# Drag and Drop (Upcoming)

## Problem Statement

Some of the earliest feedback in our beta is around the hustle of moving and re-arranging KRs.\
Below is a list of use-cases for scoping this problem:

* A user wants to re-arrange the order of their Objectives. (>90%)
* A user wants to re-arrange the order of their KR's. \[Same as previous but within an O] (>90%)
* A user wants to move a KR from one O to another O. (25%)
* A user want to move a KR from an objective to make it an independent objective \[Non-aligned objective] \~ (<5%)
* A user wants to move some/ all of the KR's from one objective to another objective. \
  \[This objective may or may-not have existing KRs] \~20% of 25% (second case)
* A user wants to move a non-aligned objective to an already existing objective.

{% hint style="success" %}
Note: Once an objective is moved (its moved with all its KR's under it)
{% endhint %}

## Solutions to explore

* Monday
* to do apps

## What impact it has on our sorting logic?

{% hint style="success" %}
Note: When a user does a drag and drop, we would have to respect the user's sorting order and would have to move away from the default sorting logic.&#x20;
{% endhint %}

{% hint style="danger" %}
It shouldn't be that a user has changed/ re-arranged something and the next time they see some other order. The drag and drop overrides our sorting order.&#x20;
{% endhint %}

<br>