Feature suggestions: Merging

[dkalweit]

Hi. I've been using merging a lot lately, and I have a couple feature suggestions for Vault/Fortress. I don't know where you normally submit it, so I'm just doing it here. They're mostly all little annoyance things.

1. I typically merge from 1 branch to another-- it would be nice to have a shortcut or something that can be setup to merge from my 'product' branch to 'v3.0' branch for example.

2. The merge wizard is way too long - I don't want empty screens saying nothing has happened, such as no renames and no moves. Typically I'm only merging branches with changed files-- going through an extra 3+ screens is just an annoyance. Other extra screens just get in the way and make the process more arduous.

3. I'm unable to double click a project name(source and target pages), hit enter once I've selected it, or use an ALT+N to go to the next page in the wizard. This means I have to click the branch with my mouse, and then CLICK the next button-- a little thing, but it's an annoyance when I'm merging multiple little changes a day...

4. The 'Settings' page lets me set the comment for all changes, which is nice-- but it's a multi-line comment with 'Merge Branches...', a blank line, 'Version :xxx' which is a useless # to me, and then my actual comment from the code change. I actively change this to 'Merge - [my comment]'. It would be nice to have a way to set a 'template' of some sorts for this merge comment... I like 1-line comments like this so I can easily see in the history lists what each change was for.


Thanks for listening.


--
Derek

[Beth]

Can you explain item one further? Are you looking for a shortcut that just repeats the merge with the same options selected?

F: (2)14813, (4)14814, (3)14815, (1)14817

[robe070]

Our whole team (30+ developers) use merging frequently during the later stages of a major release - up to 2 months. These suggestions would make a large difference to us. We agree with ALL the suggestions. e.g. we have a work practice to ALWAYS change the suggested comment to put the actual change description first - so we can see it in the history views.