Skip to content

Domain group- Unable to request money from the user which is part of domain group #7779

Closed

Description

@kbecciv

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. Go to https://staging.expensify.com/[](javascript:)
  2. Log in with expensifail account (admin account) - (applausetester+0707abb@applause.expensifail.com)
  3. Go to Groups - Create Groups
  4. Use any name for Permission group name
  5. Unable Preferred Policy tag
  6. Go to Group - Show members
  7. Add a couple members to this group
  8. Go to https://staging.new.expensify.com
  9. Log in with expensifail account (admin account) - (applausetester+0707abb@applause.expensifail.com)
  10. Click on Fub menu and click on Request Money
  11. Put amount and click continue
  12. Select on of the user from user from your domain group - (applausetester+0901abb@applause.expensifail.com)

Expected Result:

Able to request money from the user which is part of domain group

Actual Result:

Unable to request money from the user which is part of domain group

Error Message:

Chat you are looking can not be found

Workaround:

Unknown

Platform:

Where is this issue occurring?

  • Web
  • iOS
  • Android
  • Desktop App
  • Mobile Web

Version Number: 1.1.39.1

Reproducible in staging?: Yes

Reproducible in production?: Yes

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Recording.225.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause

Slack conversation:

View all open jobs on GitHub

Activity

  1. MelvinBot commented on Feb 16, 2022

    @MelvinBot
    Contributor

    Triggered auto assignment to @alex-mechler (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  2. alex-mechler commented on Feb 16, 2022

    @alex-mechler
    Contributor

    It looks like we are failing to find the IOU report, but I'm not seeing any errors in the logs. This may be internal

  3. alex-mechler commented on Feb 16, 2022

    @alex-mechler
    Contributor

    @kbecciv Can you get a screenshot of the network request for GetIOUReport when you attempt this? The logs arent being a ton of help here

  4. kbecciv commented on Feb 17, 2022

    @kbecciv
    Author

    @alex-mechler Sure, please attached. If you need credentials: applausetester+0707abb@applause.expensifail.com/Feya86Katya
    image (9)

  5. alex-mechler commented on Feb 17, 2022

    @alex-mechler
    Contributor

    Can confirm this has to be done externally, looks like something about how we are calculating if a user can send that IOU isnt working. Logs here. Dropping to pool

  6. removed their assignment
    on Feb 17, 2022
  7. MelvinBot commented on Feb 21, 2022

    @MelvinBot
    Contributor

    Whoops! This issue is 2 days overdue. Let's get this updated quick!

  8. MelvinBot commented on Feb 23, 2022

    @MelvinBot
    Contributor

    Huh... This is 4 days overdue. Who can take care of this?

  9. added
    InternalRequires API changes or must be handled by Expensify staff
    on Feb 23, 2022
  10. 29 remaining items

  11. kbecciv commented on Apr 1, 2022

    @kbecciv
    Author

    @Julesssss I just created account and I think I used the same configuration as above account. My result had different error this time. Account used: applausetester+033122abb@applause.expensifail.com/Feya86Katya

    Recording.153.mp4
  12. Julesssss commented on Apr 1, 2022

    @Julesssss
    Contributor

    Thanks. This time I'm able to login, and I'm able to make requests as expected 😕

    ReproductionAttempt2.mov
  13. mvtglobally commented on Apr 5, 2022

    @mvtglobally

    Issue not reproducible during KI retests. (First week)

  14. Julesssss commented on Apr 13, 2022

    @Julesssss
    Contributor

    Not overdue. It seems like this isn't occuring anymore, but lets await further retests.

  15. Julesssss commented on Apr 22, 2022

    @Julesssss
    Contributor

    Same as above, awaiting further retests.

  16. mvtglobally commented on Apr 26, 2022

    @mvtglobally

    Issue not reproducible during KI retests. (Second week)

  17. mvtglobally commented on May 3, 2022

    @mvtglobally

    Issue not reproducible during KI retests. (Third week) Closing

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

Metadata

Metadata

Assignees

Labels

EngineeringImprovementItem broken or needs improvement.InternalRequires API changes or must be handled by Expensify staffWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions