With metadata writing on, unwanted tags are generated when the user drags a child tag to the top level.
Submitted by cli..@..ba.org
Assigned to Lucas Beeler
Link to original bug (#717979)
Description
---- Reported by clinton@yorba.org 2011-08-30 15:05:00 -0700 ----
Original Redmine bug id: 4071
Original URL: http://redmine.yorba.org/issues/4071
Searchable id: yorba-bug-4071
Original author: Clinton Rogers
Original description:
Steps to reproduce:
With metadata writing enabled, import some metadata-capable photos that contain no metadata.
Create a tag named 'a'.
Create a child tag under 'a' named 'b'.
Create a child tag under 'b' named 'c'.
At the top level, create a tag named 'b'.
Add at least one photograph to 'c'.
Add at least one photograph to the top level 'b'.
Drag the nested 'b' up to the 'Tags' tree item and drop it.
Notice that, frequently, incorrect and unwanted tags suddenly appear.
NOTE: the bug is not sensitive to what tags are named, so 'a', 'b' and 'c' may be replaced by any valid name.
Related issues:
- related to shotwell - 4074: When metadata writing is turned on, reimport can cause HT... (Fixed)
- related to shotwell - 4096: "Hierarchical Subject" not updated when metadata writing on (Fixed)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:38:00 -0700 ----
History
Comment 1
Updated by Clinton Rogers about 2 years ago
- Description updated (diff)
Comment 2
Updated by Jim Nelson about 2 years ago
- Assignee set to Lucas Beeler
Comment 3
Updated by Lucas Beeler about 2 years ago
- Status changed from Open to 5
- Resolution set to fixed
Fixed in 5da85af7
Comment 4
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:54 UTC ---
This bug was previously known as bug 4071 at http://redmine.yorba.org/show_bug.cgi?id=4071
Unknown Component Using default product and component set in Parameters Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Version: 0.11.1
Resolution: RESOLVED FIXED