Bug: Email linking to LM Master Comment Report (Folder report 73002) (SS) (Ready for UAT on TEST)

TracyLinder commented 7 months ago

Acceptance Criteria

When all the processes in Review Process Group in the LM folders are completed, system should send 2 emails
one to the reviewers, this is working, but it should also attach the LM Master Comment Report to the email (73002)
one to Applicant of People Record, this used to work before the A7 migration, it contained a link to AB+C Portal to generate Master Comment Report.

The system stopped auto emailing the customer a link to the LM Master Report (73002)

This stopped working shortly after A7 upgrade
This feature should be triggered when the last review process closed
Internal staff is getting an automated FYI email, per Deb. The report is not attached.

TracyLinder commented 7 months ago

We need to add enough info to this to make debugging possible.

vschandramouli commented 7 months ago

Questions:

Which process/series of actions in AMANDA triggers this email?
Is it possible to get an email template of when it was working?
Was the report attaching as PDF? Or was it a link?

vschandramouli commented 7 months ago

Notes from scoping meeting:

After the last process in Review Process group was completed, 2 emails need to be sent

1 to staff- this is working, but no Master comment report attached 1 to Applicant - This is no longer working, this needs to have a link to the AB+C Portal where they can get the Master Comment Report.

vschandramouli commented 7 months ago

Updated AC, moving to Backlog.

Nadin-Nader commented 6 months ago

@SubhaShroff this has been sent to the DevOps CM Team to be deployed to TEST under SCTASK0392989

SubhaShroff commented 6 months ago

@Nadin-Nader The TEST deployment is done. I tested it on RSN-13206697. I received an email with Master report attached. Ready for UAT. Thanks.

TracyLinder commented 5 months ago

Kathy will test.

TracyLinder commented 4 months ago

Testing is reassigned to Joseph F.

UhrigK commented 3 months ago

I am testing for just this Auto Email to verify if MCR is being sent out. EASEMENT RELEASES ARE THE ONLY ONES THAT ARE WORKING LA, ROW VACATIONS, AND EA ARE NOT WORKING

Easement Release MCR is working and attached to the email. (I will be putting in a few tickets next week because the other Auto Emails sent after a reviewer adds comments has a really messy link that takes them to another permit that is not mine from 2023 and shows their status of their application.) - ER testing found MCR is now ALSO added to the Attachments Tab as well automatically.
License Agreement MCR is NOT working - no Auto Email sent to the applicant at all. and (I will be putting in a few tickets next week because the other Auto Emails sent after a reviewer adds comments has a really messy link that takes them to another permit that is not mine from 2023 and shows their status of their application.)
ROW Vacations MCR is NOT working - no Auto Email sent to the applicant at all. and (I will be putting in a few tickets next week because the other Auto Emails sent after a reviewer adds comments has a really messy link that takes them to another permit that is not mine from 2023 and shows their status of their application.)

TracyLinder commented 3 months ago

@vschandramouli it looks like 2/3 of Kathy's test cases failed. Can you please check out her notes, update the AC as needed, put this back On Deck, and let Nate know?

SubhaShroff commented 3 months ago

@TracyLinder @vschandramouli I hope Kathy tested on TEST. I just verified these on TEST and MCR works for the following subtypes. As per the existing processes code, this only works for the following subtypes and not for License Agreement subtype. If that helps. 50681 Easement Release 50682 Encroachment 50684 R.O.W. Vacation

TracyLinder commented 2 months ago

I will reach out to Kathy.

Nadin-Nader commented 2 months ago

Sent message to Kathy, Elizabeth and Beth via the Teams chanel asking for UAT on TEST. Awaiting Response

UhrigK commented 2 months ago

I am looking at these now. My computer had to be replaced and it took over 2hrs.

From: Nadin Nader @.> Sent: Friday, June 21, 2024 1:32 PM To: cityofaustin/atd-data-tech @.> Cc: Uhrig, Kathy @.>; Comment @.> Subject: Re: [cityofaustin/atd-data-tech] Bug: Email linking to LM Master Comment Report (Folder report 73002) (SS) (Ready for UAT on TEST) (Issue #15155)

External Email - Exercise Caution

Sent message to Kathy, Elizabeth and Beth via the Teams chanel asking for UAT on TEST. Awaiting Response

- Reply to this email directly, view it on GitHubhttps://github.com/cityofaustin/atd-data-tech/issues/15155#issuecomment-2183260739, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BILOQ6YNE2U3YAIUBNBBALTZIRWRVAVCNFSM6AAAAABBNRFWCWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBTGI3DANZTHE. You are receiving this because you commented.Message ID: @.***>

CAUTION: This is an EXTERNAL email. Please use caution when clicking links or opening attachments. If you believe this to be a malicious or phishing email, please report it using the "Report Message" button in Outlook. For any additional questions or concerns, contact CSIRT at @.***".

UhrigK commented 2 months ago

test EA MCR sent.docx Encroachment Agreements are working

License Agreements are still not working. Easement releases was the only one working and i can test Row Vacations Monday and ER again to verify it's working still.

Is there anyway you all can verify that you have updated for all 4 of our processes before I retest the other 2? Easement Releases, Encroachment Agreements, License Agreements, and ROW Vacations?

TracyLinder commented 2 months ago

@SubhaShroff please apply this feature to all of LM regardless of subtypes.

Nadin-Nader commented 1 month ago

This has been sent to the DevOps CM Team to be deployed to DEV under SCTASK0436054

Nadin-Nader commented 1 month ago

A second commit has been sent to the DevOps CM Team to be deployed to DEV under SCTASK0436630 since the first one didn't work for Licence agreement as there was another IF condition stopping it in another procedure.

SubhaShroff commented 1 month ago

@Nadin-Nader SCTASK0437950 - is submitted for DEV deployment. Thank you.

Nadin-Nader commented 1 month ago

This has been sent to the DevOps CM Team to be deployed to TEST under SCTASK0438360

Nadin-Nader commented 1 month ago

This has been sent to the DevOps CM Team to be deployed to TEST under SCTASK0438360

SubhaShroff commented 1 month ago

@Nadin-Nader @TracyLinder After applying the logic to all LM subtypes, I tested this ticket on TEST again. It worked for the following LM subtypes and its good to UAT on TEST: RSN - 13174627 - License Agreement RSN - 13207039 - R.O.W. Vacation RSN - 13206697 - Easement Release RSN - 13212568 - Encroachment

Thank you.

UhrigK commented 4 weeks ago

RSN - 13174627 - License Agreement This one is now sending the MCR but the email is for easements. Please see the redlines and mark outs below of these changes.

FYI: We will send in new ticket for a few of the other emails that are directing applicant to reply to a link because that is not our process.

MCR - LA Auto Email updates.docx

UhrigK commented 4 weeks ago

RSN - 13206697 - Easement Release - the MCR email looks good.

FYI: We will send in new ticket for a few of the other emails that are directing applicant to reply to a link because that is not our process.

UhrigK commented 4 weeks ago

RSN - 13212568 - Encroachment This one is now sending the MCR but the email is for easements. Please see the redlines and mark outs below of these changes.

FYI: We will send in new ticket for a few of the other emails that are directing applicant to reply to a link because that is not our process.

MCR - Encroachment Auto Email updates.docx

UhrigK commented 4 weeks ago

RSN - 13207039 - R.O.W. Vacation This one is now sending the MCR but the email is for easements. Please see the redlines and mark outs below of these changes.

FYI: We will send in new ticket for a few of the other emails that are directing applicant to reply to a link because that is not our process.

MCR - ROW Vacations Auto Email updates.docx

SubhaShroff commented 3 weeks ago

Thank you for the feedback @UhrigK . @Nadin-Nader
The email id and email content should be changed only for License Agreement LM type. No changes for other subtypes email-ids and email content: R.O.W. Vacation, Easement Release ,Encroachment. Please confirm.

UhrigK commented 3 weeks ago

No, that is not correct; the only one not needing a change is Easement Releases. I have 4 comments entered with corrections please see those.

Hope you have a wonderful day!

Please always include @.**@.> for our record keeping and a quicker response time.

4-Week Deadline to Clear Rejection(s) after MCR

[Logo, company name Description automatically generated]http://austintexas.gov/tpw Kathy Uhrig (she/her/hers) Land Development Engineering │ Real Estate Services Agent Austin Transportation and Public Works Department Direct 512-978-1639 | Main 512-974-1150 | Media 512-974-8000 [Icon Description automatically generated]https://www.facebook.com/ATXMobility/ [Icon Description automatically generated] https://twitter.com/austinmobility [Icon Description automatically generated] http://eepurl.com/gaHbbr

From: SubhaShroff @.> Sent: Thursday, August 1, 2024 2:01 PM To: cityofaustin/atd-data-tech @.> Cc: Uhrig, Kathy @.>; Mention @.> Subject: Re: [cityofaustin/atd-data-tech] Bug: Email linking to LM Master Comment Report (Folder report 73002) (SS) (Ready for UAT on TEST) (Issue #15155)

External Email - Exercise Caution

Thank you for the feedback @UhrigKhttps://github.com/UhrigK . @Nadin-Naderhttps://github.com/Nadin-Nader The email id and email content should be changed only for License Agreement LM type. No changes for other subtypes email-ids and email content: R.O.W. Vacation, Easement Release ,Encroachment. Please confirm.

- Reply to this email directly, view it on GitHubhttps://github.com/cityofaustin/atd-data-tech/issues/15155#issuecomment-2263764371, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BILOQ64OG5MS6TMERRZJUT3ZPKAXRAVCNFSM6AAAAABBNRFWCWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRTG43DIMZXGE. You are receiving this because you were mentioned.Message ID: @.***>

CAUTION: This is an EXTERNAL email. Please use caution when clicking links or opening attachments. If you believe this to be a malicious or phishing email, please report it using the "Report Message" button in Outlook. For any additional questions or concerns, contact CSIRT at @.***".

TracyLinder commented 3 weeks ago

Let's discuss this at tomorrow's LDE prioritization meeting.

Nadin-Nader commented 2 weeks ago

This has been sent to the DevOps CM Team to be deployed in DEV under SCTASK0446684

Nadin-Nader commented 2 weeks ago

This has been deployed to DEV. Please UAT

SubhaShroff commented 1 week ago

@Nadin-Nader I tested the DEV deployment., I have to fix the full stops and format. I did couple of commits and Priya created a DEV deployment request for me - SCTASK0447491.

Nadin-Nader commented 1 week ago

This has been sent tot the DevOps CM Team to be deployed to TEST under SCTASK0447750

SubhaShroff commented 1 week ago

@Nadin-Nader This is good working in TEST. Ready for UAT. Thank you.

cityofaustin / atd-data-tech

Bug: Email linking to LM Master Comment Report (Folder report 73002) (SS) (Ready for UAT on TEST) #15155

The system stopped auto emailing the customer a link to the LM Master Report (73002)