Skip to content

Conversation

@grnd-alt
Copy link
Member

@grnd-alt grnd-alt commented Jan 6, 2026

Summary

Thanks to @theoholl for coming up with a contribution.
This is a simpler fix, to not over complicate the card store logic.

We should think about some refinements to the way labels are added in the frontend in general though.
(we have no description at all on what kind of props 'addLabel' requires e.g.)

Checklist

  • Code is properly formatted
  • Sign-off message is added to all commits
  • Tests (unit, integration, api and/or acceptance) are included
  • Documentation (manuals or wiki) has been updated or is not required

@theoholl
Copy link
Contributor

theoholl commented Jan 6, 2026

Brilliant, this looks like a clean and simple solution! Thank you! :octocat:

@grnd-alt grnd-alt force-pushed the fix/6680-adding-a-new-tag-to-a-card-has-unexpected-behaviour branch from 3517c81 to 41cb63f Compare January 12, 2026 14:00
@github-project-automation github-project-automation bot moved this to 🧭 Planning evaluation (don't pick) in 📝 Office team Jan 15, 2026
@grnd-alt grnd-alt moved this from 🧭 Planning evaluation (don't pick) to 👀 In review in 📝 Office team Jan 15, 2026
@grnd-alt grnd-alt self-assigned this Jan 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 👀 In review

Development

Successfully merging this pull request may close these issues.

Adding a new tag to a card has unexpected behaviour

3 participants