Make it possible to change tags in multiple photos at one time
Submitted by an unknown user
Link to original bug (#717838)
Description
---- Reported by shotwell-maint@gnome.bugs 2011-06-05 04:13:00 -0700 ----
Original Redmine bug id: 3715
Original URL: http://redmine.yorba.org/issues/3715
Searchable id: yorba-bug-3715
Original author: Kostas -
Original description:
At the moment it is only possible to change a tag from one photo instead of changing the tags from multiple photos.
Related issues:
- related to shotwell - Feature #2382 (closed): possibly combine Add Tags and Modify Tags commands (Open)
- related to shotwell - Feature #3415: Dragging photo(s) to tagname with CTRL should remove that... (Open)
- duplicated by shotwell - Feature #4206 (closed): Modify tags for multiple images (Duplicate)
- duplicated by shotwell - Feature #6393: modify tags on multiple images simultaneously (Duplicate)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-16 14:44:00 -0700 ----
History
Comment 1
Updated by Jim Nelson about 2 years ago
- Subject changed from Make it possible to change multiple tags in one time to Make it possible to change tags in multiple photos at one time
Comment 2
Updated by Jim Nelson about 1 year ago
- Priority changed from Low to High
- Target version set to 0.14.0
Comment 3
Updated by Jim Nelson 11 months ago
- Category set to tags
Comment 4
Updated by Jim Nelson 11 months ago
- Target version changed from 0.14.0 to 0.15.0
Comment 5
Updated by Jim Nelson 8 months ago
- Target version changed from 0.15.0 to 0.16.0
Comment 6
Updated by Jim Nelson 6 months ago
-
Target version deleted (
<strike>
_0.16.0_</strike>
)
--- Bug imported by chaz@yorba.org 2013-11-25 21:54 UTC ---
This bug was previously known as bug 3715 at http://redmine.yorba.org/show_bug.cgi?id=3715
Unknown version " in product shotwell. Setting version to "!unspecified". 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. Resolution set on an open status. Dropping resolution
Resolution: RESOLVED OBSOLETE