Project

General

Profile

Actions

Bug #27885

open

Multi site--> Inherit from parent revision option is not working as expected for existing folder. Please read the description

Added by Kiruthika G about 1 year ago. Updated 4 months ago.

Status:
Open
Priority:
Medium
Start date:
04/08/2024
Due date:
% Done:

0%

Estimated time:
Steps To Reproduce:

1. Login EwQIMS as Doc pro module administrator
2. Click on folder management (it should have some hierarchy)
3. Map the revision option as custom
4. Do the New doc request, draft and draft from toc
5. Goto the folder management
6. Click on the child folder and click on the inherit from parent revision option.
7. Observe the behaviour

MODULES:
DOCPRO
Build Cycle:
Cycle 0
Customer:
Issue Dependency:
Moved from 112015 HF
Dev Commitment to Resolve in::

Description

When the user mapped custom with segment 1 for parent level and completed the document request, draft and draft from TOC.

And then again click on the same folder under the folder management and click the child folder as "Inherit from parent revision" and save. It is not showing in the child folder


Files

Actions #1

Updated by Kiruthika G about 1 year ago

  • Subject changed from Multi site--> Inherit from parent revision option is not working as expected. Please read the description to Multi site--> Inherit from parent revision option is not working as expected for existing folder. Please read the description
Actions #2

Updated by User Admin about 1 year ago

  • Status changed from New to Open
Actions #3

Updated by Kiruthika G about 1 year ago

  • Priority changed from High to Medium
Actions #4

Updated by User Admin 12 months ago

  • Project changed from SP 11.2.0.14 Patches to SP 11.2.0.15 Patches
  • Build Cycle changed from Cycle 1 to Cycle 0

Moving from SP 112014 patch release

Actions #6

Updated by User Admin 10 months ago

  • Project changed from SP 11.2.0.15 Patches to SP 11.2.0.16 Patches
  • Issue Dependency set to Moved from 112015 HF
Actions #7

Updated by Kiruthika G 4 months ago

  • Project changed from SP 11.2.0.16 Patches to SP 11.2.0.18 Patches

Still this issue is in open status so moving to 18HF project

Actions

Also available in: Atom PDF