nextcloud / nextcloud/deck

Forms integration

Open
#7,103 2 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement needs discussion
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Nextcloud (please complete the following information):

  • Nextcloud-Version: 31.0.6
  • Forms-Version: 5.1.2

Is your feature request related to a problem? Please describe.
I use both Forms and Deck in my workflow: my clients fill in a form, requesting me to do a task, and then I track progress on each task using a Deck card.
Working with Deck cards is very intuitive, but currently I have to manually create a card for each form submission, which is error-prone.

Describe the solution you'd like
I would love Deck to integrate with Flow (so that a Deck card can be created e.g. on a file edit). I would specifically love a Deck card creation to occur whenever someone submits an answer to a form.

Describe alternatives you've considered
There are push and email notifications for submissions. Maybe a card could be created from an activity notification or from an email.

Additional context
I also filed https://github.com/nextcloud/forms/issues/2814 for completeness, since I believe neither side is really ready for integration.

This might be a duplicate of #1722 but I thought the use case is separate enough from what was raised there. The official Flow announcement pitched Deck card creation specifically, so I think this is already known to be extremely useful.

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 reading this issue with Forms #2814 and the possible duplicate Deck #1722; no files, tests, or entry points are named. The requested outcome is an agreed integration that creates a Deck card when a Forms submission arrives, but the cross-app scope and Flow approach still need definition.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.