Skip to content
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

[HOLD for payment 2023-08-10] [$1000] System messages for tasks are wrong/inconsistent with other report patterns #23304

Closed
1 of 6 tasks
kavimuru opened this issue Jul 20, 2023 · 41 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 External Added to denote the issue can be worked on by a contributor

Comments

@kavimuru
Copy link

kavimuru commented Jul 20, 2023

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Create a task with
  2. Assign whoever you’d like
  3. Mark the task as done

Expected Result:

The system message should appear in all grey supporting text

Actual Result:

“Completed task” is oddly hyperlinked (why?) and the text fails to use support text, like all other system messages

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.3.43-2
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Screenshot 2023-07-18 at 23 38 22

Recording.1297.mp4

Expensify/Expensify Issue URL:
Issue reported by: @JmillsExpensify
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1689745091154569

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~017ea86167d179c7a2
  • Upwork Job ID: 1684032060275773440
  • Last Price Increase: 2023-07-26
@kavimuru kavimuru added Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Jul 20, 2023
@DanutGavrus
Copy link
Contributor

Proposal

Please re-state the problem that we are trying to solve in this issue.

System messages for tasks are wrong/inconsistent with other report patterns

What is the root cause of that problem?

In TaskAction, we use the chatItemMessageLink style even if the text is not a link:

<View style={[styles.flex1, styles.flexRow, styles.alignItemsCenter]}>
<Text>
<Text style={styles.chatItemMessageLink}>{messageLinkText}</Text>
<Text style={[styles.chatItemMessage]}>{` ${taskReportName}`}</Text>
</Text>
</View>

What changes do you think we should make in order to solve the problem?

We should replace it with another style which meets our desired style. If we want it to be gray, we should choose a style which has color: themeColors.textSupporting in it(such as mutedTextLabel or colorMuted or another existing one). If we want to apply other styling too and no existing one meets all our requirements, then we should create a new style for using it here. Decision depends on the output desired by the design team.

@melvin-bot
Copy link

melvin-bot bot commented Jul 20, 2023

Triggered auto assignment to @mallenexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

@melvin-bot
Copy link

melvin-bot bot commented Jul 20, 2023

Bug0 Triage Checklist (Main S/O)

  • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
  • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
    • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
  • This bug is reproducible using the reproduction steps in the OP. S/O
    • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
    • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
  • This issue is filled out as thoroughly and clearly as possible
    • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
  • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@neonbhai
Copy link
Contributor

neonbhai commented Jul 21, 2023

Proposal

Please re-state the problem that we are trying to solve in this issue.

System messages for tasks are wrong/inconsistent with other report patterns

What is the root cause of that problem?

The styles applied to the system message is styles.messageLinkText which is blue and looks inconsistent with other System messages

What changes do you think we should make in order to solve the problem?

  • We should change the styles of messageLinkText applied here as, styles.colorMuted as this is used in other System messages and reinforces consistency in the app. Colormuted applies the style:

    App/src/styles/styles.js

    Lines 412 to 414 in 8dcad16

    colorMuted: {
    color: themeColors.textSupporting,
    },

  • The second style rendering taskReportName is white hence good as it Mirrors the task name

  • I will also propose the capitalization of the first word in the task messages completed, canceled and repopened

    App/src/languages/en.js

    Lines 1317 to 1328 in 8dcad16

    task: {
    task: 'Task',
    title: 'Title',
    description: 'Description',
    assignee: 'Assignee',
    completed: 'Completed',
    messages: {
    completed: 'completed task',
    canceled: 'canceled task',
    reopened: 'reopened task',
    error: 'You do not have the permission to do the requested action.',
    },

    as they are System messages (in accordance to this issue)

  • Also proposing to add a seperator (i.e. ':') between the message and the taskName the message points to.

Before ### Original Screenshot

original

Final Screenshot

Final Screenshot

blue

final

What alternative solutions did you explore? (Optional)

xx

@melvin-bot melvin-bot bot added the Overdue label Jul 24, 2023
@melvin-bot
Copy link

melvin-bot bot commented Jul 25, 2023

@mallenexpensify Eep! 4 days overdue now. Issues have feelings too...

@mallenexpensify mallenexpensify added the External Added to denote the issue can be worked on by a contributor label Jul 26, 2023
@melvin-bot melvin-bot bot changed the title System messages for tasks are wrong/inconsistent with other report patterns [$1000] System messages for tasks are wrong/inconsistent with other report patterns Jul 26, 2023
@melvin-bot
Copy link

melvin-bot bot commented Jul 26, 2023

Job added to Upwork: https://www.upwork.com/jobs/~017ea86167d179c7a2

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Jul 26, 2023
@melvin-bot
Copy link

melvin-bot bot commented Jul 26, 2023

Current assignee @mallenexpensify is eligible for the External assigner, not assigning anyone new.

@melvin-bot
Copy link

melvin-bot bot commented Jul 26, 2023

Triggered auto assignment to Contributor-plus team member for initial proposal review - @ArekChr (External)

@mallenexpensify
Copy link
Contributor

Was able to reproduce, reckon it's a quick fix if we just want the text to be grey instead of blue (I didn't see a hyperlink).
Hi @ArekChr , first time seeing you as C+ on an issue for me. Can you please review the proposals above?

@melvin-bot melvin-bot bot removed the Overdue label Jul 26, 2023
@JmillsExpensify JmillsExpensify self-assigned this Jul 26, 2023
@JmillsExpensify
Copy link

Going to assign myself to this issue as well to ensure we land on the appropriate design patterns.

@ArekChr
Copy link
Contributor

ArekChr commented Jul 27, 2023

Agree, this issue is pretty straightforward, The first proposal LGTM.
🎀 👀 🎀 C+ reviewed

@melvin-bot
Copy link

melvin-bot bot commented Jul 27, 2023

Triggered auto assignment to @dangrous, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

@DanutGavrus
Copy link
Contributor

@ArekChr @dangrous I'm OOO tomorrow & up in the mountains this weekend ⛰️, don't know if it's possible to postpone the assignment. In any case, I'll create the PR as soon as possible on Monday, thank you! 😁

@dangrous
Copy link
Contributor

Hi! the proposal seems fine to me - however I'm checking with the folks who worked on tasks to see if the original idea was to have this link to something - in which case the bug wouldn't be the text styling but instead a missing link.

Stay tuned (this will probably give you the reprieve you need, @DanutGavrus - and either way it's 3 business days so you should probably be fine to raise it on Mon.)

@thienlnam
Copy link
Contributor

Yeah this is a remnant of an old thing of tasks where we used to add the system message to the parent report. The link would take you to the task report but now since the system messages are in the task report it doesn't really make sense to keep them links anymore

@dangrous
Copy link
Contributor

Okay great! Then we can move forward with @DanutGavrus's proposal. I'll assign you now, and that will give you through Tuesday to get that bonus, which should be fine!

@melvin-bot melvin-bot bot removed the Help Wanted Apply this label when an issue is open to proposals by contributors label Jul 28, 2023
@melvin-bot
Copy link

melvin-bot bot commented Jul 28, 2023

📣 @DanutGavrus You have been assigned to this job!
Please apply to the Upwork job and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Once you apply to this job, your Upwork ID will be stored and you will be automatically hired for future jobs!
Keep in mind: Code of Conduct | Contributing 📖

@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Aug 3, 2023
@melvin-bot
Copy link

melvin-bot bot commented Aug 3, 2023

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

@melvin-bot
Copy link

melvin-bot bot commented Aug 3, 2023

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.49-3 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-08-10. 🎊

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

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

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

@melvin-bot
Copy link

melvin-bot bot commented Aug 3, 2023

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

  • [@ArekChr] The PR that introduced the bug has been identified. Link to the PR:
  • [@ArekChr] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
  • [@ArekChr] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
  • [@ArekChr] Determine if we should create a regression test for this bug.
  • [@ArekChr] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
  • [@JmillsExpensify / @mallenexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

@thienlnam
Copy link
Contributor

thienlnam commented Aug 3, 2023

I've been seeing this live - and for group / room chats, the double colon doesn't look that good. I'm wondering if we should remove the colon so it just says

test31@gmail.com: Created a task task title

Screenshot 2023-08-03 at 11 03 32 AM

Thoughts on this? Maybe it's not a big deal for these specific situations but wanted to point it out

@shawnborton
Copy link
Contributor

Oh that would make sense to me, thoughts @JmillsExpensify ?

@dangrous
Copy link
Contributor

dangrous commented Aug 3, 2023

I agree that it looks weird - but that's a different issue, right? this just changed the color, not the colon or anything

@shawnborton
Copy link
Contributor

Fair, that can be fixed as a follow up.

@thienlnam
Copy link
Contributor

Oh gotcha, yeah I guess this would be a seperate issue

@ArekChr
Copy link
Contributor

ArekChr commented Aug 4, 2023

  • The PR that introduced the bug has been identified. Link to the PR: has not been identified.
  • The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: N/A
  • A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A
  • Determine if we should create a regression test for this bug: No regression test is needed for testing colors of text.

@dangrous
Copy link
Contributor

dangrous commented Aug 4, 2023

Checklist looks good, this wasn't a regression.

@thienlnam are you able to make an issue for the colon thing? I can spin up a PR quick since it'll be a five second fix.

@thienlnam
Copy link
Contributor

Nope not yet, though maybe it's fine because removing the colon makes it more confusing for non-group chats so I'm not really sure which we want to do

@dangrous
Copy link
Contributor

dangrous commented Aug 7, 2023

Hrm, maybe we sync in Slack?

@dangrous
Copy link
Contributor

dangrous commented Aug 9, 2023

Posted in Slack about that question, but either way won't affect the payment for this issue.

https://expensify.slack.com/archives/C01GTK53T8Q/p1691602405412179

@melvin-bot melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels Aug 9, 2023
@dangrous
Copy link
Contributor

Got sidetracked a bit with that discussion about the follow up issue, but it looks like we're ready for payment on this one @mallenexpensify

@melvin-bot melvin-bot bot added the Overdue label Aug 14, 2023
@JmillsExpensify
Copy link

I like removing the double colon.

@melvin-bot melvin-bot bot removed the Overdue label Aug 16, 2023
@JmillsExpensify
Copy link

JmillsExpensify commented Aug 16, 2023

Summarizing payouts:

  • Issue reporter: N/A
  • Contributor: @DanutGavrus $1,500 paid (incl. urgency bonus)
  • Contributor+: @ArekChr $1,500 (does not require payment)

Upwork job is here: https://www.upwork.com/jobs/~017ea86167d179c7a2. @DanutGavrus can you please apply?

@DanutGavrus
Copy link
Contributor

@JmillsExpensify It requires 16 connects, could you please send me an invitation? This is my Upwork profile. Thank you!

@JmillsExpensify
Copy link

Sure thing! I just sent you an offer.

@DanutGavrus
Copy link
Contributor

Applied, thank you very much!

@melvin-bot melvin-bot bot added the Overdue label Aug 21, 2023
@melvin-bot
Copy link

melvin-bot bot commented Aug 21, 2023

@JmillsExpensify, @dangrous, @mallenexpensify, @ArekChr, @DanutGavrus Whoops! This issue is 2 days overdue. Let's get this updated quick!

1 similar comment
@melvin-bot
Copy link

melvin-bot bot commented Aug 21, 2023

@JmillsExpensify, @dangrous, @mallenexpensify, @ArekChr, @DanutGavrus Whoops! This issue is 2 days overdue. Let's get this updated quick!

@mallenexpensify
Copy link
Contributor

@DanutGavrus has been paid $1500 via Upwork, updated the post above to state.

  • Contributor: @DanutGavrus $1,500 paid (incl. urgency bonus)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 External Added to denote the issue can be worked on by a contributor
Projects
None yet
Development

No branches or pull requests

9 participants