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
Description of problem:
There is a field approver in the Automate Configuration/Email/Default. I would expect that when this is set, it will be used for sending emails to the approver, but it seems the default_recipient is always used.
Version-Release number of selected component (if applicable):
5.11.6
How reproducible:
1/1
Steps to Reproduce:
Copy the Configuration/Email/Defaulut to new domain
configure approver
set SMTP on the CFME config page
Create provisioning request that is not auto-approved
Actual results:
Approver email sent to default_recipient address
Expected results:
Approver email sent to approver.
Additional info:
Perhaps we don't need the approver address and the defaut_recipient is enough. Perhaps it is the other way -- we just need approver_email.
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.
Description of problem:
There is a field
approver
in the Automate Configuration/Email/Default. I would expect that when this is set, it will be used for sending emails to the approver, but it seems thedefault_recipient
is always used.Version-Release number of selected component (if applicable):
5.11.6
How reproducible:
1/1
Steps to Reproduce:
Actual results:
Approver email sent to default_recipient address
Expected results:
Approver email sent to
approver
.Additional info:
Perhaps we don't need the approver address and the defaut_recipient is enough. Perhaps it is the other way -- we just need
approver_email
.https://bugzilla.redhat.com/show_bug.cgi?id=1783511
The text was updated successfully, but these errors were encountered: