Project

General

Profile

Actions
Copy link

Bug #27278

open

When a pending request trying to Terminate from DocPro Action page showing "HTTP 503 Error" /Access Denied

Added by Preethi A about 1 year ago. Updated 3 months ago.

Status:
Open
Priority:
Low
Assignee:
Jacqueline Antonette
Start date:
02/18/2024
Due date:
% Done:

0%

Estimated time:
Steps To Reproduce:

Login as PM
Go To Doc Pro Action Page
Open any Pending Request of Project Charter or Project Plan
Check behavior after Terminate that request.

MODULES:
DOCPRO
Build Cycle:
Cycle 2
Customer:
Internal
Issue Dependency:
It is fixed in 11.3.0 Cycle 3, now reopened moved to know issues
Dev Commitment to Resolve in::

Description

When a pending request trying to Terminate from DocPro Action page showing "HTTP 503 Error". Termination happening but showing error page instead of showing other pending request list.

Files

Download all files
Terminate Pending Request Error.png (95.5 KB) Terminate Pending Request Error.png Error page after termination Preethi A, 02/18/2024 12:34 AM
Access Denied after Termination.png (81.4 KB) Access Denied after Termination.png Access Denied after termination Preethi A, 08/01/2024 11:33 AM
Actions
Copy link
 #1

Updated by User Admin about 1 year ago

  • Status changed from New to Open
Actions
Copy link
 #2

Updated by User Admin about 1 year ago

  • Build Cycle changed from Cycle 1 to Cycle 0
Actions
Copy link
 #3

Updated by Jacqueline Antonette 11 months ago

  • Assignee changed from Jacqueline Antonette to Raghu Ram
  • MODULES SUITE added
  • MODULES deleted (DOCPRO)
Actions
Copy link
 #4

Updated by Raghu Ram 11 months ago

  • Assignee changed from Raghu Ram to Nikhil d
Actions
Copy link
 #5

Updated by Nikhil d 11 months ago

  • Assignee changed from Nikhil d to Raghu Ram

redirecting to raghuram

Actions
Copy link
 #6

Updated by Raghu Ram 11 months ago

  • Assignee changed from Raghu Ram to Jacqueline Antonette
Actions
Copy link
 #8

Updated by Preethi A 10 months ago

  • MODULES DOCPRO added
  • MODULES deleted (SUITE)
Actions
Copy link
 #9

Updated by Preethi A 10 months ago

  • Priority changed from Medium to Low

Since it is not replicating for dev team, changing the priority from Medium to Low

Actions
Copy link
 #10

Updated by Jacqueline Antonette 10 months ago

  • Status changed from Open to Resolved

Once we move the 1130 to cloudqa1 this issue will get automatically resolved

Actions
Copy link
 #11

Updated by Preethi A 9 months ago

Not resolved in cloudqa3 site. Now behavior changed and showing Access Denied message (screenshot attached) instead of Error page. Expecting behavior is to display Action page after reloading.

Actions
Copy link
 #12

Updated by Jacqueline Antonette 8 months ago

  • Status changed from Not Resolved to Resolved
Actions
Copy link
 #13

Updated by Preethi A 7 months ago

  • Status changed from Resolved to Closed
  • Build Cycle changed from Cycle 0 to Cycle 4
  • Issue Dependency set to from Cycle 0
  • How do we missed in Testing ? set to Doc Pro issue, reported in cycle 0. Environment change is the reason reported by Dev team

As it is not replicating in 113.0 Cycle 3 & 4, closing this issue now. Verified 11.3.0 in Gabriel DB and Parker Dev site, QA Site. Customers are not reported this issue in their environment.

Actions
Copy link
 #14

Updated by User Admin 3 months ago

  • Status changed from Closed to Reopen
Actions
Copy link
 #15

Updated by Preethi A 3 months ago

  • Project changed from SP 11.3.0 to SP 11.3.2
  • Subject changed from When a pending request trying to Terminate from DocPro Action page showing "HTTP 503 Error" to When a pending request trying to Terminate from DocPro Action page showing "HTTP 503 Error" /Access Denied
  • Build Cycle changed from Cycle 4 to Cycle 2
  • Customer set to Internal
  • Issue Dependency changed from from Cycle 0 to It is fixed in 11.3.0 Cycle 3, now reopened
  • ISSUE TYPE deleted (EXISTING)
  • How do we missed in Testing ? deleted (Doc Pro issue, reported in cycle 0. Environment change is the reason reported by Dev team)

User date format was DD/MM/YYYYY, for other date formats it is working fine. Also from Action Management > Action > Documents it is working fine.

Actions
Copy link
 #16

Updated by Jacqueline Antonette 3 months ago

  • Status changed from Reopen to Resolved

Not able to replicating it in the local

Actions
Copy link
 #17

Updated by Preethi A 3 months ago

  • Status changed from Resolved to Not Resolved

This is replicating in cloudqa3 (11.3.2 cycle 3) also. So changing status as Not Resolved

Actions
Copy link
 #18

Updated by Jacqueline Antonette 3 months ago

  • Status changed from Not Resolved to Resolved

we are not fixing this because not using port in the url

Actions
Copy link
 #19

Updated by User Admin 3 months ago

  • Status changed from Resolved to Open
Actions
Copy link
 #20

Updated by User Admin 3 months ago

  • Status changed from Open to Resolved
Actions
Copy link
 #21

Updated by User Admin 3 months ago

  • Status changed from Resolved to Not Resolved
Actions
Copy link
 #22

Updated by User Admin 3 months ago

  • Project changed from SP 11.3.2 to Known Issue
  • Status changed from Not Resolved to Open
  • Issue Dependency changed from It is fixed in 11.3.0 Cycle 3, now reopened to It is fixed in 11.3.0 Cycle 3, now reopened moved to know issues
Actions
Copy link

Also available in: Atom PDF