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

Utilize status field on inspection table to report Inspection Findings #1318

Open
UsamaEquinorAFK opened this issue Jan 8, 2024 · 2 comments
Labels
backend Backend related functionality database-change Will require migration frontend Frontend related functionality improvement Improvement to existing functionality question Further information is requested stale This issue or pull request already exists ux Issue needs input from UX designer

Comments

@UsamaEquinorAFK
Copy link
Contributor

UsamaEquinorAFK commented Jan 8, 2024

Describe the improvement you would like to see
Have a status on the inspection which tells us, is_completed or is_reported. Naturally everything that is completed should be reported once. Right now this is handled by running the service every day and going back 24 hours and fetching inspection findings but if the service goes down than we are at a risk of loss of inspection data.

Describe the solution you'd like
Run the service every day at a set time as it is designed right now but fetch all the inspections which have status is_completed but not is_reported.

Change status to is_repoerted after fetching them and compiling them into a inspection report.

How will this feature affect the current Threat Model?

NA. Feel free to add anything here,

@UsamaEquinorAFK UsamaEquinorAFK added the backend Backend related functionality label Jan 8, 2024
@UsamaEquinorAFK UsamaEquinorAFK changed the title Utilize Status field on inspection to report Inspection Findings Utilize status field on inspection table to report Inspection Findings Jan 8, 2024
@UsamaEquinorAFK UsamaEquinorAFK added question Further information is requested improvement Improvement to existing functionality database-change Will require migration labels Jan 8, 2024
@aeshub
Copy link
Contributor

aeshub commented May 4, 2024

This issue has automatically been marked as stale as there has been no activity for 60 days.

@aeshub aeshub added the stale This issue or pull request already exists label May 4, 2024
@andchiind andchiind added frontend Frontend related functionality ux Issue needs input from UX designer and removed stale This issue or pull request already exists labels Jul 25, 2024
@aeshub
Copy link
Contributor

aeshub commented Sep 24, 2024

This issue has automatically been marked as stale as there has been no activity for 60 days.

@aeshub aeshub added the stale This issue or pull request already exists label Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Backend related functionality database-change Will require migration frontend Frontend related functionality improvement Improvement to existing functionality question Further information is requested stale This issue or pull request already exists ux Issue needs input from UX designer
Projects
None yet
Development

No branches or pull requests

3 participants