[CONTTAGS-60] Tagging multiple items doesn't work correctly Created: 26/Feb/18  Updated: 30/Sep/21  Resolved: 30/Sep/21

Status: Closed
Project: Content Tags
Component/s: None
Affects Version/s: 1.0.1
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Pieter Ardinois Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: tagging, y2k
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

MacOsX High Sierra


Attachments: PNG File image-2018-02-26-11-00-15-881.png     PNG File image-2018-02-26-11-00-32-233.png     PNG File image-2018-02-26-11-00-56-484.png     PNG File image-2018-02-26-11-01-19-557.png     PNG File image-2018-02-26-11-02-25-427.png     PNG File image-2018-02-26-11-02-42-542.png     File tags1.webm     File tags2.webm    
Issue Links:
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

When adding tags to multiple nodes, the proces works fine if both nodes already have at least one tag assigned.
If one of the nodes to be tagged is empty, it will automatically get all the tags the other node is tagged with.
By default all the common tags are listed, but when no tags are already assigned all the tags from 1 node are being assigned



 Comments   
Comment by Ervin Vystup [ 26/Feb/18 ]

Reproducible in the Assets app
Case 1:
If you choose 2 items where one of them is empty, you can see in the "Tags" field that all tags are listed from the first item -> it is incorrect because you should see just common tags from all items.

tags1.webm

 

Case 2:
If you choose 3 items where two of them are already filled with some tags and one isn't, in the "Tags" field the common tags are listed from these 2 non-empty items. Unfortunately it is also incorrect because just tags common for all chosen fields should be listed there - in this case therefore no tags because one field is empty.

tags2.webm

 

Results:
New tags are always added after the tags which are already listed in the "Tags" field. So it is necessary to list them there correctly. All the tags in the "Tags" field are then copied also to the assets with empty tags. You can see the behavior also in the records above.

Comment by Marta Kobus [ 30/Sep/21 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

 

Thank you,

The Magnolia Team

Generated at Mon Feb 12 00:24:34 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.