Actions
Bug #1191
closedAfter creating default folder in parent entity, doing action in PPT1 (Corporate) site system not able to create default folder in PPT 1 site. Because of that publish documents and attached documents are cant able to be viewed (multi site)
Start date:
05/14/2017
Due date:
% Done:
0%
Estimated time:
Steps To Reproduce:
1. Log into Audit pro as parent entity user.
2. publish the document in PPT ss.
3. Log in as PPT 1 (Corporate) user.
4. Add actual audit and perform.
5. Click on attachments nt shows the attachments.
MODULES:
AUDITPRO
Build Cycle:
Cycle 0
Customer:
Issue Dependency:
Multi-Site
Dev Commitment to Resolve in::
NA
Description
After creating default folder in parent entity, doing action in PPT1 (Corporate) site system not able to create default folder in PPT 1 site. Because of that publish documents and attached documents are cant able to be viewed.
Updated by Anonymous almost 8 years ago
- Assignee changed from Anonymous to Nikhil d
Root Cause Analyses 16-05-2017
Dead line 17-05-2017
Updated by Anonymous almost 8 years ago
- Status changed from Fixed in Dev to Resolved
Updated by Anonymous almost 8 years ago
- Status changed from Resolved to Yet to Verify
Updated by Anonymous almost 8 years ago
- Project changed from EwQIMS SP636 to EwQIMS SP700
- Subject changed from After creating default folder in parent entity, doing action in PPT1 (Corporate) site system not able to create default folder in PPT 1 site. Because of that publish documents and attached documents are cant able to be viewed. to After creating default folder in parent entity, doing action in PPT1 (Corporate) site system not able to create default folder in PPT 1 site. Because of that publish documents and attached documents are cant able to be viewed (multi site)
- Build Cycle changed from Cycle 4 to Cycle 0
- Issue Dependency changed from Multi Site to 636
- Dev Commitment to Resolve in: set to NA
Updated by User Admin almost 8 years ago
- Status changed from Yet to Verify to Open
Updated by Anonymous almost 8 years ago
- Status changed from Resolved to Yet to Verify
issue related to multi site need to verify
Updated by Anonymous almost 8 years ago
- Issue Dependency changed from 636 to Multi-Site
Updated by Anonymous almost 8 years ago
- Status changed from Yet to Verify to Closed
Actions