-
Notifications
You must be signed in to change notification settings - Fork 32
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
sig#803: Add Technical User "Status" inside the technical user management page #944
Comments
Please make sure to validate against the backend swagger docu which values are possible and make sure that an translation is existing |
@lavanya-bmw i had a look please proceed as following: ACTIVE = green (confirmed) |
@jjeroch @MaximilianHauer Regarding documentation, need more information where to update the docs as https://portal.dev.demo.catena-x.net/documentation/?path=user%2F03.+User+Management%2F03.+Technical+User is currently empty |
Shared component changes is available in PR: eclipse-tractusx/portal-shared-components#249 |
@jjeroch @MaximilianHauer PR is approved from my side - please label PR with newly created tag "merge ready" if you consider this ready to merge |
@lavanya-bmw i would ask you to update the following page
|
PR link: eclipse-tractusx/portal-assets#377 |
approved |
Description:
The Technical User Management page (https://portal.int.demo.catena-x.net/technicaluser) requires an enhancement to display the status of each technical user in the form of a chipcard, similar to what we have for normal users. The status value for each technical user is available through a GET API endpoint. The task involves fetching the status from the backend and implementing the visual chipcard indicator within the technical user table.
Pre-implementation Checklist:
/api/administration/serviceaccount/owncompany/serviceaccounts
Implementation Details:
"status":
.portal-shared-component registry
to visually represent the status of each technical user.Documentation:
Acceptance Criteria:
The text was updated successfully, but these errors were encountered: