Dokploy / Dokploy/dokploy

Add drag-and-drop or frequency-based sorting for services and projects

Open
#2,398 0 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

What problem will this feature address?

I often get frustrated that I can’t sort my services and projects in the order I want. It’s difficult to keep the most frequently used services at the top. Current sorting options don’t solve this, so I often waste time scrolling. Sometimes I even create placeholder services just to keep things in position, which isn’t ideal.

Describe the solution you'd like

Add a drag-and-drop feature for services and projects, allowing users to arrange them in a custom order. The chosen order should be saved and shown consistently across sessions. This makes it easier to keep related services grouped and to put each service in a place that the user is comfortable with.

Describe alternatives you've considered

I’ve tried using the existing sorting options (by name, date, etc.), but they don’t let me group related services together in the way I want. I also created placeholder services to keep future projects in position, but that feels like a workaround rather than a real solution. But I can suggest adding a frequency-based sorting option if the drag-and-drop is too much for now.

Additional context

Being able to organize services and projects visually with drag-and-drop would make the dashboard easier to navigate, especially for larger deployments. It would reduce clutter, save time, and improve overall usability. A simple, intuitive feature like this would bring flexibility that many teams need when managing complex environments.

Will you send a PR to implement it?

No

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the dashboard code that renders services and projects and its existing sorting behavior, then trace how user preferences are persisted. Done means users can reorder both lists, the chosen order is retained across sessions, and the behavior is covered by the project’s relevant tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.