Skip to content

[HOLD for payment 2023-06-28] Allow Mark as Read/Unread from LHN #20249

Closed

Description

@Gonals

Problem: In NewDot, as opposed to most chat/messaging apps, in order to mark a conversation as read/unread, users need to actually open the chat. This is not a huge inconvenience on Desktop/web, but it can be on mobile. Our very own
@ted
has expressed a need for this feature so he can keep being a terrible friend on our platform too!

Solution: We now have a long-press menu on the LHN to Pin/Unpin chats! Let’s add another option to mark them as read/unread (the last message would be marked as unread)!

Slack proposal here

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01ad862a284f6e0c5e
  • Upwork Job ID: 1666024301398683648
  • Last Price Increase: 2023-06-06

Activity

  1. self-assigned this
    on Jun 6, 2023
  2. melvin-bot commented on Jun 6, 2023

    @melvin-bot
  3. added
    InternalRequires API changes or must be handled by Expensify staff
    on Jun 6, 2023
  4. melvin-bot commented on Jun 6, 2023

    @melvin-bot
  5. melvin-bot commented on Jun 6, 2023

    @melvin-bot

    Triggered auto assignment to Contributor Plus for review of internal employee PR - @0xmiroslav (Internal)

  6. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jun 21, 2023
  7. changed the title [-]Allow Mark as Read/Unread from LHN[/-] [+][HOLD for payment 2023-06-28] Allow Mark as Read/Unread from LHN[/+] on Jun 21, 2023
  8. melvin-bot commented on Jun 21, 2023

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  9. melvin-bot commented on Jun 21, 2023

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.29-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2023-06-28. 🎊

    After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

    • External issue reporter
    • Contributor that fixed the issue
    • Contributor+ that helped on the issue and/or PR

    As a reminder, here are the bonuses/penalties that should be applied for any External issue:

    • Merged PR within 3 business days of assignment - 50% bonus
    • Merged PR more than 9 business days after assignment - 50% penalty
  10. conorpendergrast commented on Jun 21, 2023

    @conorpendergrast
    Contributor

    @Gonals This doesn't have an explicit price on the issue, so unless I hear otherwise I'll pay out @0xmiroslav the default $1000

  11. Gonals commented on Jun 21, 2023

    @Gonals
    ContributorAuthor

    @Gonals This doesn't have an explicit price on the issue, so unless I hear otherwise I'll pay out @0xmiroslav the default $1000

    That sounds reasonable!

  12. conorpendergrast commented on Jun 22, 2023

    @conorpendergrast
    Contributor

    Offer sent to @0xmiroslav via Upwork: https://www.upwork.com/ab/applicants/1666024301398683648/hired
    Once that's accepted, we'll have the wait period until June 28th and then that'll be paid out

  13. conorpendergrast commented on Jun 28, 2023

    @conorpendergrast
    Contributor

    Today is the day! Paid @0xmiroslav and ended contract. All done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2InternalRequires API changes or must be handled by Expensify staffNewFeatureSomething to build that is a new item.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions