16

3

I'd like to add support for Custom Fields plugin into Foglyn, but I need to

  1. be able to retrieve list of all custom fields and their configuration through XML API: name (preferrably long one), type, upon what actions it is editable
  2. be able to edit fields when creating, rediting, resolving or closing case

It seems that editing of custom fields possible (except when creating new case), but I cannot find any way how to fetch list of available custom fields. What am I missing?

Fog Creek Case FC1956302

flag

3 Answers

1

In general, plugins and the API aren't very well integrated, for a variety of reasons.

Querying any bug and adding "plugin" to the list of cols will return all custom fields, so you can get a list, but there's no easy way to get a list of possible values.

If you're willing to get your hands dirty, you can start at default.asp?pg=pgPluginConfig&sPluginId=customfields@fogcreek.com and scrape the possible values.

link|flag
Scraping is a possibility, but it can break too easily :-( Thank you for suggestion. – Peter Štibraný Sep 27 2010 at 16:35
1

Many bug trackers such as Jira, VersionOne, TFS WorkItem Tracking, HP Quality Center, Assembla, etc. already support creating and querying custom fields. They also support submitting bug/defect along with custom fields' value. It would be great if XML API also support this so that other system can integrate with FogBugz. Thanks.

link|flag
0

I have opened a case to look into how to expose the lists of possible values to the XML API for a future release. Please up-vote this question (not this answer) to show your support for adding this functionality.

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.