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

Expose AddedBy in Documents #11148

Closed
abrahamseni opened this issue May 16, 2024 · 1 comment
Closed

Expose AddedBy in Documents #11148

abrahamseni opened this issue May 16, 2024 · 1 comment
Assignees
Labels
3 3 story points back-end Relates to back end issues external-request External request feature-request User requested feature

Comments

@abrahamseni
Copy link

abrahamseni commented May 16, 2024

The documents/ endpoint doesn't show addedBy property as in AC.

Please expose the property as our user needs it for auditing purposes (GET, POST, PATCH)

API response:
Screenshot 2024-05-16 032822

Added property we need:
Screenshot 2024-05-16 032839

Thanks.

Specification

  • Project: Reapit.Services.Documents
  • Update the service to allow the reading and writing of theAddedBy field shown above. This is stored in extras: 'fileman.extras.gfAddedBy'
  • Pull the name from the platform identity identity.User.Name, possibly fallback to AppName for clientCredential flows. (Speak with Saab)
  • Do not allow this to be changed via PATCH (Not possible in AC)
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 refinement To be included in a future refinement session and removed needs-triage labels May 16, 2024
@AshDeeming AshDeeming added this to To review in Platform Backlog via automation May 16, 2024
@RWilcox-Reapit RWilcox-Reapit removed this from To review in Platform Backlog May 16, 2024
@RWilcox-Reapit RWilcox-Reapit added this to To do in Platform sprint 120 via automation May 16, 2024
@HollyJoyPhillips HollyJoyPhillips added 3 3 story points and removed refinement To be included in a future refinement session labels May 17, 2024
@RWilcox-Reapit RWilcox-Reapit self-assigned this May 21, 2024
@RWilcox-Reapit RWilcox-Reapit moved this from To do to In progress in Platform sprint 120 May 21, 2024
@RWilcox-Reapit RWilcox-Reapit moved this from In progress to In review in Platform sprint 120 May 23, 2024
@RWilcox-Reapit RWilcox-Reapit moved this from In review to QA in Platform sprint 120 May 24, 2024
@RWilcox-Reapit RWilcox-Reapit moved this from QA to Done in Platform sprint 120 May 24, 2024
@RWilcox-Reapit RWilcox-Reapit moved this from Done to QA in Platform sprint 120 May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 3 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