FE allow User to Filter Users through TenantUser queries endpoint

Description

PRDE - Story default text according to the team DoR (Definition of Ready)

01 - STAKEHOLDER (PERSON THAT CAN VALIDATE AND ANSWER QUESTIONS):
02 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):
03 - GOAL (DESCRIBE THE PROPOSED SOLUTION):

Provide an endpoint to allow FE to query tenantUsers.

04 - WHO CAN USE THIS FEATURE (USER ROLES):
05 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
06 - ACCEPTANCE CRITERIA:

  • Endpoint on FE side allowing to filter tenant user (/admin/query/sqlfilter).
  • Tenand ID should be provided within the query to be perfomed by (/admin/query/sqlfilter).
  • Abilities:
    • Open filter (using like) by name, email and phone number.
    • Filter by groups (using defined list of groups). It allows one or more.
    • Filter by status (using defined list of status). It allows one or more.
    • Filter by roles (using defined list of roles). It allows one or more.
    • All filters work as AND condition.

Activity

Automation for Jira 22 March 2024, 10:28 Jira Internal Users

This issue was automatically transitioned to WAITING DEPLOY, as its linked QA regression issue has just reached WAITING DEPLOY status (PR was just merged into master branch in Github).

Automation for Jira 21 March 2024, 16:05 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 21 March 2024, 16:05 Jira Internal Users

This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.

Automation for Jira 21 March 2024, 15:44 Jira Internal Users

This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by carlosafw,douglascoimbra.

Automation for Jira 21 March 2024, 15:44 Jira Internal Users

Github user douglascoimbra has just approved a PR (added as Shard Assignee in this Jira issue).

refactor: https://totvslabs.atlassian.net/browse/CAPL-5316#icft=CAPL-5316 fe allow user to filter users through tenant user queries endpoint

Douglas Coimbra Lopes 21 March 2024, 15:44 Jira Internal Users

FIXED

Automation for Jira 21 March 2024, 14:30 Jira Internal Users

@MARCOS STUMPF ,
@Douglas Coimbra Lopes , @Ingo Wagner , @Carlos Affonso Wagner , @Chámam Diomede Caires , @Douglas Coimbra Lopes

Flag was removed since you have just transitioned the issue status/column.

Douglas Coimbra Lopes 21 March 2024, 14:30 Jira Internal Users

@Ingo Wagner The users are still with Inactive status from OrgUser Users tab

Automation for Jira 20 March 2024, 18:27 Jira Internal Users

This issue was automatically transitioned to WAITING DEPLOY, as its PR was just merged into master branch in Github.

Automation for Jira 20 March 2024, 17:46 Jira Internal Users

@MARCOS STUMPF ,
@Douglas Coimbra Lopes , @Ingo Wagner , @Carlos Affonso Wagner , @Chámam Diomede Caires , @Douglas Coimbra Lopes

Flag was removed since you have just transitioned the issue status/column.

Douglas Coimbra Lopes 20 March 2024, 17:46 Jira Internal Users

@Ingo Wagner Os OrgAdmins estao sendo exibindos incorretamente como Inativos. Entretando, os mesmos podem acessar e serem registrados em qualque tenant, pois estao ativos.

Automation for Jira 20 March 2024, 14:36 Jira Internal Users

This issue was automatically transitioned to WAITING DEPLOY, as its PR was just merged into master branch in Github.

Automation for Jira 20 March 2024, 14:36 Jira Internal Users

This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.

feat: https://totvslabs.atlassian.net/browse/CAPL-5316#icft=CAPL-5316 new endpoints to get org users

Automation for Jira 19 March 2024, 13:38 Jira Internal Users

@MARCOS STUMPF ,
@Douglas Coimbra Lopes , @Ingo Wagner , @Carlos Affonso Wagner , @Douglas Coimbra Lopes

Flag was removed since you have just transitioned the issue status/column.

Douglas Coimbra Lopes 19 March 2024, 13:38 Jira Internal Users

@Ingo Wagner We are receiving console errors when we try to use the new filter on the UI

https://totvsalanharper.qarol.ai/carol-org/admin/users

Automation for Jira 16 March 2024, 21:51 Jira Internal Users

This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.

Automation for Jira 14 March 2024, 16:10 Jira Internal Users

This issue was automatically transitioned to WAITING DEPLOY, as its PR was just merged into master branch in Github.

Automation for Jira 14 March 2024, 14:06 Jira Internal Users

This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.

refactor: https://totvslabs.atlassian.net/browse/CAPL-5316#icft=CAPL-5316 fe allow user to filter users through tenant user queries endpoint

Automation for Jira 14 March 2024, 14:06 Jira Internal Users

This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.

feat: https://totvslabs.atlassian.net/browse/CAPL-5316#icft=CAPL-5316 fe allow user to filter users through tenant user queries endpoint

Automation for Jira 14 March 2024, 14:05 Jira Internal Users

This issue was automatically transitioned to WAITING DEPLOY, as its PR was just merged into master branch in Github.

Automation for Jira 1 March 2024, 19:01 Jira Internal Users

@MARCOS STUMPF ,
@Pedro Buzzi , @Ingo Wagner , @Carlos Affonso Wagner

This issue was planned to be delivered until 2024-03-25. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2024-03-01, 2024-03-25

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.

Automation for Jira 12 February 2024, 19:31 Jira Internal Users

@MARCOS STUMPF ,
@Gabriel DAmore Marciano ,
@Geny Isam Hamud Herrera ,
This issue was planned to be delivered until 2024-03-04. You can check that by consulting the issue in the Due Date field.

Dates already planned for this issue: 2024-03-04

If External Issue Link field is filled, customer was also informed on JIRA TOTVS.