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

Public Cloud - Email Scenario #2 #2570

Open
4 tasks done
Iryna-Kaplun opened this issue Apr 25, 2024 · 2 comments
Open
4 tasks done

Public Cloud - Email Scenario #2 #2570

Iryna-Kaplun opened this issue Apr 25, 2024 · 2 comments
Assignees

Comments

@Iryna-Kaplun
Copy link
Collaborator

Iryna-Kaplun commented Apr 25, 2024

Public Cloud

  • Scenario 2, edit request is sending a provisioned email, this should not be the case. Only send the edit summary email
  • Ask public cloud if there is a callback for an edit. Explore possibility of sending an email before the edit is provisioned and sends the edit summary email. Update docs if we do implement this change
  • Scenario 3, change subject of rejection email to say something like "Request has been rejected for [product name]"
  • Scenario 3, for reject delete email, add product details section
@Iryna-Kaplun Iryna-Kaplun changed the title Public Cloud - Email Scenarios Public Cloud - Email Scenario #2 Apr 25, 2024
@Amritpal-Nijjar
Copy link
Collaborator

Asked Public Cloud if there is a callback when an edit request is received, and confirmed that there is not one. There is only a callback when the provisioner completes the request.

@funtigr
Copy link
Collaborator

funtigr commented May 14, 2024

  1. Summary only instead of two emails - implemented,
  2. Change Rejected email name:
    @Amritpal-Nijjar
    The phrase in the header is in single quotes for both Create Rejected and Delete Rejected emails:

image.png

3. The section with product data is added to Delete Rejected email.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants