Apply Filter to new Cards
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
If a filter is applied new cards should automatically get the same tags, assigned people, etc.
Some examples from my day-to-day work with Deck.
I use deck as my personal task manager. Tasks which belong to different projects are tagged accordingly ("project 1", "project 2"). In the past I had for each project a dedicated Deck board but this didn't really scaled at the end and it was hard to have a joint overview over all current tasks.
When I want to focus on tasks of "project 1" I apply the filter accordingly. If I now add a new card, the card directly disappears after creation because it doesn't has the tag "project 1". If I create new card while focusing on "project 1" I would like that the new card gets directly the same tag.
The Sales Engineering Team at Nextcloud has a shared Deck board to keep an overview over currently running projects. Cards are assigned to the responsible Sales Engineer. Same as above, if I filter for myself and add a new card, the card disappears directly after creation because it is not assigned to myself. I have the disable the filter, find the card in a huge list of cards and assign it to me. If I look at my cards and create a new one, it is quite likely that it is also a card for me. Therefore it would be nice if all filters would be applied and the cards would be assigned automatically to myself.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing the new-card creation flow and how active filters represent tags and assignees; done means a card created under a filter receives the applicable filter values and remains visible without disabling the filter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100