Project

General

Profile

Actions
Copy link

Bug #5962

closed

Publish for Approval(Chrome Browser) - Unable to select Level to Publish the Document

Added by Shankar Narayanan almost 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Start date:
05/22/2018
Due date:
% Done:

100%

Estimated time:
Steps To Reproduce:

1.Select a PI
2.Select VOC from the menu
3.Click Publish for Approval button
4.Click on level icon to select Level
5.Observe the result

MODULES:
RFD
Build Cycle:
Cycle 1
Customer:
Issue Dependency:
SP810 Dev build
Dev Commitment to Resolve in::

Description

•Unable to select Level to Publish the Document.

Files

2018-05-22 Levels.png (112 KB) 2018-05-22 Levels.png Shankar Narayanan, 05/22/2018 05:24 PM
Actions
Copy link
 #1

Updated by Shankar Narayanan almost 7 years ago

  • Subject changed from Publish for Approval - Unable to select Level to Publish the Document to Publish for Approval(Chrome Browser) - Unable to select Level to Publish the Document
  • Description updated (diff)
Actions
Copy link
 #2

Updated by Anonymous almost 7 years ago

  • Assignee changed from Anonymous to Anonymous
Actions
Copy link
 #3

Updated by User Admin almost 7 years ago

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

Updated by User Admin almost 7 years ago

  • Assignee changed from Anonymous to Anonymous
Actions
Copy link
 #5

Updated by Anonymous almost 7 years ago

  • Status changed from Open to Resolved

Doc Pro Related Issue

Actions
Copy link
 #6

Updated by Shankar Narayanan over 6 years ago

  • Status changed from Resolved to Not Resolved

Level cannot be selected in any browser

Actions
Copy link
 #7

Updated by Anonymous over 6 years ago

  • Assignee changed from Anonymous to Anonymous
Actions
Copy link
 #8

Updated by Anonymous over 6 years ago

  • % Done changed from 0 to 100
Actions
Copy link
 #9

Updated by Shankar Narayanan over 6 years ago

  • Project changed from SP810 Dev Build to SP810 - QA build
  • Build Cycle changed from Cycle 3 to Cycle 1
  • Issue Dependency set to SP810 Dev build
Actions
Copy link
 #10

Updated by Anonymous over 6 years ago

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

Updated by Shankar Narayanan over 6 years ago

  • Status changed from Resolved to Fixed with Hotfix
Actions
Copy link
 #12

Updated by Shankar Narayanan over 6 years ago

  • Status changed from Fixed with Hotfix to Resolved
Actions
Copy link
 #13

Updated by Shankar Narayanan over 6 years ago

  • Status changed from Resolved to Closed

Closed in SP810 Cycle 2

Actions
Copy link

Also available in: Atom PDF