|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
|
|
Remove bugtraq:number information from Recent MessagesHi There,
I am using TortoiseSVN and allowing it to interface with FogBugz. We have the bugtraq:number property enabled and the user has to enter an issue number before committing. What we are seeing is the following: - Commit a certain piece of code and submit the bugtraq number using the textbox: 1 - Do another commit after making changes but instead choose bugnumber: 2 - Select recent messages and select the previous message - This inserts: Previous Comment which includes BugID: 1 - When the commit is completed and we look at the recent messages we see: Comment BugID: 1 BugID: 2 I was wondering was, when we select a recent message to reuse, is it possible to remove the BugID which was added to the comment previously before the "message" field is populated. Thanks ------------------------------------------------------ http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2412161 To unsubscribe from this discussion, e-mail: [users-unsubscribe@...]. |
|
|
Re: Remove bugtraq:number information from Recent MessagesWe are currently using version 1.5.9.15518 and upgrading to
1.6.6.17493. Adding more information to clarify the issue I am seeing. Usage with Version 1.5.9.15518 1. Check in a file with BugzID: 12 and add comment: asasas 2. The screen-shot just before check-in : http://tortoisesvn.googlegroups.com/web/1.5.9.15518%20-%20Original%20Message.JPG?gsc=fITssgsAAABipLvHJSU10qtt5OaBwY1I 3. Edit the same file 4. Check in file with BugzID: 13 - Add comment asasass - Click on "Recent Messages" - Select the previous commit for BugzID: 12 - Another line is added to the new comment without the old "BugzID: 12" 5. Please see screen-shot just before check-in: http://tortoisesvn.googlegroups.com/web/1.5.9.15518%20-%20NewMessage_plus_RecentMessages.JPG?gsc=McM7qgsAAABcjjUgN-klWq2AnQ5E46JH Usage with Version 1.6.6.17493 1. Check in a file with BugzID: 12 and add comment: asasas 2. The screen-shot just before check-in : http://tortoisesvn.googlegroups.com/web/1.6.6.17493%20-%20Original%20Message.JPG?gsc=zdoR5AsAAADa7JBQfIazzaht9TIEQwif 3. Edit the same file 4. Check in file with BugzID: 13 - Add comment asasass - Click on "Recent Messages" - Select the previous commit for BugzID: 12 - Another line is added to the new comment with the old "BugzID: 12" 5. Please see screen-shot just before check-in: http://tortoisesvn.googlegroups.com/web/1.6.6.17493%20-%20NewMessage_plus_RecentMessages.JPG?gsc=EzSP1wsAAAARGDun0THmCacsyKg7dIKL When the commit is completed, the final log message contains BugzID:12 and BugzID:13 in the comment. This was not the case before with the old version of TortoiseSVN. We currently us FogBugz for our bugtracking sytem and even though this commit was supposed to be only filed under Bug: 13 it is actually also filed under Bug: 12 which is incorrect. I am not sure whether this is by design in TortoiseSVN 1.6 or not. If it is by design is there any way to get the old functionality back using the SVN properties? The SVN properties we are currently using: bugtraq:label = BugzID bugtraq:message = BugzID:%BUGID% bugtraq:number = true bugtraq:warnifnoissue = true Appreciate your help. Dhruv ------------------------------------------------------ http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2412231 To unsubscribe from this discussion, e-mail: [users-unsubscribe@...]. |
|
|
Re: Remove bugtraq:number information from Recent MessagesOn 28.10.2009 20:34, Dhruv wrote:
> We are currently using version 1.5.9.15518 and upgrading to > 1.6.6.17493. > > Adding more information to clarify the issue I am seeing. > > Usage with Version 1.5.9.15518 > 1. Check in a file with BugzID: 12 and add comment: asasas > 2. The screen-shot just before check-in : > http://tortoisesvn.googlegroups.com/web/1.5.9.15518%20-%20Original%20Message.JPG?gsc=fITssgsAAABipLvHJSU10qtt5OaBwY1I > > 3. Edit the same file > 4. Check in file with BugzID: 13 > - Add comment asasass > - Click on "Recent Messages" > - Select the previous commit for BugzID: 12 > - Another line is added to the new comment without the old > "BugzID: 12" > 5. Please see screen-shot just before check-in: > http://tortoisesvn.googlegroups.com/web/1.5.9.15518%20-%20NewMessage_plus_RecentMessages.JPG?gsc=McM7qgsAAABcjjUgN-klWq2AnQ5E46JH > > Usage with Version 1.6.6.17493 > 1. Check in a file with BugzID: 12 and add comment: asasas > 2. The screen-shot just before check-in : > http://tortoisesvn.googlegroups.com/web/1.6.6.17493%20-%20Original%20Message.JPG?gsc=zdoR5AsAAADa7JBQfIazzaht9TIEQwif > > 3. Edit the same file > 4. Check in file with BugzID: 13 > - Add comment asasass > - Click on "Recent Messages" > - Select the previous commit for BugzID: 12 > - Another line is added to the new comment with the old "BugzID: > 12" > 5. Please see screen-shot just before check-in: > http://tortoisesvn.googlegroups.com/web/1.6.6.17493%20-%20NewMessage_plus_RecentMessages.JPG?gsc=EzSP1wsAAAARGDun0THmCacsyKg7dIKL > > When the commit is completed, the final log message contains BugzID:12 > and BugzID:13 in the comment. This was not the case before with the > old version of TortoiseSVN. > > We currently us FogBugz for our bugtracking sytem and even though this > commit was supposed to be only filed under Bug: 13 it is actually also > filed under Bug: 12 which is incorrect. > > I am not sure whether this is by design in TortoiseSVN 1.6 or not. If > it is by design is there any way to get the old functionality back > using the SVN properties? It is by design and was requested that it work that way. But you can see that the old issue number is inserted and correct it before you commit, so it really shouldn't be a problem? Stefan -- ___ oo // \\ "De Chelonian Mobile" (_,\/ \_/ \ TortoiseSVN \ \_/_\_/> The coolest Interface to (Sub)Version Control /_/ \_\ http://tortoisesvn.net ------------------------------------------------------ http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2412782 To unsubscribe from this discussion, e-mail: [users-unsubscribe@...]. |
|
|
Re: Remove bugtraq:number information from Recent MessagesThanks for your response.
Just wanted to make sure this was not a bug and indeed a design change. We just have to make sure we update our scripts to handle this. Since we parse the bug ID numbers entered by the users. Thanks On Oct 29, 1:48 pm, Stefan Küng <tortoise...@...> wrote: > On 28.10.2009 20:34, Dhruv wrote: > > > > > We are currently using version 1.5.9.15518 and upgrading to > > 1.6.6.17493. > > > Adding more information to clarify the issue I am seeing. > > > Usage with Version 1.5.9.15518 > > 1. Check in a file with BugzID: 12 and add comment: asasas > > 2. The screen-shot just before check-in : > >http://tortoisesvn.googlegroups.com/web/1.5.9.15518%20-%20Original%20... > > > 3. Edit the same file > > 4. Check in file with BugzID: 13 > > - Add comment asasass > > - Click on "Recent Messages" > > - Select the previous commit for BugzID: 12 > > - Another line is added to the new comment without the old > > "BugzID: 12" > > 5. Please see screen-shot just before check-in: > >http://tortoisesvn.googlegroups.com/web/1.5.9.15518%20-%20NewMessage_... > > > Usage with Version 1.6.6.17493 > > 1. Check in a file with BugzID: 12 and add comment: asasas > > 2. The screen-shot just before check-in : > >http://tortoisesvn.googlegroups.com/web/1.6.6.17493%20-%20Original%20... > > > 3. Edit the same file > > 4. Check in file with BugzID: 13 > > - Add comment asasass > > - Click on "Recent Messages" > > - Select the previous commit for BugzID: 12 > > - Another line is added to the new comment with the old "BugzID: > > 12" > > 5. Please see screen-shot just before check-in: > >http://tortoisesvn.googlegroups.com/web/1.6.6.17493%20-%20NewMessage_... > > > When the commit is completed, the final log message contains BugzID:12 > > and BugzID:13 in the comment. This was not the case before with the > > old version of TortoiseSVN. > > > We currently us FogBugz for our bugtracking sytem and even though this > > commit was supposed to be only filed under Bug: 13 it is actually also > > filed under Bug: 12 which is incorrect. > > > I am not sure whether this is by design in TortoiseSVN 1.6 or not. If > > it is by design is there any way to get the old functionality back > > using the SVN properties? > > It is by design and was requested that it work that way. > But you can see that the old issue number is inserted and correct it > before you commit, so it really shouldn't be a problem? > > Stefan > > -- > ___ > oo // \\ "De Chelonian Mobile" > (_,\/ \_/ \ TortoiseSVN > \ \_/_\_/> The coolest Interface to (Sub)Version Control > /_/ \_\ http://tortoisesvn.net > > ------------------------------------------------------http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMess... > > To unsubscribe from this discussion, e-mail: [users-unsubscr...@...]. ------------------------------------------------------ http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2415262 To unsubscribe from this discussion, e-mail: [users-unsubscribe@...]. |
| Free embeddable forum powered by Nabble | Forum Help |