Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

STATUS field instead of using multiple lists (again and again) #5791

Open
lauff opened this issue Apr 22, 2024 · 0 comments
Open

STATUS field instead of using multiple lists (again and again) #5791

lauff opened this issue Apr 22, 2024 · 0 comments

Comments

@lauff
Copy link

lauff commented Apr 22, 2024

How to use GitHub

  • Please use the 馃憤 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

As is

Today Deck uses multiple lists (e.g. open / in progress / done) to reflect the status of the card.
The disadvantages are, that

  • those lists are usually again and again created for most boards.
  • the semantic status is not captured (instead it is hidden in the name of the list, e.g. open)
  • the overview shows the different status lists multiple times, because it "does not know about them"

Describe the solution you'd like

I would suggest to have a "status" field available, that allows to flag (e.g.) open, in progress, done.

At best, the list of statuses would be configurable (even per board) (e.g. open, in preparation, in progress, done). But the basic set above would be a very good starting point.

Having this, the deck views would nicely allow filtering for this.
Additionally, setting the status could be easily done by dragging between the columns in a respective "status view".

Already discussed?

I wonder why this request is not yet already on the issue list, at least I did not find it.
Please let me know, if this was already discussed and excuse that I did not find / refer to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants