starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 13:55:59 +03:00

[GH-ISSUE #1230] Custom Text field with predefined label/caption #344

New issue

Closed

opened 2026-02-26 18:46:36 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 18:46:36 +03:00

Owner

Originally created by @Rainson12 on GitHub (Jul 15, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/1230

Feature Description

As a Signer I would like to know what I should enter in the Custom Text field as it always is presented as Text. For example, should I enter my Company name? My Position? My cars license plate?

Use Case

A common scenario is to ask for the Title/Position of the Signer (eg. CEO/VP etc.). When now sending a request for Signing it will show Signature and Text where as the User doesnt know what the Text stands for. This is especially usefull when defining templates.

Currently it looks like:

Instead it should look like this:

Proposed Solution

When adding a custom text field, also define a caption what will be shown to the user/signer. This way the user knows what has to be entered in such field.

Alternatives (optional)

Configure / Define static fields in an administration interface. Like one for Position or Title.

Additional Context

No response

Please check the boxes that apply to this feature request.

I have searched the existing feature requests to make sure this is not a duplicate.
I have provided a detailed description of the requested feature.
I have explained the use case or scenario for this feature.
I have included any relevant technical details or design suggestions.
I understand that this is a suggestion and that there is no guarantee of implementation.
I want to work on creating a PR for this issue if approved

Originally created by @Rainson12 on GitHub (Jul 15, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/1230 ### Feature Description As a Signer I would like to know what I should enter in the `Custom Text` field as it always is presented as `Text`. For example, should I enter my Company name? My Position? My cars license plate? ### Use Case A common scenario is to ask for the Title/Position of the Signer (eg. CEO/VP etc.). When now sending a request for Signing it will show `Signature` and `Text` where as the User doesnt know what the `Text` stands for. This is especially usefull when defining templates. Currently it looks like: ![image](https://github.com/user-attachments/assets/57a81c75-90d7-42d6-ae36-7f4891d57042) Instead it should look like this: ![image](https://github.com/user-attachments/assets/fc1bdbda-75b8-4f62-8ead-575269044954) ### Proposed Solution When adding a custom text field, also define a caption what will be shown to the user/signer. This way the user knows what has to be entered in such field. ### Alternatives (optional) Configure / Define static fields in an administration interface. Like one for `Position` or `Title`. ### Additional Context _No response_ ### Please check the boxes that apply to this feature request. - [X] I have searched the existing feature requests to make sure this is not a duplicate. - [X] I have provided a detailed description of the requested feature. - [X] I have explained the use case or scenario for this feature. - [X] I have included any relevant technical details or design suggestions. - [X] I understand that this is a suggestion and that there is no guarantee of implementation. - [ ] I want to work on creating a PR for this issue if approved

kerem

2026-02-26 18:46:36 +03:00

closed this issue
added the
status: triage
label

kerem commented

2026-02-26 18:46:37 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 15, 2024):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

@github-actions[bot] commented on GitHub (Jul 15, 2024): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)

kerem commented

2026-02-26 18:46:37 +03:00

Author

Owner

@Rainson12 commented on GitHub (Jul 15, 2024):

Seems that there is already a branch: https://github.com/documenso/documenso/tree/feat/more-field-types
and PR https://github.com/documenso/documenso/pull/1141 for this although I couldn't find any issue. I will close this for now

@Rainson12 commented on GitHub (Jul 15, 2024): Seems that there is already a branch: https://github.com/documenso/documenso/tree/feat/more-field-types and PR https://github.com/documenso/documenso/pull/1141 for this although I couldn't find any issue. I will close this for now

kerem commented

2026-02-26 18:46:37 +03:00

Author

Owner

@ElTimuro commented on GitHub (Jul 16, 2024):

@Rainson12 This was on our internal roadmap, as we like to tackle core features via the core team. Still great thinking. It's been a while, advanced fields will land very soon.

@ElTimuro commented on GitHub (Jul 16, 2024): @Rainson12 This was on our internal roadmap, as we like to tackle core features via the core team. Still great thinking. It's been a while, advanced fields will land very soon.

kerem commented

2026-02-26 18:46:37 +03:00

Author

Owner

@Rainson12 commented on GitHub (Jul 16, 2024):

@ElTimuro yeah I saw that as well. Started reviewing the PR and integrating it into my fork to already have a chance to look at it. Great work!

@Rainson12 commented on GitHub (Jul 16, 2024): @ElTimuro yeah I saw that as well. Started reviewing the PR and integrating it into my fork to already have a chance to look at it. Great work!

kerem referenced this issue

2026-02-26 19:30:57 +03:00

[PR #344] [MERGED] chore: add some eslint rules #896

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#344

No description provided.

Rows
Columns