Skip to content

Request cancellation - the email goes to the partner. Should probably also go to the user who sent the request. #5564

@ruestitch

Description

@ruestitch

Summary

When cancelling a request, send the email to the user who sent the request as well as the partner

Why?

That's likely who really needs to know. Sometimes the official email is at a higher level than who is really working with the banks, or may be an employee who is no longer with the agency.

Details

Recreating

Step 1 - add another user to Pawnee Parent Service

-- sign in as verified@example.com
-- Click "verified@example.com" in the top right corner, then "My Coworkers"
-- Click "Invite new user"
-- add your favourite name and bogus email
-- Create User
The email inviting for that user will soon appear in your browser.
-- Logout before clicking the "Accept Invitation" button
-- Accept Invitation
-- set a password -- password! will do

Step 2 Create some requests

Now make a request. Heck -- make two or three, so you have some available for testing when you make the fix!

Click "create request", fill in some items and quantities, and click save, and confirm. You will see Request Confirmation emails regarding these appear in a few minutes.

Step 3 Cancel one of those requests

  • Logout, then log in as org_Admin1@example.com
  • Click Requests
  • Find an email with the request sender that matches the user you created above
  • click cancel
  • enter a cancelation reason, and click "Yes, Cancel Request" (we have a separate issue to improve this screen)
    You should see a message that the request has been removed

In a few moments, you should see an email in your browser about the cancelation. Note who it was sent to.

What we want

That email should go both to the partner (which it does) and the Request sender (which it does not)

Criteria for completion

  • behaviour as described above
  • tests to support that behaviour
  • This might need a small change to the user documentation. Please mention that in your PR.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Good First IssueSuitable for users that are newer or less experienced

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions