[jira] [Updated] (RANGER-4521) All records not displayed on Admin Audits UI when filtered using session ID

[Rakesh Gupta (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rakesh Gupta updated RANGER-4521:
-
Attachment: 0004-RANGER-4521.patch

> All records not displayed on Admin Audits UI when filtered using session ID
> ---
>
> Key: RANGER-4521
> URL: https://issues.apache.org/jira/browse/RANGER-4521
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: suja s
>Assignee: Rakesh Gupta
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 0004-RANGER-4521.patch
>
>
> STEPS TO REPRODUCE:
> Login as keyadmin user to Ranger Admin UI.
> Add a ranger kms policy by doing a json import.
> Navigate to Admin Audits on UI
> Click on the session ID corresponding to policy import and select "Show 
> Actions" so that audits related to specific sessionID are displayed
> CURRENT BEHAVIOUR:
> Some audit entries are missing when filtered using sessionID
> (Audots for import and export are shown, audit corresponding to policy create 
> is missing)
> EXPECTED BEHAVIOUR:
> All audits corresponding to filtered sessionID should be displayed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (RANGER-4521) All records not displayed on Admin Audits UI when filtered using session ID

[Rakesh Gupta (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rakesh Gupta updated RANGER-4521:
-
Attachment: (was: 0003-RANGER-4521.patch)

> All records not displayed on Admin Audits UI when filtered using session ID
> ---
>
> Key: RANGER-4521
> URL: https://issues.apache.org/jira/browse/RANGER-4521
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: suja s
>Assignee: Rakesh Gupta
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 0004-RANGER-4521.patch
>
>
> STEPS TO REPRODUCE:
> Login as keyadmin user to Ranger Admin UI.
> Add a ranger kms policy by doing a json import.
> Navigate to Admin Audits on UI
> Click on the session ID corresponding to policy import and select "Show 
> Actions" so that audits related to specific sessionID are displayed
> CURRENT BEHAVIOUR:
> Some audit entries are missing when filtered using sessionID
> (Audots for import and export are shown, audit corresponding to policy create 
> is missing)
> EXPECTED BEHAVIOUR:
> All audits corresponding to filtered sessionID should be displayed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Review Request 74753: RANGER-4521: All records not displayed on Admin Audits UI when filtered using session ID

[Rakesh Gupta]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74753/
---

(Updated Dec. 14, 2023, 7:26 a.m.)


Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay 
Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, sanket 
shelar, Sailaja Polavarapu, and Velmurugan Periasamy.


Bugs: RANGER-4521
https://issues.apache.org/jira/browse/RANGER-4521


Repository: ranger


Description
---

Some audit entries for keyadmin user are missing when filtered using sessionID 
or Audit Type = Ranger Policy. Also when moved to next page most audit entries 
are missing

(Audits for import and export are shown, audit corresponding to policy crud 
operation is missing for keyadmin user)


Diffs (updated)
-

  security-admin/src/main/java/org/apache/ranger/service/XTrxLogService.java 
9d9e0bbc0 


Diff: https://reviews.apache.org/r/74753/diff/4/

Changes: https://reviews.apache.org/r/74753/diff/3-4/


Testing
---

Tested All audits are displayed properly with filter and without filter for 
admin and keyadmin user.


Thanks,

Rakesh Gupta

Re: Review Request 74728: RANGER-4513: Policy listing page experiences an reset to Access tab when attempting to filter the service and zone dropdown options.

[Mugdha Varadkar]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74728/#review226049
---




security-admin/src/main/webapp/react-webapp/src/views/SideBar/TopNavBar.jsx
Line 218 (original), 218 (patched)


We have below solutions to handle this,

1) We can use hideSelectedOptions props of react-select to hide the 
selected option from the menu so that onChange is not triggered for the same 
value.

2) Update the logic in onChange to check if the selected value does match 
the currently selected value, then simply do nothing



security-admin/src/main/webapp/react-webapp/src/views/SideBar/TopNavBar.jsx
Line 232 (original), 240 (patched)


Please refer above review comments from above.


- Mugdha Varadkar


On Nov. 9, 2023, 9:46 a.m., Brijesh Bhalala wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74728/
> ---
> 
> (Updated Nov. 9, 2023, 9:46 a.m.)
> 
> 
> Review request for ranger, Dhaval Rajpara and Mugdha Varadkar.
> 
> 
> Bugs: RANGER-4513
> https://issues.apache.org/jira/browse/RANGER-4513
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> The policy listing page experiences an unexpected reset when attempting to 
> filter the service and zone dropdown options. 
> 
> Steps to Reproduce:
>  1)Navigate to the "hive" policy listing page.
>  2)Goto  Masking tab 
>  3)Select the "Service" dropdown to filter policies based on a specific 
> service.
>  4)Select the "Zone" dropdown to filter policies based on  specific zone.
>  5)Observe that the page resets to the default "Access" tab
> 
> Expected Behavior:
> 
> The page should retain the selected tab when filtering the service and zone 
> dropdown.
> 
> 
> Diffs
> -
> 
>   
> security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/PolicyListingTabView.jsx
>  44d9f1da9 
>   security-admin/src/main/webapp/react-webapp/src/views/SideBar/TopNavBar.jsx 
> d4dbc57d1 
> 
> 
> Diff: https://reviews.apache.org/r/74728/diff/1/
> 
> 
> Testing
> ---
> 
> Testing is in progress
> 
> 
> Thanks,
> 
> Brijesh Bhalala
> 
>

Re: Review Request 74791: RANGER-4606 /assets/assets/count API does not return the proper count if the number of services is greater than 200

[Ramachandran Krishnan]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74791/#review226048
---


Ship it!




Ship It!

- Ramachandran Krishnan


On Dec. 14, 2023, 4:24 a.m., Abhishek Patil wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74791/
> ---
> 
> (Updated Dec. 14, 2023, 4:24 a.m.)
> 
> 
> Review request for ranger, Mehul Parikh and Pradeep Agrawal.
> 
> 
> Bugs: RANGER-4606
> https://issues.apache.org/jira/browse/RANGER-4606
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> When the number of services in Ranger admin is greater than 200,
> the /public/api/policy/count policy returns the count as 200.
> The API should ideally return the actual number of services present in Ranger 
> admin
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/java/org/apache/ranger/rest/AssetREST.java 
> abc324dd1 
> 
> 
> Diff: https://reviews.apache.org/r/74791/diff/1/
> 
> 
> Testing
> ---
> 
> Applied the patch on a cluster and tested the following scenarios :-
> 1. Fetched the count using the API when the number of services is less than 
> 20, and then ensured that the proper count is returned (i.e count is returned 
> only for legacy services).
> 2. Created 250 Hdfs service repos, and fetched the count using the API, and 
> ensured that the proper count is returned.
> 
> 
> Thanks,
> 
> Abhishek Patil
> 
>

[jira] [Commented] (RANGER-4605) /assets/resources/count does not return proper count if policies are greater than 200

[Abhishek (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796544#comment-17796544
 ] 

Abhishek commented on RANGER-4605:
--

Review request available at :- [https://reviews.apache.org/r/74792/]
Thank you

> /assets/resources/count does not return proper count if policies are greater 
> than 200
> -
>
> Key: RANGER-4605
> URL: https://issues.apache.org/jira/browse/RANGER-4605
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Abhishek
>Assignee: Abhishek
>Priority: Major
>
> {color:#172b4d}The /assets/resources/count API should return the actual 
> number of policies (present in knox, hbase, hive and hdfs repos).{color}
> {color:#172b4d}However, if the number of policies is greater than 200, then 
> to fetch the actual number of policies, a parameter "?pageSize" has to be 
> added, and the response returned is based on the page size parameter.{color}
> {color:#172b4d}Ideally, the count returned should not depend on the pageSize 
> parameter.{color}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Review Request 74792: RANGER-4605: /assets/resources/count does not return proper count if policies are greater than 200

[Abhishek Patil]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74792/
---

Review request for ranger, Mehul Parikh and Pradeep Agrawal.


Bugs: RANGER-4605
https://issues.apache.org/jira/browse/RANGER-4605


Repository: ranger


Description
---

The /assets/resources/count API should return the actual number of policies 
(present in knox, hbase, hive and hdfs repos).
However, if the number of policies is greater than 200, then to fetch the 
actual number of policies, a parameter "?pageSize" has to be added, and the 
response returned is based on the page size parameter.
Ideally, the count returned should not depend on the pageSize parameter.


Diffs
-

  security-admin/src/main/java/org/apache/ranger/rest/AssetREST.java abc324dd1 


Diff: https://reviews.apache.org/r/74792/diff/1/


Testing
---

Applied the patch on a cluster and tested the following scenarios :-
1. Created 100 policies for hdfs, fetched the count using the API endpoint and 
ensured that the correct count is returned.
2. Created 2000 policies for hive, fetched the count using the API, and ensured 
that the proper count is returned.
3. Made a get request to the API endpoint using keyadmin user, and ensured that 
the count returned is 0 (0 is the expected value as keyadmin user can access 
only kms policies).


Thanks,

Abhishek Patil

[jira] [Created] (RANGER-4607) Ranger REST API improvements

[Pradeep Agrawal (Jira)]

Pradeep Agrawal created RANGER-4607:
---

 Summary: Ranger REST API improvements
 Key: RANGER-4607
 URL: https://issues.apache.org/jira/browse/RANGER-4607
 Project: Ranger
  Issue Type: Improvement
  Components: Ranger
Affects Versions: 3.0.0, 2.4.1
Reporter: Pradeep Agrawal
Assignee: Pradeep Agrawal






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (RANGER-4606) /assets/assets/count API does not return the proper count if the number of services is greater than 200

[Abhishek (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796537#comment-17796537
 ] 

Abhishek commented on RANGER-4606:
--

Review request available at :- [https://reviews.apache.org/r/74791/]
Thank you

> /assets/assets/count API does not return the proper count if the number of 
> services is greater than 200
> ---
>
> Key: RANGER-4606
> URL: https://issues.apache.org/jira/browse/RANGER-4606
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Abhishek
>Assignee: Abhishek
>Priority: Major
>
> {color:#172b4d}When the number of services in Ranger admin is greater than 
> 200,{color}
> {color:#172b4d}the /public/api/policy/count policy returns the count as 
> 200.{color}
> {color:#172b4d}The API should ideally return the actual number of services 
> present in Ranger admin{color}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Review Request 74791: RANGER-4606 /assets/assets/count API does not return the proper count if the number of services is greater than 200

[Abhishek Patil]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74791/
---

Review request for ranger, Mehul Parikh and Pradeep Agrawal.


Bugs: RANGER-4606
https://issues.apache.org/jira/browse/RANGER-4606


Repository: ranger


Description
---

When the number of services in Ranger admin is greater than 200,
the /public/api/policy/count policy returns the count as 200.
The API should ideally return the actual number of services present in Ranger 
admin


Diffs
-

  security-admin/src/main/java/org/apache/ranger/rest/AssetREST.java abc324dd1 


Diff: https://reviews.apache.org/r/74791/diff/1/


Testing
---

Applied the patch on a cluster and tested the following scenarios :-
1. Fetched the count using the API when the number of services is less than 20, 
and then ensured that the proper count is returned (i.e count is returned only 
for legacy services).
2. Created 250 Hdfs service repos, and fetched the count using the API, and 
ensured that the proper count is returned.


Thanks,

Abhishek Patil

Re: DRAFT][REPORT] Apache Ranger - Quarterly ending November 2023

[Selvamohan Neethiraj]

Thanks Madhan, Updated the board report with your suggestions below.

Selva-

On 12/13/23 5:39 PM, Madhan Neethiraj wrote:

+1

Selva,

Thank you compiling the report. I suggest adding following items as well:
   - new UI developed in react framework is made as the default
   - docker setup updates to support validation of earlier version plugins with 
later version of Ranger server
   - security-zone updates to support roles for admin and auditor privileges

Thanks,
Madhan


On 12/13/23, 7:29 AM, "Selvamohan Neethiraj" mailto:sneet...@apache.org>> wrote:


Rangers:


Here is the board report of Apache Ranger for the period, Quarter ending
Nov-2023.
Please review and provide your feedback.


Thanks,
Selva-


=


## Description:
Apache Ranger is a framework to enable, monitor and manage comprehensive
data
security - consistently across various data processing services.


## Issues:
There are no issues requiring board attention at this time


## Membership Data:
- Apache Ranger was founded 2017-01-17 (6 years ago).
- There are 32 committers and 17 PMC members in this project.
- The Committer-to-PMC ratio is roughly 8:5.


##Community changes, past quarter:
- No new PMC members. Last addition was Sailaja Polavarapu on 2019-09-18.
- Last addition to Committer was Dineshkumar Yadav on 2023-02-06.
- One PMC member has resigned (Colm O hEigeartaigh) on 2023-10-10.


## Project Activity:
- Review of security issues from Apache Security Team
- Working on ranger 3.0.0 version features and bugfixes (886 resolved
jira(s) - includes 448 bugfixes).
- Updated ranger website with new blogs and updated team member information.
- Will be working on moving the ranger doc content from SVN based to GIT
repo
- Will be planning to do the release of 3.0.0


## Community Health:
-1472 emails in dev@ranger.apache.org  in this 
quarter (+46% change from
past quarter)
- 7 emails in u...@ranger.apache.org  in this 
quarter (+ 0% change from
past quarter)
- 165 issues opened in JIRA in this quarter (+28% change from
past quarter)
- 121 issues closed in JIRA in this quarter (+45% change from
past quarter)
- 137 commits in this quarter (+53% change from
past quarter)
- 22 code contributors in this quarter (- 4% change from
past quarter)
- 8 PRs opened on GitHub in this quarter (-46% change from
past quarter)
- 5 PRs closed on GitHub in this quarter (-37% change from
past quarter)


## Most Recent releases:
- Apache Ranger 2.4.0 was released on 2023-03-30
- Apache Ranger 2.3.0 was released on 2022-07-06
- Apache Ranger 2.2.0 was released on 2021-11-01


=

Re: DRAFT][REPORT] Apache Ranger - Quarterly ending November 2023

[Madhan Neethiraj]

+1

Selva,

Thank you compiling the report. I suggest adding following items as well:
  - new UI developed in react framework is made as the default
  - docker setup updates to support validation of earlier version plugins with 
later version of Ranger server
  - security-zone updates to support roles for admin and auditor privileges

Thanks,
Madhan


On 12/13/23, 7:29 AM, "Selvamohan Neethiraj" mailto:sneet...@apache.org>> wrote:


Rangers:


Here is the board report of Apache Ranger for the period, Quarter ending 
Nov-2023.
Please review and provide your feedback.


Thanks,
Selva-


=


## Description:
Apache Ranger is a framework to enable, monitor and manage comprehensive 
data
security - consistently across various data processing services.


## Issues:
There are no issues requiring board attention at this time


## Membership Data:
- Apache Ranger was founded 2017-01-17 (6 years ago).
- There are 32 committers and 17 PMC members in this project.
- The Committer-to-PMC ratio is roughly 8:5.


##Community changes, past quarter:
- No new PMC members. Last addition was Sailaja Polavarapu on 2019-09-18.
- Last addition to Committer was Dineshkumar Yadav on 2023-02-06.
- One PMC member has resigned (Colm O hEigeartaigh) on 2023-10-10.


## Project Activity:
- Review of security issues from Apache Security Team
- Working on ranger 3.0.0 version features and bugfixes (886 resolved 
jira(s) - includes 448 bugfixes).
- Updated ranger website with new blogs and updated team member information.
- Will be working on moving the ranger doc content from SVN based to GIT 
repo
- Will be planning to do the release of 3.0.0


## Community Health:
-1472 emails in dev@ranger.apache.org  in this 
quarter (+46% change from 
past quarter)
- 7 emails in u...@ranger.apache.org  in this 
quarter (+ 0% change from 
past quarter)
- 165 issues opened in JIRA in this quarter (+28% change from 
past quarter)
- 121 issues closed in JIRA in this quarter (+45% change from 
past quarter)
- 137 commits in this quarter (+53% change from 
past quarter)
- 22 code contributors in this quarter (- 4% change from 
past quarter)
- 8 PRs opened on GitHub in this quarter (-46% change from 
past quarter)
- 5 PRs closed on GitHub in this quarter (-37% change from 
past quarter)


## Most Recent releases:
- Apache Ranger 2.4.0 was released on 2023-03-30
- Apache Ranger 2.3.0 was released on 2022-07-06
- Apache Ranger 2.2.0 was released on 2021-11-01


=

[jira] [Commented] (RANGER-4599) Prevent admin users from performing CRUD operations on KMS service repos

[Abhishek (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796430#comment-17796430
 ] 

Abhishek commented on RANGER-4599:
--

Review request available at :- [https://reviews.apache.org/r/74765/]
Thank you

> Prevent admin users from performing CRUD operations on KMS service repos
> 
>
> Key: RANGER-4599
> URL: https://issues.apache.org/jira/browse/RANGER-4599
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Abhishek
>Assignee: Abhishek
>Priority: Major
>
> Prevent admin users from performing CRUD operations on KMS service repos



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (RANGER-4600) Add improvement for /xaudit/access_audit API based on user role

[Abhishek (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796428#comment-17796428
 ] 

Abhishek commented on RANGER-4600:
--

Review request available at :- [https://reviews.apache.org/r/74782/]
Thank you

> Add improvement for /xaudit/access_audit API based on user role
> ---
>
> Key: RANGER-4600
> URL: https://issues.apache.org/jira/browse/RANGER-4600
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Abhishek
>Assignee: Abhishek
>Priority: Major
>
> Add improvement for /xaudit/access_audit API based on user role



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (RANGER-4601) /xaudit/access_audit/count API does not return the proper value

[Abhishek (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796426#comment-17796426
 ] 

Abhishek commented on RANGER-4601:
--

Review request available at :- [https://reviews.apache.org/r/74784/]
Thank you

> /xaudit/access_audit/count API does not return the proper value
> ---
>
> Key: RANGER-4601
> URL: https://issues.apache.org/jira/browse/RANGER-4601
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Abhishek
>Assignee: Abhishek
>Priority: Major
>
> /xaudit/access_audit/count API does not return the proper value



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (RANGER-4606) /assets/assets/count API does not return the proper count if the number of services is greater than 200

[Abhishek (Jira)]

Abhishek created RANGER-4606:


 Summary: /assets/assets/count API does not return the proper count 
if the number of services is greater than 200
 Key: RANGER-4606
 URL: https://issues.apache.org/jira/browse/RANGER-4606
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Reporter: Abhishek
Assignee: Abhishek


{color:#172b4d}When the number of services in Ranger admin is greater than 
200,{color}
{color:#172b4d}the /public/api/policy/count policy returns the count as 
200.{color}
{color:#172b4d}The API should ideally return the actual number of services 
present in Ranger admin{color}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (RANGER-4605) /assets/resources/count does not return proper count if policies are greater than 200

[Abhishek (Jira)]

Abhishek created RANGER-4605:


 Summary: /assets/resources/count does not return proper count if 
policies are greater than 200
 Key: RANGER-4605
 URL: https://issues.apache.org/jira/browse/RANGER-4605
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Reporter: Abhishek
Assignee: Abhishek


{color:#172b4d}The /assets/resources/count API should return the actual number 
of policies (present in knox, hbase, hive and hdfs repos).{color}
{color:#172b4d}However, if the number of policies is greater than 200, then to 
fetch the actual number of policies, a parameter "?pageSize" has to be added, 
and the response returned is based on the page size parameter.{color}
{color:#172b4d}Ideally, the count returned should not depend on the pageSize 
parameter.{color}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

DRAFT][REPORT] Apache Ranger - Quarterly ending November 2023

[Selvamohan Neethiraj]

Rangers:

Here is the board report of Apache Ranger for the period, Quarter ending 
Nov-2023.

Please review and provide your feedback.

Thanks,
Selva-

=

## Description:
Apache Ranger is a framework to enable, monitor and manage comprehensive 
data

security - consistently across various data processing services.

## Issues:
There are no issues requiring board attention at this time

## Membership Data:
- Apache Ranger was founded 2017-01-17 (6 years ago).
- There are 32 committers and 17 PMC members in this project.
- The Committer-to-PMC ratio is roughly 8:5.

##Community changes, past quarter:
- No new PMC members. Last addition was Sailaja Polavarapu on 2019-09-18.
- Last addition to Committer was Dineshkumar Yadav on 2023-02-06.
- One PMC member has resigned (Colm O hEigeartaigh) on 2023-10-10.

## Project Activity:
- Review of security issues from Apache Security Team
- Working on ranger 3.0.0 version features and bugfixes (886 resolved 
jira(s) - includes 448 bugfixes).

- Updated ranger website with new blogs and updated team member information.
- Will be working on moving the ranger doc content from SVN based to GIT 
repo

- Will be planning to do the release of 3.0.0

## Community Health:
-1472 emails in dev@ranger.apache.org in this quarter  (+46% change from 
past quarter)
-   7 emails in u...@ranger.apache.org in this quarter (+ 0% change from 
past quarter)
- 165 issues opened in JIRA in this quarter(+28% change from 
past quarter)
- 121 issues closed in JIRA in this quarter(+45% change from 
past quarter)
- 137 commits in this  quarter (+53% change from 
past quarter)
-  22 code contributors in this quarter(- 4% change from 
past quarter)
-   8 PRs opened on GitHub in this quarter (-46% change from 
past quarter)
-   5 PRs closed on GitHub in this quarter (-37% change from 
past quarter)


## Most Recent releases:
- Apache Ranger 2.4.0 was released on 2023-03-30
- Apache Ranger 2.3.0 was released on 2022-07-06
- Apache Ranger 2.2.0 was released on 2021-11-01

=

Re: Review Request 74747: RANGER-4532: Optimize policy listing loader after session timeout and Audit Admin session ID modal loader

[Brijesh Bhalala]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74747/
---

(Updated Dec. 13, 2023, 2:05 p.m.)


Review request for ranger, Dhaval Rajpara and Mugdha Varadkar.


Bugs: RANGER-4532
https://issues.apache.org/jira/browse/RANGER-4532


Repository: ranger


Description
---

Optimize policy listing loader after session timeout and Audit Admin session ID 
modal loader.

Current behaviour :-
1) After session timeout, if we navigate to policy listing page then "Something 
went wrong page is seen" for fraction of seconds.
2) In Audit admin session Id modal, the loader is not in sync.

Improvising the loader logic in both above the scenarios.


Diffs (updated)
-

  
security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AdminModal.jsx 
be7736241 
  
security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/PolicyListing.jsx
 253395806 
  
security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/PolicyListingTabView.jsx
 7c6b1c19b 
  security-admin/src/main/webapp/react-webapp/src/views/SideBar/TopNavBar.jsx 
860b1ab78 


Diff: https://reviews.apache.org/r/74747/diff/3/

Changes: https://reviews.apache.org/r/74747/diff/2-3/


Testing
---

Testing is in progress


Thanks,

Brijesh Bhalala

[jira] [Updated] (RANGER-4532) Optimize policy listing loader after session timeout and Audit Admin session ID modal loader

[Brijesh Bhalala (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brijesh Bhalala updated RANGER-4532:

Attachment: 0003-RANGER-4532.patch

> Optimize policy listing  loader after session timeout  and  Audit Admin 
> session ID modal loader
> ---
>
> Key: RANGER-4532
> URL: https://issues.apache.org/jira/browse/RANGER-4532
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Brijesh Bhalala
>Assignee: Brijesh Bhalala
>Priority: Major
>  Labels: ranger-react
> Fix For: 3.0.0
>
> Attachments: 0001-RANGER-4532.patch, 0002-RANGER-4532.patch, 
> 0003-RANGER-4532.patch
>
>
> Optimize policy listing  loader after session timeout and Audit Admin session 
> ID modal loader.
> Current behaviour  :-
> 1) After session timeout, if we navigate to policy listing page then 
> "Something went wrong page is seen" for fraction of seconds.
> 2) In Audit admin session Id modal, the loader is not in sync.
> Improvising the loader logic in both above the scenarios. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Review Request 74775: RANGER-4502 : Getting Error to load backbone.js latest UI.

[Brijesh Bhalala]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74775/#review226047
---


Ship it!




Ship It!

- Brijesh Bhalala


On Dec. 5, 2023, 7:14 a.m., Dhaval Rajpara wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74775/
> ---
> 
> (Updated Dec. 5, 2023, 7:14 a.m.)
> 
> 
> Review request for ranger, Brijesh Bhalala, Dhaval Shah, Dineshkumar Yadav, 
> Kishor Gollapalliwar, Madhan Neethiraj, Mehul Parikh, Mugdha Varadkar, 
> Pradeep Agrawal, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4502
> https://issues.apache.org/jira/browse/RANGER-4502
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Step to reproduce:
> 
> 1) Login to ranger admin UI
> 2) go to the profile drop-down
> 3) Click on Switch to latest UI
> 
> Result in "NO services found" page displayed. But we have services present in 
> Backbone Classic UI.
> 
> 
> Diffs
> -
> 
>   
> security-admin/src/main/webapp/scripts/views/policymanager/ServiceLayoutSidebar.js
>  965c52c37 
> 
> 
> Diff: https://reviews.apache.org/r/74775/diff/1/
> 
> 
> Testing
> ---
> 
> Testing is in progress
> 
> 
> Thanks,
> 
> Dhaval Rajpara
> 
>

[jira] [Updated] (RANGER-4521) All records not displayed on Admin Audits UI when filtered using session ID

[Rakesh Gupta (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rakesh Gupta updated RANGER-4521:
-
Attachment: 0003-RANGER-4521.patch

> All records not displayed on Admin Audits UI when filtered using session ID
> ---
>
> Key: RANGER-4521
> URL: https://issues.apache.org/jira/browse/RANGER-4521
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: suja s
>Assignee: Rakesh Gupta
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 0003-RANGER-4521.patch
>
>
> STEPS TO REPRODUCE:
> Login as keyadmin user to Ranger Admin UI.
> Add a ranger kms policy by doing a json import.
> Navigate to Admin Audits on UI
> Click on the session ID corresponding to policy import and select "Show 
> Actions" so that audits related to specific sessionID are displayed
> CURRENT BEHAVIOUR:
> Some audit entries are missing when filtered using sessionID
> (Audots for import and export are shown, audit corresponding to policy create 
> is missing)
> EXPECTED BEHAVIOUR:
> All audits corresponding to filtered sessionID should be displayed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (RANGER-4521) All records not displayed on Admin Audits UI when filtered using session ID

[Rakesh Gupta (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rakesh Gupta updated RANGER-4521:
-
Attachment: (was: 0002-RANGER-4521.patch)

> All records not displayed on Admin Audits UI when filtered using session ID
> ---
>
> Key: RANGER-4521
> URL: https://issues.apache.org/jira/browse/RANGER-4521
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: suja s
>Assignee: Rakesh Gupta
>Priority: Major
> Fix For: 3.0.0
>
>
> STEPS TO REPRODUCE:
> Login as keyadmin user to Ranger Admin UI.
> Add a ranger kms policy by doing a json import.
> Navigate to Admin Audits on UI
> Click on the session ID corresponding to policy import and select "Show 
> Actions" so that audits related to specific sessionID are displayed
> CURRENT BEHAVIOUR:
> Some audit entries are missing when filtered using sessionID
> (Audots for import and export are shown, audit corresponding to policy create 
> is missing)
> EXPECTED BEHAVIOUR:
> All audits corresponding to filtered sessionID should be displayed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Review Request 74753: RANGER-4521: All records not displayed on Admin Audits UI when filtered using session ID

[Rakesh Gupta]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74753/
---

(Updated Dec. 13, 2023, 12:57 p.m.)


Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay 
Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, sanket 
shelar, Sailaja Polavarapu, and Velmurugan Periasamy.


Changes
---

Fetching keyadmin audit entries by query.


Bugs: RANGER-4521
https://issues.apache.org/jira/browse/RANGER-4521


Repository: ranger


Description
---

Some audit entries for keyadmin user are missing when filtered using sessionID 
or Audit Type = Ranger Policy. Also when moved to next page most audit entries 
are missing

(Audits for import and export are shown, audit corresponding to policy crud 
operation is missing for keyadmin user)


Diffs (updated)
-

  security-admin/src/main/java/org/apache/ranger/service/XTrxLogService.java 
9d9e0bbc0 


Diff: https://reviews.apache.org/r/74753/diff/3/

Changes: https://reviews.apache.org/r/74753/diff/2-3/


Testing
---

Tested All audits are displayed properly with filter and without filter for 
admin and keyadmin user.


Thanks,

Rakesh Gupta

Review Request 74790: RANGER-4604: Need to add query param createdBy for security-zone GET API

[Prashant Satam]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74790/
---

Review request for ranger, Anand Nadar, Ankita Sinha, Madhan Neethiraj, Monika 
Kachhadiya, Subhrat Chaudhary, and Vanita Ubale.


Bugs: RANGER-4604
https://issues.apache.org/jira/browse/RANGER-4604


Repository: ranger


Description
---

We need to add a query param createdBy for security-zone GET API. It will be 
useful to filter list of security-zones created by user, especially to get the 
security-zone created by self


Diffs
-

  
agents-common/src/main/java/org/apache/ranger/plugin/store/SecurityZonePredicateUtil.java
 54b477502 
  agents-common/src/main/java/org/apache/ranger/plugin/util/SearchFilter.java 
719ec3005 
  security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java 
87a278674 


Diff: https://reviews.apache.org/r/74790/diff/1/


Testing
---

Steps to test
1)create a Security-zone by Test-user-1
2)GET security-zones using GET API /service/zones/zones by using query param 
createdBy
3)Request > (/service/zones/zones?createdBy=Test-user-1) in Response you 
will get zones which are created by Test-user-1


Thanks,

Prashant Satam

Review Request 74788: RANGER:4603 : Need to add query param createdBy for dataset GET API

[Prashant Satam]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74788/
---

Review request for ranger, Anand Nadar, Ankita Sinha, Madhan Neethiraj, Monika 
Kachhadiya, Subhrat Chaudhary, and Vanita Ubale.


Bugs: RANGER-4603
https://issues.apache.org/jira/browse/RANGER-4603


Repository: ranger


Description
---

Currently we have dataset GET APIs to get list datasets based on ACL. It will 
be useful to be able filter the list based on users who created the dataset, 
especially to get the datasets created by self.


Diffs
-

  agents-common/src/main/java/org/apache/ranger/plugin/util/SearchFilter.java 
719ec3005 
  security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java af70daa9d 
  
security-admin/src/main/java/org/apache/ranger/service/RangerGdsDatasetService.java
 e8d672015 


Diff: https://reviews.apache.org/r/74788/diff/1/


Testing
---

Steps to check 
1)create 2 users with userName user1,user2
2)create 1 dataset by user 1 and add user 2 in dataset ACL with permission VIEW
3)use GET API (service/gds/dataset) with query param createdBy we will get 
dataset in response
4)Request ==> (service/gds/dataset?createdBy=user2)


Thanks,

Prashant Satam

Re: Review Request 74538: RANGER-4345 plugin side metrics on polling from the policy server

[Sai Sandeep Rangisetti via Review Board]

> On Nov. 28, 2023, 9:12 a.m., Ramachandran Krishnan wrote:
> > agents-common/src/main/java/org/apache/ranger/plugin/util/PolicyRefresher.java
> > Lines 55 (patched)
> > 
> >
> > Are we adding metrics only for Policy download ?.It would be great if 
> > you add the same for roles as well.The policy refresher thread will 
> > download policies as well as roles also.

RangerRESTClient should handle all the API calls including policy download and 
role download. I had added additional metrics for roles just like for policies


- Sai Sandeep


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74538/#review226013
---


On Dec. 13, 2023, 10:45 a.m., Sai Sandeep Rangisetti wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74538/
> ---
> 
> (Updated Dec. 13, 2023, 10:45 a.m.)
> 
> 
> Review request for ranger, Kishor Gollapalliwar, Abhay Kulkarni, Madhan 
> Neethiraj, Mehul Parikh, Pradeep Agrawal, and Ramachandran Krishnan.
> 
> 
> Bugs: RANGER-4345
> https://issues.apache.org/jira/browse/RANGER-4345
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Add metrics in the plugins for increased visibility on what is happening in 
> the systems
> 
> 
> Diffs
> -
> 
>   agents-common/pom.xml 12e093f78915a77a14e5489e0c9cd2492382017f 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/PolicyRefresher.java
>  aa0c801199cb6e50b0b307471e5579f762721c89 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/RangerMetricRegistry.java
>  PRE-CREATION 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/RangerRESTClient.java
>  e54313403d2207cf82838f4cae4ead63dee38069 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/RangerRolesProvider.java
>  58a47cf1b07f88f06304a9ff8f4272c5e84e700a 
> 
> 
> Diff: https://reviews.apache.org/r/74538/diff/5/
> 
> 
> Testing
> ---
> 
> Compiled and installed the hbase plugin and verified that metrics are being 
> published to jmx. Simulated failures by blocking port and verified timeout 
> and retry metrics are also being published
> 
> 
> Thanks,
> 
> Sai Sandeep Rangisetti
> 
>

Re: Review Request 74538: RANGER-4345 plugin side metrics on polling from the policy server

[Sai Sandeep Rangisetti via Review Board]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74538/
---

(Updated Dec. 13, 2023, 10:45 a.m.)


Review request for ranger, Kishor Gollapalliwar, Abhay Kulkarni, Madhan 
Neethiraj, Mehul Parikh, Pradeep Agrawal, and Ramachandran Krishnan.


Changes
---

Added metrics in RangerRolesProvider


Bugs: RANGER-4345
https://issues.apache.org/jira/browse/RANGER-4345


Repository: ranger


Description
---

Add metrics in the plugins for increased visibility on what is happening in the 
systems


Diffs (updated)
-

  agents-common/pom.xml 12e093f78915a77a14e5489e0c9cd2492382017f 
  
agents-common/src/main/java/org/apache/ranger/plugin/util/PolicyRefresher.java 
aa0c801199cb6e50b0b307471e5579f762721c89 
  
agents-common/src/main/java/org/apache/ranger/plugin/util/RangerMetricRegistry.java
 PRE-CREATION 
  
agents-common/src/main/java/org/apache/ranger/plugin/util/RangerRESTClient.java 
e54313403d2207cf82838f4cae4ead63dee38069 
  
agents-common/src/main/java/org/apache/ranger/plugin/util/RangerRolesProvider.java
 58a47cf1b07f88f06304a9ff8f4272c5e84e700a 


Diff: https://reviews.apache.org/r/74538/diff/5/

Changes: https://reviews.apache.org/r/74538/diff/4-5/


Testing
---

Compiled and installed the hbase plugin and verified that metrics are being 
published to jmx. Simulated failures by blocking port and verified timeout and 
retry metrics are also being published


Thanks,

Sai Sandeep Rangisetti

[jira] [Updated] (RANGER-4604) Need to add query param createdBy for security-zone GET API

[Prashant Satam (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prashant Satam updated RANGER-4604:
---
Description: We need to add a query param createdBy for security-zone GET 
API. It will be useful to filter list of security-zones created by user, 
especially to get the security-zone created by self  (was: We need to add a 
query param createdBy for security-zone GET API)

> Need to add query param createdBy for security-zone GET API
> ---
>
> Key: RANGER-4604
> URL: https://issues.apache.org/jira/browse/RANGER-4604
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Major
>
> We need to add a query param createdBy for security-zone GET API. It will be 
> useful to filter list of security-zones created by user, especially to get 
> the security-zone created by self



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (RANGER-4603) Need to add query param createdBy for dataset GET API

[Prashant Satam (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prashant Satam updated RANGER-4603:
---
Description: Currently we have dataset GET APIs to get list datasets based 
on ACL. It will be useful to be able filter the list based on users who created 
the dataset, especially to get the datasets created by self.  (was: Currently 
we have dataset GET APIs to get list datasets based on ACL. It will be useful 
to be able filter the list based users who created the dataset, especially to 
get the datasets created by self.)

> Need to add query param createdBy for dataset GET API
> -
>
> Key: RANGER-4603
> URL: https://issues.apache.org/jira/browse/RANGER-4603
> Project: Ranger
>  Issue Type: Sub-task
>  Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Major
>
> Currently we have dataset GET APIs to get list datasets based on ACL. It will 
> be useful to be able filter the list based on users who created the dataset, 
> especially to get the datasets created by self.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (RANGER-4603) Need to add query param createdBy for dataset GET API

[Prashant Satam (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prashant Satam updated RANGER-4603:
---
Description: Currently we have dataset GET APIs to get list datasets based 
on ACL. It will be useful to be able filter the list based users who created 
the dataset, especially to get the datasets created by self.  (was: We need add 
a query param createdBy for dataset GET API it will be needed in case of 
(/dataset/summary) API )

> Need to add query param createdBy for dataset GET API
> -
>
> Key: RANGER-4603
> URL: https://issues.apache.org/jira/browse/RANGER-4603
> Project: Ranger
>  Issue Type: Sub-task
>  Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Major
>
> Currently we have dataset GET APIs to get list datasets based on ACL. It will 
> be useful to be able filter the list based users who created the dataset, 
> especially to get the datasets created by self.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (RANGER-4604) Need to add query param createdBy for security-zone GET API

[Prashant Satam (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prashant Satam reassigned RANGER-4604:
--

Assignee: Prashant Satam

> Need to add query param createdBy for security-zone GET API
> ---
>
> Key: RANGER-4604
> URL: https://issues.apache.org/jira/browse/RANGER-4604
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Major
>
> We need to add a query param createdBy for security-zone GET API



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (RANGER-4603) Need to add query param createdBy for dataset GET API

[Prashant Satam (Jira)]

Prashant Satam created RANGER-4603:
--

 Summary: Need to add query param createdBy for dataset GET API
 Key: RANGER-4603
 URL: https://issues.apache.org/jira/browse/RANGER-4603
 Project: Ranger
  Issue Type: Sub-task
  Components: Ranger
Reporter: Prashant Satam


We need add a query param createdBy for dataset GET API it will be needed in 
case of (/dataset/summary) API 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (RANGER-4604) Need to add query param createdBy for security-zone GET API

[Prashant Satam (Jira)]

Prashant Satam created RANGER-4604:
--

 Summary: Need to add query param createdBy for security-zone GET 
API
 Key: RANGER-4604
 URL: https://issues.apache.org/jira/browse/RANGER-4604
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Reporter: Prashant Satam


We need to add a query param createdBy for security-zone GET API



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (RANGER-4603) Need to add query param createdBy for dataset GET API

[Prashant Satam (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prashant Satam reassigned RANGER-4603:
--

Assignee: Prashant Satam

> Need to add query param createdBy for dataset GET API
> -
>
> Key: RANGER-4603
> URL: https://issues.apache.org/jira/browse/RANGER-4603
> Project: Ranger
>  Issue Type: Sub-task
>  Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Major
>
> We need add a query param createdBy for dataset GET API it will be needed in 
> case of (/dataset/summary) API 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (RANGER-4557) Need api to get count of all request list according to their status and the total count of requests.

[Anand Nadar (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anand Nadar resolved RANGER-4557.
-
Resolution: Workaround

> Need api to get count of all request list according to their status and the 
> total count of requests.
> 
>
> Key: RANGER-4557
> URL: https://issues.apache.org/jira/browse/RANGER-4557
> Project: Ranger
>  Issue Type: Sub-task
>  Components: admin
>Reporter: Anand Nadar
>Priority: Critical
>
> Need an api which returns the count of requests according to their status and 
> the total count of requests.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (RANGER-4557) Need api to get count of all request list according to their status and the total count of requests.

[Anand Nadar (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796098#comment-17796098
 ] 

Anand Nadar commented on RANGER-4557:
-

This ticket will not be needed as we will be getting all the data from  
/dataset/summary?datasetId=  and then calculate the count of shareStatus 
from UI end.
Marking this ticket as invalid.

> Need api to get count of all request list according to their status and the 
> total count of requests.
> 
>
> Key: RANGER-4557
> URL: https://issues.apache.org/jira/browse/RANGER-4557
> Project: Ranger
>  Issue Type: Sub-task
>  Components: admin
>Reporter: Anand Nadar
>Priority: Critical
>
> Need an api which returns the count of requests according to their status and 
> the total count of requests.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)