Feature suggestion for next release

bwilson · Post by **bwilson** » Wed Feb 02, 2005 11:26 am

Just wanted to suggest a new feature for the next Vault release...

Add an option to REQUIRE associating to a valid bug/issue number on check-in. It could work just like the "Require Check-In comments" checkbox in the Vault Admin - Repository Options tab. If the bug# is keyed in by user rather than selected from 'Browse', Vault should query to make sure the bug# entered is a valid and open one.

Is it likely this could be included in next release?

Any update on target availabliity date?

Thanks,

Billy

bfinney · Post by **bfinney** » Mon Feb 07, 2005 10:11 am

Thanks for the suggestion - I've added it to our request list. I can't make a good guess about a time frame, but it's not likely to make it into 3.1, which is currently being worked on.

christian · Post by **christian** » Tue Feb 08, 2005 7:32 am

Another related suggestion: Allow more granular control over which folder we can associate rules against.

Often there are a number of codelines within the same Vault Repository eg Mainline, ReleaseCandidate_1.0, PrivateCode all with different requirements as to what policy rules should be enforced. Being able to associate rules at the folder level would be in line with practice.

Thanks
Christian

ericsink · Post by **ericsink** » Tue Feb 08, 2005 9:30 am

christian wrote:Another related suggestion: Allow more granular control over which folder we can associate rules against.

Often there are a number of codelines within the same Vault Repository eg Mainline, ReleaseCandidate_1.0, PrivateCode all with different requirements as to what policy rules should be enforced. Being able to associate rules at the folder level would be in line with practice.

Thanks
Christian

Thus far, we have resisted the temptation to incorporate much workflow support into Vault. We don't want the tool to impose any particular methodology.

I don't think we will begin adding these kinds of features until we are ready to design them well enough to make them very flexible, somewhat like you are describing in the quoted material just above. We still won't want to impose any particular methodology.

christian · Post by **christian** » Tue Feb 08, 2005 9:59 am

I agree that Vault shouldn't be *imposing* a methodology. I tend to think enforcing code line policies in general from a tool could suggest that there's a lack of communication and discipline in a team, fix that and you don’t need the code line policy. Having said that I've made check-in comments mandatory!

C