LibreSign / LibreSign/libresign
Require at least one signature field before sending document
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 818
- Forks
- 146
- Avg merge
- 10h 53m
- Merged PRs (30d)
- 353
Description
Is your feature request related to a problem? Please describe.
As a document creator in LibreSign, I can send a document to a
signer without placing any signature fields. This leads to confusion
for the recipient, who receives a document but has no idea where
or whether they need to sign.
Describe the solution you'd like
LibreSign should validate before sending a document that at least
one signature field has been placed. If no signature field exists,
the send button should be disabled or a warning message should
appear, preventing the document from being sent without a
designated signing area.
Describe alternatives you've considered
Currently the only alternative is an internal policy reminding
creators to always place signature fields manually. This is
error-prone and not a reliable solution, especially for teams
with multiple users.
Additional context
This would significantly improve the user experience for both
document creators and recipients. It is a common validation
feature in other signing tools like DocuSign or Adobe Sign and
would make LibreSign more professional and reliable for
business use.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the document-send flow and the send button's handling of placed signature fields. Verify how the interface detects whether any signature field exists, then confirm that a document with none cannot be sent and that the warning or disabled state is clear to the creator.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100