starred/documenso

Fork 0

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

[GH-ISSUE #710] [DOC-376] No jump to sign field #210

New issue

Closed

opened 2026-02-26 18:45:53 +03:00 by kerem · 7 comments

kerem commented

2026-02-26 18:45:53 +03:00

Owner

Originally created by @ElTimuro on GitHub (Dec 1, 2023).
Original GitHub issue: https://github.com/documenso/documenso/issues/710

Originally assigned to: @catalinpit on GitHub.

When the user already has a signature in their account, the complete button is disabled, forcing them to scroll through the doc and click each field manually.
When clicked on complete, the auto-scroll to open field should also be triggered.

_{From SyncLinear.com | DOC-376}

Originally created by @ElTimuro on GitHub (Dec 1, 2023). Original GitHub issue: https://github.com/documenso/documenso/issues/710 Originally assigned to: @catalinpit on GitHub. ![image.png](https://uploads.linear.app/884f43d5-69da-459d-bc6b-864f16914e0f/cfb8b919-9780-401d-a927-09aec7ab57c9/91e90dc1-1c4e-4447-b8e1-db4590f2424b?signature=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJwYXRoIjoiLzg4NGY0M2Q1LTY5ZGEtNDU5ZC1iYzZiLTg2NGYxNjkxNGUwZi9jZmI4YjkxOS05NzgwLTQwMWQtYTkyNy0wOWFlYzdhYjU3YzkvOTFlOTBkYzEtMWM0ZS00NDQ3LWI4ZTEtZGI0NTkwZjI0MjRiIiwiaWF0IjoxNzAxNDcwMTQxLCJleHAiOjE3MDE1NTY1NDF9.Lo77tPPabVngXJHO3abGFDlGtUYsx5u_GzUUTOtxj88) * When the user already has a signature in their account, the complete button is disabled, forcing them to scroll through the doc and click each field manually. * When clicked on complete, the auto-scroll to open field should also be triggered. <sub>From [SyncLinear.com](https://synclinear.com) | [DOC-376](https://linear.app/documenso/issue/DOC-376/no-jump-to-sign-field)</sub>

kerem closed this issue

2026-02-26 18:45:53 +03:00

kerem commented

2026-02-26 18:45:54 +03:00

Author

Owner

@ksushant6566 commented on GitHub (Dec 5, 2023):

Hey @ElTimuro @Mythie , if I understand this correctly the complete button shouldn't be disabled and when clicked should trigger scroll to the first field in the document right?

also wdym by open field here?

attaching a loom: https://www.loom.com/share/25d099d8557e4b1688b0f139bb75f1ff?sid=cc9dac8e-3a10-446a-8a8f-58946e071fef

@ksushant6566 commented on GitHub (Dec 5, 2023): Hey @ElTimuro @Mythie , if I understand this correctly the complete button shouldn't be disabled and when clicked should trigger scroll to the first field in the document right? also wdym by `open field` here? attaching a loom: https://www.loom.com/share/25d099d8557e4b1688b0f139bb75f1ff?sid=cc9dac8e-3a10-446a-8a8f-58946e071fef

kerem commented

2026-02-26 18:45:54 +03:00

Author

Owner

@catalinpit commented on GitHub (Jan 4, 2024):

Hey, just to make sure I understand this. When the user has a signature AND clicks the first signature field, should the app take the user to the next field automatically OR should the app complete all the signature fields?

@catalinpit commented on GitHub (Jan 4, 2024): Hey, just to make sure I understand this. When the user has a signature **AND** clicks the first signature field, should the app take the user to the next field automatically **OR** should the app complete all the signature fields?

kerem commented

2026-02-26 18:45:54 +03:00

Author

Owner

@ElTimuro commented on GitHub (Jan 4, 2024):

Complete should be clickable but if not all fields are signed, jump to the next open field. click to sign. its not legal to autofill all sadly

@ElTimuro commented on GitHub (Jan 4, 2024): Complete should be clickable but if not all fields are signed, jump to the next open field. click to sign. its not legal to autofill all sadly

kerem commented

2026-02-26 18:45:54 +03:00

Author

Owner

@ElTimuro commented on GitHub (Jan 4, 2024):

signing the big field could also trigger going to the next open one, if that can work smoothly.
the open field trigger a dialog, if the big field is not signed

@ElTimuro commented on GitHub (Jan 4, 2024): signing the big field could also trigger going to the next open one, if that can work smoothly. the open field trigger a dialog, if the big field is not signed

kerem commented

2026-02-26 18:45:54 +03:00

Author

Owner

@ksushant6566 commented on GitHub (Jan 4, 2024):

Complete should be clickable but if not all fields are signed, jump to the next open field. click to sign. its not legal to autofill all sadly

Hey guys, this behaviour was achieved in PR #729 but I see that PR is now outdated now. Would you like me to update it?

@ksushant6566 commented on GitHub (Jan 4, 2024): > Complete should be clickable but if not all fields are signed, jump to the next open field. click to sign. its not legal to autofill all sadly Hey guys, this behaviour was achieved in PR #729 but I see that PR is now outdated now. Would you like me to update it?

kerem commented

2026-02-26 18:45:54 +03:00

Author

Owner

@ksushant6566 commented on GitHub (Jan 4, 2024):

signing the big field could also trigger going to the next open one, if that can work smoothly. the open field trigger a dialog, if the big field is not signed

not sure what is meant by big field here?

@ksushant6566 commented on GitHub (Jan 4, 2024): > signing the big field could also trigger going to the next open one, if that can work smoothly. the open field trigger a dialog, if the big field is not signed not sure what is meant by big field here?

kerem commented

2026-02-26 18:45:54 +03:00

Author

Owner

@ElTimuro commented on GitHub (Jan 10, 2024):

marked as done on GH

@ElTimuro commented on GitHub (Jan 10, 2024): marked as done on GH

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#210

No description provided.

Rows
Columns