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

Add 'Status' to GET /properties/{id}/certificates/ model #9126

Closed
MatthewGoddard opened this issue May 23, 2023 · 4 comments
Closed

Add 'Status' to GET /properties/{id}/certificates/ model #9126

MatthewGoddard opened this issue May 23, 2023 · 4 comments

Comments

@MatthewGoddard
Copy link

MatthewGoddard commented May 23, 2023

A 'Status' field has been added to the Cert table to support new functionality in AC.

Please can this be exposed in the GET /properties/{id}/certificates/ model.

image

This will likely also need a corresponding /configuration/certificateTypes endpoint, as it is a configurable field... :)

Specification

  • Project: Reapit.Services.Properties

  • Add new statusId column to PropertyCertificateModel that exposes the value stored in cert.status

  • If cert.status is null/empty, model property should be null. Statuses do not apply to all certificate types

  • This should be read only for now as the write side is complex

  • Project: Reapit.Services.Configuration

  • Alter model returned from certificateTypes endpoint to include a new statuses collection of ConfigurationItemModel which contains an id and value property (use existing model) and exposes the unpacked configuration option value configsetting.uCertFollowUpStatuses - be sure to understand how to parse this field before proceeding. Output should look like this:

{
    "id": "AI",
    "value": "Appliance Insurance", 
    "statuses": [
      { 
         "id": "NV",
         "value": "Not Valid"
      },
      { 
         "id": "US",
         "value": "Unsatisfactory"
      }
    ]
}
@github-actions
Copy link
Contributor

Thank you for raising a feature request. Feature requests will be prioritised in accordance with our roadmap, customer and developer priorities.
This request will be reviewed in our weekly refinement sessions and assigned to a specific project board or column, depending on the nature of the request and the development work required.
For more information on our processes, please click here

@AshDeeming AshDeeming added feature-request User requested feature back-end Relates to back end issues and removed needs-triage labels May 23, 2023
@AshDeeming AshDeeming added this to To review in Platform Backlog via automation May 23, 2023
@plittlewood-rpt plittlewood-rpt added the 5 5 story points label May 25, 2023
@plittlewood-rpt plittlewood-rpt removed this from To review in Platform Backlog May 25, 2023
@plittlewood-rpt plittlewood-rpt added this to To do in Platform sprint 95 via automation May 25, 2023
@RWilcox-Reapit RWilcox-Reapit moved this from To do to In progress in Platform sprint 95 May 30, 2023
@RWilcox-Reapit RWilcox-Reapit self-assigned this May 30, 2023
@plittlewood-rpt
Copy link
Contributor

Internal ticket SI-21439 opened for applying db field to all datasets to make introduction of this feature easier to handle

@RWilcox-Reapit RWilcox-Reapit moved this from In progress to In review in Platform sprint 95 May 30, 2023
@HollyJoyPhillips HollyJoyPhillips added this to To do in Platform sprint 96 via automation Jun 9, 2023
@HollyJoyPhillips HollyJoyPhillips moved this from To do to Blocked in Platform sprint 96 Jun 9, 2023
@HollyJoyPhillips HollyJoyPhillips added this to To do in Platform sprint 97 via automation Jun 23, 2023
@HollyJoyPhillips HollyJoyPhillips moved this from To do to Blocked in Platform sprint 97 Jun 23, 2023
@HollyJoyPhillips HollyJoyPhillips added this to To do in Platform sprint 98 via automation Jul 7, 2023
@HollyJoyPhillips HollyJoyPhillips moved this from To do to Blocked in Platform sprint 98 Jul 7, 2023
@plittlewood-rpt plittlewood-rpt added this to To do in Platform sprint 99 via automation Jul 21, 2023
@plittlewood-rpt plittlewood-rpt moved this from To do to Blocked in Platform sprint 99 Jul 21, 2023
@HollyJoyPhillips HollyJoyPhillips added this to To review in Platform Backlog via automation Aug 4, 2023
@HollyJoyPhillips HollyJoyPhillips moved this from To review to Not ready in Platform Backlog Aug 4, 2023
@plittlewood-rpt
Copy link
Contributor

Field now present in all databases, so we can get this picked up and ready to merge

@plittlewood-rpt plittlewood-rpt moved this from Not ready to To review in Platform Backlog Sep 12, 2023
@plittlewood-rpt plittlewood-rpt moved this from To review to Near term in Platform Backlog Sep 14, 2023
@github-actions
Copy link
Contributor

This issue has been updated and moved to our ‘Near Term’ column (typically completed within 0 - 4 months). We have assessed the effort required and outlined a technical specification - please take the time to review this detail. When we're ready to schedule the issue, it will be assigned to the relevant board where you can continue to track its progress to completion.
For more information on our processes, please click here

@HollyJoyPhillips HollyJoyPhillips removed this from Near term in Platform Backlog Oct 13, 2023
@HollyJoyPhillips HollyJoyPhillips added this to To do in Platform sprint 105 via automation Oct 13, 2023
@RWilcox-Reapit RWilcox-Reapit moved this from To do to In progress in Platform sprint 105 Oct 16, 2023
@RWilcox-Reapit RWilcox-Reapit moved this from In progress to In review in Platform sprint 105 Oct 16, 2023
@RWilcox-Reapit RWilcox-Reapit moved this from In review to QA in Platform sprint 105 Oct 19, 2023
@RWilcox-Reapit RWilcox-Reapit moved this from QA to Done in Platform sprint 105 Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5 5 story points back-end Relates to back end issues external-request External request feature-request User requested feature
Projects
No open projects
Development

No branches or pull requests

4 participants