You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
⚠️ It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time ⚠️
@mananjadhav, it's best practice to split out individual components into individual issues so the main tracking issue isn't overwhelmed with comments. Since we've completed all other dev already, working on the tracking issue isn't causing confusion, but in the future, I'd recommend keeping your comments on the specific issue you're working on instead of the broader tracking one.
Activity
melvin-bot commentedon Mar 19, 2025
Triggered auto assignment to @dylanexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.lakchote commentedon Mar 19, 2025
Not a bug, unassigning.
melvin-bot commentedon Mar 19, 2025
Current assignee @dylanexpensify is eligible for the NewFeature assigner, not assigning anyone new.
melvin-bot commentedon Mar 19, 2025
30 remaining items
mananjadhav commentedon May 7, 2025
I am tracking the code with #52049. Will be posting questions/updates there.
melvin-bot commentedon May 13, 2025
@mananjadhav Huh... This is 4 days overdue. Who can take care of this?
garrettmknight commentedon May 14, 2025
Still making progress in the other issue.
melvin-bot commentedon May 15, 2025
@mananjadhav Still overdue 6 days?! Let's take care of this!
mananjadhav commentedon May 15, 2025
Making progress in the linked issue. @garrettmknight Is there a reason we have two issues to track the same feature?
melvin-bot commentedon May 19, 2025
@mananjadhav Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
garrettmknight commentedon May 19, 2025
@mananjadhav, it's best practice to split out individual components into individual issues so the main tracking issue isn't overwhelmed with comments. Since we've completed all other dev already, working on the tracking issue isn't causing confusion, but in the future, I'd recommend keeping your comments on the specific issue you're working on instead of the broader tracking one.