© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Understood. However, I do think this is a tremendously useful feature, so I have a more limited suggestion that *seems* do-able as it is effectively the same as renaming tags manually: forget about moving the children and only move/rename the selected/dragged tag, which would *simply* require the dragged tag to be renamed to the New Parent Tag + "." + Existing Tag Name.
The children of the dragged tags would remain behind, thus a "dummy" parent would stay there as well. But this already happens when I manually rename/move a tag. Once the children tags are also renamed, the "dummy" parent disappears.
e.g. I want to put the History hierarchy within the Nonfiction one.
Origial:
History (10)
History.American (6)
History.
Nonfiction (100)
Final:
Nonfiction (110)
Nonfiction.History (10)
Nonfiction.
Nonfiction.
The simplified proposal would be to only move/rename one tag at a time. If that happens to be History, you get
History (6)
History.American (6)
History.
Nonfiction (104)
Nonfiction.History (4)
If I then rename/drag History.American to Nonfiction.
History (3)
History.American (3)
History.
Nonfiction (107)
Nonfiction.History (7)
Nonfiction.
and finally after renaming/dragging the Civil War child, the History hierarchy disappears altogether.
Nonfiction (110)
Nonfiction.History (10)
Nonfiction.
Nonfiction.
The net effect is that I can drag the 3 (or, in reality, dozens/hundreds of) tags in 3 seconds vs multiple clicks and typing to rename them - maybe 30 seconds? Multipled across dozens or even hundreds of tags (and users) and the time savings adds up.
This appears to be possible, but I know nothing about actual coding and of course defer to your expertise and inclination. If still rejected, could it at least be left in a list of Open/Maybe/Wishlist enhancements rather than Wont Fix/Rejected?
Thanks for all your hard work and extreme responsiveness!