Feature request: card archiving option #518

New Issue

OVERLORD · 2026-02-04T20:07:07+03:00

OVERLORD commented

2026-02-04 20:07:07 +03:00

Originally created by @prxgma on GitHub (May 31, 2024).

Hiya, I was looking to suggest a way of archiving cards/lists the way Trello has always done, so that things are more neatly cleaned up on the face of a board, to also further help reduce lag etc. while maintaining the ability to search the board & automatically look through the archives of the board in question at the same time.

Originally created by @prxgma on GitHub (May 31, 2024). Hiya, I was looking to suggest a way of archiving cards/lists the way Trello has always done, so that things are more neatly cleaned up on the face of a board, to also further help reduce lag etc. while maintaining the ability to search the board & automatically look through the archives of the board in question at the same time.

OVERLORD added the enhancement label 2026-02-04 20:07:07 +03:00

OVERLORD closed this issue

2026-02-04 20:07:09 +03:00

OVERLORD commented

2026-02-04 20:07:20 +03:00

@meltyshev commented on GitHub (Jun 1, 2024):

Hi! We've already solve this in the v2, but it's not yet publicly available.

@meltyshev commented on GitHub (Jun 1, 2024): Hi! We've already solve this in the v2, but it's not yet publicly available.

OVERLORD commented

2026-02-04 20:07:32 +03:00

@UnverifiedContact commented on GitHub (Jul 17, 2024):

Hi! We've already solve this in the v2, but it's not yet publicly available.

Hi @meltyshev do you have any word on roughly when v2 might be made public?

Also, how come you guys are doing work on branches you don't make public? Why do that?

@UnverifiedContact commented on GitHub (Jul 17, 2024): > Hi! We've already solve this in the v2, but it's not yet publicly available. Hi @meltyshev do you have any word on roughly when v2 might be made public? Also, how come you guys are doing work on branches you don't make public? Why do that?

OVERLORD commented

2026-02-04 20:07:45 +03:00

@meltyshev commented on GitHub (Jul 17, 2024):

Hi @meltyshev do you have any word on roughly when v2 might be made public?

Hi! We still can't provide any date, but we're trying to release v2 as soon as possible.

Also, how come you guys are doing work on branches you don't make public? Why do that?

It's easier for us to do it in a private repository, because otherwise people will try to use an unfinished version, write issues that we'll have to respond to, even though some parts may not work simply because they're not ready yet. In short, maintaining both versions at the same time is hard, time-consuming and distracting, which only slows down development.

@meltyshev commented on GitHub (Jul 17, 2024): > Hi @meltyshev do you have any word on roughly when v2 might be made public? Hi! We still can't provide any date, but we're trying to release v2 as soon as possible. > Also, how come you guys are doing work on branches you don't make public? Why do that? It's easier for us to do it in a private repository, because otherwise people will try to use an unfinished version, write issues that we'll have to respond to, even though some parts may not work simply because they're not ready yet. In short, maintaining both versions at the same time is hard, time-consuming and distracting, which only slows down development.

OVERLORD commented

2026-02-04 20:07:49 +03:00

@denilsonsa commented on GitHub (Sep 14, 2024):

Looks like a duplicate of #456

@denilsonsa commented on GitHub (Sep 14, 2024): Looks like a duplicate of #456

OVERLORD commented

2026-02-04 20:07:53 +03:00

@meltyshev commented on GitHub (May 13, 2025):

This should be resolved in v2, but feel free to reopen if the issue persists.

@meltyshev commented on GitHub (May 13, 2025): This should be resolved in v2, but feel free to reopen if the issue persists.

OVERLORD referenced this issue

2026-02-04 21:45:14 +03:00