nextcloud / nextcloud/collectives
Deck card: Labels and assigned users are not transferred when creating via “/New Deck card” in a Collectives page
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 195
- Forks
- 51
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 48
Description
Describe the bug
When a user creates a new Deck card from a Collectives page using the “/New Deck card” button, the labels (tags) and assigned users that are set in the dialog are not saved in the resulting Deck task. The due date works correctly.
To Reproduce
Steps to reproduce the behavior:
- Open a Collectives page.
- Click the “/New Deck card” button (the board‑dropdown in the top toolbar).
- Fill in the form:
-
Title – any text -
Due date – select a date (this works) -
Labels – add one or more tags -
Assignees – select one or more users - Press Create.
- Open the newly created Deck board and inspect the card.
Server details:
- Collectives app version: 4.6.1
- Nextcloud version: (34.0.4 Enterprise)
- PHP Version: 8.3.33
- Database: MariaDB 10.11.14
This issue is also reported on other Nextcloud Instances.
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
Reproduce the issue from a Collectives page using the “/New Deck card” dialog, then trace the card-creation request from the page through persistence. Compare the handling of the working due date with labels and assignees; done means newly created cards retain both selected labels and assigned users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100