nextcloud / nextcloud/deck

Move cards to other boards - Handling of tags & assignees

Open
#1,832 4 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug concept feature parity feature: sharing feature: tags integration
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

This is a discussion about the new feature "Move cards to other boards".

On the UI the tags and assignees of the old board are shown, therefore i guess you don't handle them.

This can (probably will) lead to strange errors when synchronizing - tags do exist, don't exist assigned users might exist or not - or have no permissions at this board. The web interface for example does not allow editing tags which are brought from other boards, in the board details such tags aren't displayed, one cannot filter for them etc.

I think you need a better handling here. Something like:

Tags

  • If a tag with the same text exists, assign this tag instead of the other
  • If no similar tag exists:
    • If user has permission to create tags, create a tag with this color and text and assign it
    • Else remove this tag from the card

grafik

Assignees

  • If the user which is assigned to the card has at least view permission at the board, keep it
  • Else de-assign the user from the card.

grafik

@desperateCoder this might really break a lot of stuff when syncing, be prepared 😄 We also will have to implement this behavior for https://github.com/stefan-niedermann/nextcloud-deck/issues/453 on our side, so i would appreciate a common solution here.

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

The issue names no implementation files, tests, or entry points. First locate the move-card synchronization path and its tag and assignee handling; done means moved cards use valid board tags and retain only permitted assignees without synchronization errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.