relations Questions - FogBugz Knowledge Exchange

Feature Request: Remove relations (links) between cases

2009-12-17T19:41:26Z

I have cases linked to my case in the see also section. I want to remove the links. How do I do it?

One use case for removing a relation is using Case Event Edit to fix the text of a bugevent. When I incorrectly type in 'case x' where I meant to enter 'case y', If I then edit the post, It adds the new relation to y. I would assume the link to case x would be removed as well.

Case FC1259445

Definitive Syntax to Associate & Link Cases in FogBugz, Kiln and the Wiki.

2011-08-30T07:39:23Z

Okay so I think there should be a point of reference on how to cross-link / associate / relate cases to and from each other within FogBugz, Kiln, the Wiki, Discussions etc...

Because linking Cases in FogBugz and Kiln is awesome.

The Basics:

http://kiln.stackexchange.com/questions/491

review 123
case 123
bug 123

http://fogbugz.stackexchange.com/questions/4405 & http://fogbugz.stackexchange.com/questions/4417

BugzID: 1234

Assuming these works too?

Review: 123
Case: 123
Bug: 123

How bout plural?

Cases 123
Bugs 123

Advance stuff:

http://kiln.stackexchange.com/questions/1320/

If you haven't made a commit yet, simply mention the case in the commit message. For example, "Fixes case 123", "bugzid: 123", "Solves some bugs (bug ids 123, 456, and 789)" all work just fine, and will cause bidirectional linking.

bug ids 123, 456, 789

I tried to make this clear, but apparently I failed. You need the word "case", "bug", "bug id", "bugz id", or "review" in front of the case number. All of the examples above follow that. The only pseudoexception is that, if enumerating multiple cases, you only need to have the word appear in front of the first. Thus, "Fixes cases 123 and 456" will work, but "Fixes 123 and 456" will fail.

cases 123 and 456

...but not

Case 123 & 456

How about...

BugzId: 123 456 789    
Cases 123, 456, 789

Sadly some of the advance linking only works from Kiln to FogBugz but doesn't work from within FogBugz itself.

The point is, I'm not sure which does work, and which doesn't work... the fact that you can say:

Case #blah #blah

and have it show up auto-magically in FogBugz under "See also" related cases field is awesome and amazing. (should be easy to unlink though)

I just think it should work the same way throughout FogBugz & Kiln, or at least have a definitive reference for all the syntax in the docs somewhere.

Editted:

Ben Pollack was nice enough to release the RegExp for Kiln here:

\b(?<case>(review|case|bug[zs]?(\s| )*(id)?:?)s?(\s| )*([#:; ]| )+)((([ ,:;#]|and)*)(?<bugid>\d+))+

Plural Case Linking "Related Cases"

2011-07-26T06:50:53Z

Plural text "Cases 308, 309" doesen't auto-link ?

I thought it did... (I think it links in Kiln?)

Shouldn't have to say "Case 308, Case 309"

Thanks :)

How do I get the list of related cases for a CBug in my plugin?

2010-07-12T18:33:46Z

I can get the related cases for a given case via the XML API, but how do I get them in a plugin?

Case FC1917292

Can I use the number of "see also" links to a case to search or even display this figure in fogbugz?

2010-07-28T17:30:14Z

I'd like to be able to list or even find cases based on how many other cases it is linked to, we are using this to record duplicate requests from users for new features.

Should I be using occurrences instead? I can't seem to find a simple way to mark one case as another occurrence of another case?

Can I use a custom field to connect several cases to one case?

2010-07-20T20:50:03Z

Can I create a custom field to define several cases to one case? If so, how?

Incoming customer emails create case relations when they have case numbers in the bodies

2010-02-05T16:33:01Z

I have a case 1234. If a customer emails in with the text "case 1234" in the body of their email, a case relation is created. Is this intended?

Case FC1129713

XML API returns wrong ixRelatedBugs when referenced on wiki page

2010-06-02T14:30:05Z

Using the XML API, if you pass in an ixBug that is referenced on a Wiki Page, the ixRelatedBugs column will return the same ixBug you're passing in for each wiki reference instance. I ended up having to filter out the display of those if the ixBugRelation values match the ixBug being passed in.

1. Find one to test:

SELECT TOP 10 *
FROM fogbugz.dbo.BugRelation (NOLOCK)
WHERE ixWikiPageFrom <> 0
ORDER BY ixBugTo DESC

2. Call the XML API

/api.asp?cmd=search&ixBug=[ixBug]&cols=ixRelatedBugs&token=[token]

Expect

ixBug not in the list as a related case

Bug

ixBug is in the list

Case FC1917312