-
Notifications
You must be signed in to change notification settings - Fork 409
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
Show creator/editor in 'Edit properties' #9550
Show creator/editor in 'Edit properties' #9550
Comments
@tdipisa there's a point we need to clarify here, currently the owner does not exist in the model. The existing resources won't have one unfortunately. How to deal with it? |
@tdipisa @offtherailz backend PR available here |
@afabiani thank you so much. @offtherailz will review asap. |
@Igi-ID (FYI @offtherailz) |
FYI @tdipisa, Given two users A and B, when user A creates a resource and then user B edits the properties of that resource, user B is possibly not persisted in the editor column and consequently not shown in the "last modified by" field inside the modal. Internally this would be the resource.editor field pointing to the last user that changed the resource properties. in geostore\src\modules\rest\impl\src\main\java\it\geosolutions\geostore\services\rest\impl\RESTResourceServiceImpl.java we seem to be setting the current user of the update, so I am not sure where the issue is coming from (@afabiani). Is it possible to re-test this functionality given the scenario above? |
@afabiani we need some of your time to review the above. |
@offtherailz @Igi-ID according to my tests it shouldn't be a backend issue, however please test this patch here If this is still not working, most probably you are sending the |
Thanks to this from @afabiani, I suppose, right?
|
Indeed, most likely yes. |
Description
For Admin users only, it is requested to show who created a resource as well as the last editor inside the Edit properties panel.
Acceptance criteria
Other useful information
Expected activities:
The text was updated successfully, but these errors were encountered: