Often, when I am reading through features, I realize someone has added a new one that's a duplicate, and I want to merge them. The "old" feature name is most often the one we want to keep, not the new one.
I'm not sure if it is a naming issue when merging Feature Requests as Neil described above, but there is definitely something off here.
Merging is inconsisttent: when merging tags, it uses the existing tag name and tells you "Select a tag to merge into 'the current tag". But then it is the other way around for Feature Requests: when clicking on Merge, you are merging the current Feature Request into a different one.
I would say the corrent way is how Feature Requests do it, and the same logic should apply everywhere else. In other words, when I click on Merge on a specific item, I expect this item to be merged into different one (the seloected item gets merged into another one; keeping the name of the item that it is merged into). At least this is the way it's done in other good user interfaces, so that's how I would do it here. Seems more like a consistency issue and best practices issue to me, rather than a problem with merging Feature Requests specifically (if anything, merging Tags is the wrong way around).
Activity
Often, when I am reading through features, I realize someone has added a new one that's a duplicate, and I want to merge them. The "old" feature name is most often the one we want to keep, not the new one.
I'm not sure if it is a naming issue when merging Feature Requests as Neil described above, but there is definitely something off here.
Merging is inconsisttent: when merging tags, it uses the existing tag name and tells you "Select a tag to merge into 'the current tag". But then it is the other way around for Feature Requests: when clicking on Merge, you are merging the current Feature Request into a different one.
I would say the corrent way is how Feature Requests do it, and the same logic should apply everywhere else. In other words, when I click on Merge on a specific item, I expect this item to be merged into different one (the seloected item gets merged into another one; keeping the name of the item that it is merged into). At least this is the way it's done in other good user interfaces, so that's how I would do it here. Seems more like a consistency issue and best practices issue to me, rather than a problem with merging Feature Requests specifically (if anything, merging Tags is the wrong way around).