nextcloud / nextcloud/deck

"Send/Post to conversation": Add an input field for a message

Open
#3,992 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

I like the feature a lot and I actually prefer it to adding comments to a card. When referencing someone in a comment, the notification just shows the AD-User's GUID and most of the time nobody responds. When posting the card to a conversation instead, people know for sure that their action is needed.

Most of the time when posting a card to a conversation, I want to add some context though. For now, I have to open the card, click "post to conversation", select the recipient, go to Talk, open the conversation I posted to, send an additional message where I describe the context and then I go back to Deck and continue my work.

It would be far easier when I select "post to conversation" and could directly write that message in the lower half of the conversation selection window before clicking the confirmation button. Additionally, I would like to see #3180 implemented. Having to open the card every time I want to send it (and move the cursor to a totally different area of the screen!) makes it much more cumbersome than it should be.

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

Start by tracing the Deck action labeled “post to conversation” and the conversation selection window described in the issue; also review related issue #3180. Done means the selection flow accepts context text and sends it with the card to the chosen conversation without requiring a separate Talk step.

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
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.