[GH-ISSUE #1765] Old issues needing closing #508

New issue

Closed

opened 2026-02-26 18:47:21 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 18:47:21 +03:00

Owner

Originally created by @Novapixel1010 on GitHub (Apr 27, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/1765

Describe the improvement you are suggesting in detail

I have notice a few old issues that seem to have been fixed but never closed. I would be willing to test and make the sure issue is actually fixed and then close it. I would also be willing to help with docs if there is a github for it.

My rational is having less issue open can avoid confusion. Be leaving a closing comment of the fix and link to the docs.

Additional Information & Alternatives (optional)

sorry about the rant

And also I would love to see this project pass the project docuseal 😆 because charging people for api access when you are hosting the api is wild. Also charging monthly to have basic white-labeling like a logo. I would understand a onetime fee but monthly not going to work for small business.

Do you want to work on this improvement?

Yes

Please check the boxes that apply to this improvement suggestion.

I have searched the existing issues and improvement suggestions to avoid duplication.
I have provided a clear description of the improvement being suggested.
I have explained the rationale behind this improvement.
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.

Originally created by @Novapixel1010 on GitHub (Apr 27, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/1765 ### Describe the improvement you are suggesting in detail I have notice a few old issues that seem to have been fixed but never closed. I would be willing to test and make the sure issue is actually fixed and then close it. I would also be willing to help with docs if there is a github for it. My rational is having less issue open can avoid confusion. Be leaving a closing comment of the fix and link to the docs. ### Additional Information & Alternatives (optional) ### sorry about the rant And also I would love to see this project pass the project docuseal 😆 because charging people for api access when you are hosting the api is wild. Also charging monthly to have basic white-labeling like a logo. I would understand a onetime fee but monthly not going to work for small business. ### Do you want to work on this improvement? Yes ### Please check the boxes that apply to this improvement suggestion. - [ ] I have searched the existing issues and improvement suggestions to avoid duplication. - [x] I have provided a clear description of the improvement being suggested. - [x] I have explained the rationale behind this improvement. - [ ] 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.

kerem

2026-02-26 18:47:21 +03:00

closed this issue
added the
Stale

status: triage
labels

kerem commented

2026-02-26 18:47:21 +03:00

Author

Owner

@ephraimduncan commented on GitHub (Aug 23, 2025):

Hi, the docs for the project are in the same repo. We'd love your contributions.

@ephraimduncan commented on GitHub (Aug 23, 2025): Hi, the docs for the project are in the same repo. We'd love your contributions.

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

No description provided.

Rows
Columns