nextcloud / nextcloud/forms

Ability to create a task or deck card from a single response

Open
#1,772 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement integration
Dominant language
JavaScript
Stars
382
Forks
127
Avg merge
19h 31m
Merged PRs (30d)
75

Description

Nextcloud (please complete the following information):

  • Nextcloud-Version: 27.1.3
  • Forms-Version: 3.3.1

Is your feature request related to a problem? Please describe.
I created a form to gather subscription interest from future members of our association. Every time a new person fills out the form I need to create a Deck card to track the subscription procedure (e.g. paper module + id card submission + payment + account creation etc...).

Describe the solution you'd like
It would be easier to track things to do if I could create a task or Deck card directly from Forms single response. I think this could be useful also for other people and other cases as the form data usually have to be processed later anyway.
In case of a high number of Forms responses this could be solved better by an automatic Flow that creates tasks or cards in a certain board when there are new responses.
The title of the cards/tasks could be one text field or the combination of more text fields to be chosen from the form (e.g. Name + Surname) and the description of Deck card or the notes of tasks could store the other data from the form.

Describe alternatives you've considered
The alternative is manually creating the Deck cards or tasks but it can be tedious or time consuming when you have a lot of form responses.

Additional context
None.

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 files or tests. Start by tracing how a single Forms response is viewed and how integrations with Tasks, Deck, and Flow are exposed; define the supported field mappings and trigger behavior, then verify that a response can create the requested task or card with selected form data.

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
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.