-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notes Field with date tag. #28
Comments
Is it truly necessary for the broader audience to keep tabs on when the notes were written? |
The date stamp would be a nice to have as I'm used to it from a previously used p/w safe. But it's not a necessity if hard to implement. |
Have you had any further progress? I would be happy to beta test any enhancements. |
Thank you for your continued interest in KeyGo and your willingness to beta test enhancements. Unfortunately, I haven't had the time to make progress on adding the timestamp feature you requested over the past few months. However, I did implement a note feature in a branch (not published yet and without timestaps). In the meantime, you can use the tag feature. However, I'm still uncertain whether the note feature will make it into a stable release, as notes and tags serve similar purposes, albeit notes can be longer. I appreciate your understanding and patience! If you have any more feedback or questions, feel free to let me know. |
Thanks for the update.
Martin
…On 14 May 2024 2:36:26 am AEST, Davis ***@***.***> wrote:
Thank you for your continued interest in KeyGo and your willingness to
beta test enhancements.
Unfortunately, I haven't had the time to make progress on adding the
timestamp feature you requested over the past few months. However, I
did implement a note feature in a branch (not published yet and without
timestaps). In the meantime, you can use the tag feature. However, I'm
still uncertain whether the note feature will make it into a stable
release, as notes and tags serve similar purposes, albeit notes can be
longer.
I appreciate your understanding and patience! If you have any more
feedback or questions, feel free to let me know.
--
Reply to this email directly or view it on GitHub:
#28 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
Thanks for the heads up. The notes feature you mentioned would be great, more usable than the tag feature for me at least. Don't worry about the time-stamp as it's easy enough to manually date entries in notes if needed. Thanks again.
…On 14 May 2024 2:36:26 am AEST, Davis ***@***.***> wrote:
Thank you for your continued interest in KeyGo and your willingness to
beta test enhancements.
Unfortunately, I haven't had the time to make progress on adding the
timestamp feature you requested over the past few months. However, I
did implement a note feature in a branch (not published yet and without
timestaps). In the meantime, you can use the tag feature. However, I'm
still uncertain whether the note feature will make it into a stable
release, as notes and tags serve similar purposes, albeit notes can be
longer.
I appreciate your understanding and patience! If you have any more
feedback or questions, feel free to let me know.
--
Reply to this email directly or view it on GitHub:
#28 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
Feature Request Template
Description:
A notes field with date stamp to be included along with password and user name.
Problem/Use Case:
When logging into banks I have multiple accounts with some. It would be great to have a notes field so I can list further details regarding the accounts. Verbal passwords and other notes that are needed.
Proposed Solution:
A text box/section where I can type notes and have it date stamped so I can keep tabs on when I wrote it.
Benefits:
I need more information kept securely for bank accounts. It could be added below the password field and above the tags field.
I do hope that this wouldn't be too difficult to add to KeyGo.
Thank you for considering my request.
The text was updated successfully, but these errors were encountered: