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

Brijesh Bhalala updated RANGER-4532:
------------------------------------
    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 before going to login page.
2)In Audit admin session Id modal, the loader is not in sync.

Improvise a loader in both the scenarios. 
1)Add a loader in policy page.
2)Sync the loader in audit session Id modal



  was:
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".
2)In Audit admin session Id modal, the loader is not in sync.

Improvise a loader in both the scenarios. 




> 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
>
>
> 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 before going to login page.
> 2)In Audit admin session Id modal, the loader is not in sync.
> Improvise a loader in both the scenarios. 
> 1)Add a loader in policy page.
> 2)Sync the loader in audit session Id modal



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

Reply via email to