[MNT-10089] Tags section works incorrectly after deleting content Created: 03-Apr-13  Updated: 27-May-14  Resolved: 17-Dec-13

Status: Closed
Project: Service Packs and Hot Fixes
Component/s: Tags and Categories
Affects Version/s: 4.2
Fix Version/s: None

Type: Bug
Reporter: Alfresco QA Team (Inactive) Assignee: Closed Issues
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 2 days, 5 hours
Original Estimate: Not Specified
Environment:

Alfresco Enterprise v4.2.0 (r48616-b1379) schema 6023; RHEL 6.3 X64, MySQL 5.5, mysql-connector-java-5.1.17-bin.jar, Tomcat 7.0.35, JDK 7 U13, Alfresco+ OpenLDAP 2.4.23; Client: FF v19.0.2, Windows 7 SP1 X64


Attachments: JPEG File deleting_topic.jpg     JPEG File tags_section.jpg    
Issue Links:
Duplicate
Bug Priority:
Category 3
Testcase ID:

Enterprise40x-4365


 Description   

Steps to reproduce:

1. User is logged in as Site Manager for the Site;
3. Any Topic with tags was created for current Site;
3. Discussions component page is opened;
4. Delete created topic on "Discussions Topic List" page.

Actual result: Topic was deleted from List, there are no tags to associate with deleted topic in Tags section.

Expected result: Topic was deleted from List, but Tags section wasn't refreshed (see attachments). The system works correctly only after reloading page.

The same system behaviour is observed while deleting items with tags on the Document Library and Blog pages. On the Calendar, Wiki and Links pages Tags section refreshed correctly.



 Comments   
Comment by Brian Remmington [ 14-Jun-13 ]

Is this a regression? Please would you indicate when this test case was last run successfully?

Comment by Alfresco QA Team (Inactive) [ 02-Oct-13 ]

The issue is reproduced on Alfresco Enterprise v4.2.0 (r56130-b1527), ootb, RHEL 6.4 x64
client: Win7x64, FF 23
We have no execution history, the issue was found randomly during testing

Comment by Alfresco QA Team (Inactive) [ 17-Dec-13 ]

closed as won't fix

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