Configuring Additional Case Columns - For use with third-party plugins? #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
with third-party plugins, e.g. Kanban.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The FogBugz API supports querying and updating columns / fields that are associated with other third-party plugins, as well as the core FogBugz fields associated with each case. See the following link:
http://fogbugz.stackexchange.com/questions/729/access-custom-fields-or-other-plugin-field-such-as-backlog-on-a-case-using-the
This change supports adding an additional configuration key to the fbapi4j configuration file called "case.columns". This setting (a CSV of column names) instructs the CaseHandler on which columns to request whilst performing HTTP GET calls.
Appropriate test cases added.