Skip to content

[Due for payment 2026-04-14] Add Start/Stop timer buttons to the Chronos report header #86742

Closed

Description

@tgolen

Problem

When using chronos to track time, if you manually add time logs, then they aren't as accurate as using start/stop commands.

Solution

Make it even easier to use start/stop by adding "Start Timer" and "Stop Timer" buttons to the header of the Chronos chat.

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. self-assigned this
    on Mar 31, 2026
  2. melvin-bot commented on Mar 31, 2026

    @melvin-bot

    Auto-assigning issues to engineers is no longer supported. If you think this issue should receive engineering attention, please raise it in #whatsnext.

  3. ahmedGaber93 commented on Apr 2, 2026

    @ahmedGaber93
    Contributor

    Please assign me here since I’ve already reviewed the PR: #86690

  4. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Apr 7, 2026
  5. changed the title [-]Add Start/Stop timer buttons to the Chronos report header[/-] [+][Due for payment 2026-04-14] Add Start/Stop timer buttons to the Chronos report header[/+] on Apr 7, 2026
  6. melvin-bot commented on Apr 7, 2026

    @melvin-bot

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

  7. melvin-bot commented on Apr 7, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.53-7 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 2026-04-14. 🎊

    For reference, here are some details about the assignees on this issue:

  8. melvin-bot commented on Apr 7, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  9. ahmedGaber93 commented on Apr 13, 2026

    @ahmedGaber93
  10. tgolen commented on Apr 13, 2026

    @tgolen
    ContributorAuthor

    Since this is mostly an internal tool, let's not add regression tets for this.

  11. melvin-bot commented on Apr 14, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  12. mallenexpensify commented on Apr 16, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @ahmedGaber93 due $250 via NewDot

  13. flaviadefaria commented on Apr 29, 2026

    @flaviadefaria
    Contributor

    $250 approved for @ahmedGaber93

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 productionDailyKSv2EngineeringImprovementItem broken or needs improvement.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions