nextcloud / nextcloud/integration_docusign

[Feature request] Use the Requester user/mail from Nextcloud in the Docuware mail

Open
#170 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
6
Forks
1
Avg merge
1d 6h
Merged PRs (30d)
6

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • 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.

Feature request

Which Nextcloud Version are you currently using: (see administration page)
31.0.6

Is your feature request related to a problem? Please describe.
It would be nice if the requester of the Signature would be mentioned in the email that Docuware is sending.
Currently the main/dummy user in Docuware is always the requester for the Signature.

Current workflow:
Nextcloud user (user A) requests a signature from user (user B), Docuware sents an email with the following text: Company XYZ is requesting a signature.

Describe the solution you'd like
Requester of the signature to be the requester in the Docuware Mail.

Solution:
Nextcloud user (user A) requests a signature from user (user B), Docuware sents an email with the following text: User A is requesting a signature.

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, tests, or entry points; start by tracing where the DocuSign email is created and how the Nextcloud requester is passed into that workflow. Verify the result against the two-user example so the DocuSign message identifies user A rather than the main or dummy user.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.