[ALF-15544] Incorrect notification for move action for locked on-premise copy Created: 17-Aug-12  Updated: 21-Jan-16  Resolved: 17-Jul-14

Status: Closed
Project: Alfresco
Component/s: Share Application
Affects Version/s: 4.1 Enterprise
Fix Version/s: None
Security Level: external (External user)

Type: Bug Priority: Minor
Reporter: Alfresco QA Team (Inactive) Assignee: Closed Issues
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Alfresco 4.1 build 130, tomcat6, java6, postgresql (all installer deployed), windowx7, ie9, Solr

Attachments: PNG File move1.png     PNG File move2.png     PNG File move_to.png    
Issue Links:
is related to by MNT-2641 User can delete or move a working copy Closed
Date of First Response:


1. Alt least one network and at least one site are setup in Cloud;
2. User have access to the Cloud accounts;
3. Log in Alfresco Share (On-premise) as any user;
4. Create any site in Alfresco Share (On-premise);
5. Any file is created/uploaded into the Document Library, synced to Cloud and locked 'on-premise' copy;
6. Choose Delete option from More+ menu for created file (absent according specification);
7. Choose Move option from Selected drop down menu-->Move option is available but shouldn't be, pop-up window to choose target location for move action is appeared
8. Choose target location for move action and click Ok button-->Incorrect notification appears the successful move of the locked file, file is not moved.

Actual result: Message about the successful moved of the locked file, but file is displayed at the page.

Expected result: message about impossibility of move action should appear or Move option should be absent

Thank you,

Comment by Will Taylor [X] (Inactive) [ 17-Jul-14 ]

This issue has been re-triaged and determined as “Won’t Fix” and Closed.
Many factors were considered in this decision, among which is the need to correctly prioritise the work of the Engineering team and be clear with those issues that are not going to be resolved.

Generated at Fri Dec 04 05:13:30 GMT 2020 using Jira 7.13.15#713015-sha1:7c5ddd2c3e1709974ae9c48c17df8edd3919fe2c.