StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3610
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
2008-09-09T22:45:40.670
CreationDate
2008-08-06T16:12:49.533
FavoriteCount
0
LastActivityDate
2012-04-01T09:10:27.697
LastEditDate
2012-04-01T09:10:27.697
LastEditorUserId
1219121
OwnerUserId
58
ParentId
3607
PostTypeId
2
Score
11
ViewCount
0
LastEditorDisplayName
Jeff Atwood
text
Body
This answer is incomplete and flawed! It only works from TortoisSVN to Fogbugz, but not the other way around. I still need to know how to get it to work backwards from Fogbugz (like it's designed to) so that I can see the Revision number a bug is addressed in from Fogbugz while looking at a bug. <hr> <h2>Helpful URLS</h2> <a href="http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-propertypage.html" rel="nofollow noreferrer">http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-propertypage.html</a> <a href="http://tortoisesvn.net/issuetracker_integration" rel="nofollow noreferrer">http://tortoisesvn.net/issuetracker_integration</a> <hr> <h2>Set the "Hooks"</h2> <ol> <li>Go into your fogbugz account and click Extras > Configure Source Control Integration</li> <li>Download "post-commit.bat" and the VBScript file for Subversion</li> <li>Create a "hooks" directory in a common easily accessed location (preferably with no spaces in the file path)</li> <li>Place a copy of the files in the hooks directories</li> <li>Rename the files without the ".safe" extension</li> <li>Right click on any directory.</li> <li>Select "TortoiseSVN > Settings" (in the right click menu from the last step)</li> <li>Select "Hook Scripts"</li> </ol> <a href="http://www.chomperstomp.com/img/tortoiseSVNSettings.png" rel="nofollow noreferrer">http://www.chomperstomp.com/img/tortoiseSVNSettings.png</a> <ol> <li>Click "Add"</li> <li>Set the properties thus: <ul> <li>Hook Type: Post-Commit Hook </li> <li>Working Copy Path: C:\\Projects (or whatever your root directory for all of your projects is. If you have multiple you will need to do this step for each one.) </li> <li>Command Line To Execute: C:\\subversion\\hooks\\post-commit.bat (this needs to point to wherever you put your hooks directory from step 3)</li> <li>I also selected the checkbox to Wait for the script to finish...</li> </ul></li> </ol> WARNING: Don't forget the double back-slash! "\\" Click OK... <img src="https://i.stack.imgur.com/GFHEz.png" alt="Adding a Hook Script"> Note: the screenshot is different, follow the text for the file paths, NOT the screenshot... At this point it would seem you could click "Issue Tracker Integration" and select Fogbugz. nope. It just returns "There are no issue-tracker providers available". <ol> <li>Click "OK" to close the whole settings dialogue window</li> </ol> <h2>Configure the Properties</h2> <ol start="2"> <li>Once again, Right click on the root directory of the checked out project you want to work with (you need to do this "configure the properties" step for each project -- See "Migrating Properties Between Projects" below)</li> <li>Select "TortoiseSVN > Properties" (in the right click menu from the last step)</li> <li>Add five property value pairs by clicking "New..." and inserting the following in "Property Name" and "Property Value" respectively:</li> </ol> <blockquote> bugtraq:label BugzID: bugtraq:message BugzID: %%BUGID%% bugtraq:number true bugtraq:url <a href="http://[your" rel="nofollow noreferrer">http://[your</a> fogbugz URL here]/default.asp?%BUGID% bugtraq:warnifnoissue false </blockquote> <img src="https://i.stack.imgur.com/K28XR.png" alt="properties window"> <img src="https://i.stack.imgur.com/yDnSC.png" alt="adding new property"> <ol start="15"> <li>Click "OK"</li> </ol> <h2>Commiting Changes and Viewing the Logs</h2> Now when you are commiting, you can specify one bug that the commit addresses. This kind of forces you to commit after fixing each bug... <img src="https://i.stack.imgur.com/pGnHL.png" alt="specifying bug addressed when commiting"> When you view the log (Right click root of project, TortoiseSVN > show log) you can see the bug id that each checking corresponds to (1), and you can click the bug id number to be taken to fogbugz to view that bug automatically if you are looking at the actual log message. Pretty nifty! <a href="http://www.chomperstomp.com/img/viewLog.png" rel="nofollow noreferrer">http://www.chomperstomp.com/img/viewLog.png</a> <hr> <h2>Migrating Properties Between Projects</h2> <ol> <li>Right click on a project that already has the proper Properties configuration</li> <li>Select "TortoiseSVN > Properties" (from the right-click menu from step 1)</li> <li>Highlight all of the desired properties</li> <li>Click "Export"</li> <li>Name the file after the property, and place in an easily accessible directory (I placed mine with the hooks files)</li> </ol> <img src="https://i.stack.imgur.com/ywPry.png" alt="save properties dialogue"> <ol start="5"> <li>Right click on the root directory of the checked out project needing properties set for.</li> <li>Click "Import"</li> <li>Select the file you exported in step 4 above</li> <li>Click Open</li> </ol>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIntegrating Fogbugz with TortoiseSVN with no URL/Subversion backend
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USNeysor
UserOwnerUserId
1. UScmcculloh
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.