github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-07 03:23:29 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #4780] Reopen 4659 or improve tracking of unreleased fixes #50265

New Issue
Closed
opened 2026-05-01 12:16:32 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-05-01 12:16:32 -05:00
Owner
Copy Link

Originally created by @mwisnicki on GitHub (Feb 25, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/4780

Steps To Reproduce

Can you please consider ways of improving communication around progress of fixed bugs such as #4659?

Bugs are closed without a comment and not released for weeks or months while frustrated users keep asking about status or reopening or upvoting such comments.

A simple label would do and a milestone with due date for ETA of upcoming version that has this fix.

I know you track that in external system but that doesn't help your users or customers. Perhaps you can export them from that system or expose it in some way, even if only for paying customers. Note that reaching out to customer service is nowhere near convenient.

Expected Result

Users are informed and can easily track issues until actual resolution.

Actual Result

Your users, including paying customers waste time and get frustrated.

Screenshots or Videos

No response

Additional Context

No response

Build Version

0

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Samsung S25 Ultra
Android 15

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Originally created by @mwisnicki on GitHub (Feb 25, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/4780 ### Steps To Reproduce Can you please consider ways of improving communication around progress of fixed bugs such as #4659? Bugs are closed without a comment and not released for weeks or months while frustrated users keep asking about status or reopening or upvoting such comments. A simple label would do and a milestone with due date for ETA of upcoming version that has this fix. I know you track that in external system but that doesn't help your users or customers. Perhaps you can export them from that system or expose it in some way, even if only for paying customers. Note that reaching out to customer service is nowhere near convenient. ### Expected Result Users are informed and can easily track issues until actual resolution. ### Actual Result Your users, including paying customers waste time and get frustrated. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version 0 ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details Samsung S25 Ultra Android 15 ### Issue Tracking Info - [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
GiteaMirror added the bug label 2026-05-01 12:16:32 -05:00
GiteaMirror commented 2026-05-01 12:16:34 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Feb 25, 2025):

Thank you for your report! We've added this to our internal board for review.
ID: PM-18592

<!-- gh-comment-id:2680220310 --> @bitwarden-bot commented on GitHub (Feb 25, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-18592
GiteaMirror commented 2026-05-01 12:16:35 -05:00
Author
Owner
Copy Link

@parcelcat commented on GitHub (Feb 27, 2025):

Pull request #4696 is supposed to resolve issue #4659. I assume it was closed for this reason.

<!-- gh-comment-id:2688681665 --> @parcelcat commented on GitHub (Feb 27, 2025): Pull request #4696 is supposed to resolve issue #4659. I assume it was closed for this reason.
GiteaMirror commented 2026-05-01 12:16:36 -05:00
Author
Owner
Copy Link

@MarikaBW commented on GitHub (Mar 2, 2025):

Hi there,

@parcelcat is correct, the pull request is supposed to resolve issue #4659 hence why it was closed.

Feel free to reach out to the support team if you have any further queries.

The issue here will be closed.

Thanks!

<!-- gh-comment-id:2692958156 --> @MarikaBW commented on GitHub (Mar 2, 2025): Hi there, @parcelcat is correct, the pull request is supposed to resolve issue #4659 hence why it was closed. Feel free to reach out to the support team if you have any further queries. The issue here will be closed. Thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#50265
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?