Project

General

Profile

Actions

roos-fs tasks #144

open

Create a report sending mechanism

Added by Vadim Pariev 10 months ago. Updated 5 days ago.

Status:
Closed
Priority:
Normal
Start date:
06/24/2025
Due date:
% Done:

0%

Estimated time:
14:00 h

Description

General
Since ROOS needs to provide proper information about the services to their customer in a timely manner the report needs to be sent automatically as soon as it is created. But there ar use cases where the some tasks in the Service could be reopened due to some additional works that needs to be doen or some ther reason, hence the new report needs to begenerated and sent out.

Expected result

  • Admin can predefine what contact in the CUSTOMER would be used for the report sending (report receiver)
  • Admin can predefine multiple contacts within the customer who would receive the report by checking the checkbox "Report receiver" - At least one contact has to be marked as a report receiver
  • The generated PDF is sent to the email that is stated n the customer contact that has a "Report receiver" check box checked 24 hours after the report was generated
  • If 24 hours have apssed the report is then sent
  • If the user reopened the service AFTER 24 hours, then no report would be sent, a new process starts as soon as the user has completed the service
  • If the service reopened after 24 hours, the new report would be generated as soon as the user comletes the reopened service
Actions #1

Updated by Vadim Pariev 10 months ago

  • Status changed from Backlog to Open
Actions #2

Updated by Alex Katasonov 10 months ago

  • Status changed from Open to In progress
Actions #3

Updated by Alex Katasonov 10 months ago

  • Estimated time set to 10:00 h
Actions #4

Updated by Alex Katasonov 10 months ago

  • Estimated time changed from 10:00 h to 14:00 h
Actions #5

Updated by Alex Katasonov 10 months ago

  • Status changed from In progress to Open
Actions #6

Updated by Alex Katasonov 10 months ago

  • Status changed from Open to In progress
Actions #7

Updated by Alex Katasonov 10 months ago

  • Status changed from In progress to Deployed (QA)
Actions #8

Updated by Alex Katasonov 10 months ago

  • Status changed from Deployed (QA) to In progress
Actions #9

Updated by Alex Katasonov 10 months ago

  • Status changed from In progress to Deployed (QA)
Actions #10

Updated by Alex Katasonov 10 months ago

  • Status changed from Deployed (QA) to In progress
Actions #11

Updated by Alex Katasonov 10 months ago

  • Status changed from In progress to Deployed (QA)
Actions #12

Updated by Vadim Pariev 10 months ago ยท Edited

Test result NOT OK

  • Admin can predefine what contact in the CUSTOMER would be used for the report sending (report receiver)
  • Admin can predefine multiple contacts within the customer who would receive the report by checking the checkbox "Report receiver" - At least one contact has to be marked as a report receiver

these points are not implimented

Actions #13

Updated by Vadim Pariev 10 months ago

  • Status changed from Deployed (QA) to Open
Actions #14

Updated by Alex Katasonov 10 months ago

  • Status changed from Open to Deployed (QA)
Actions #15

Updated by Alex Katasonov 10 months ago

Vadim Pariev wrote in #note-12:

Test result NOT OK

  • Admin can predefine what contact in the CUSTOMER would be used for the report sending (report receiver)
  • Admin can predefine multiple contacts within the customer who would receive the report by checking the checkbox "Report receiver" - At least one contact has to be marked as a report receiver

these points are not implimented

@Vadim Pariev deployed

Actions #17

Updated by Vadim Pariev 10 months ago

  • Status changed from Deployed (QA) to Closed
Actions #18

Updated by Albert Katasonov 5 days ago

  • Project changed from 8 to Roos-fs-ZIP
Actions

Also available in: Atom PDF