New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
257: Proper setting of custom fields in Jira issues #392
Conversation
|
Webrevs
|
Looks good! Just a minor nit: since this patch was created the JSON
API has gotten the possibility to query JSONValue
objects for their type using is*
methods (e.g. isObject()
). If you merge master into this PR then you will be able to use these new methods
if (!name.startsWith("customfield_")) { | ||
return unfiltered; | ||
} | ||
if (unfiltered instanceof JSONObject) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if (unfiltered instanceof JSONObject) { | |
if (unfiltered.isObject()) { |
@rwestberg This change now passes all automated pre-integration checks. When the change also fulfills all project specific requirements, type
|
/integrate |
@rwestberg |
Mailing list message from Robin Westberg on skara-dev: Changeset: 72c721a 257: Proper setting of custom fields in Jira issues Reviewed-by: ehelin ! bots/notify/src/test/java/org/openjdk/skara/bots/notify/UpdaterTests.java |
Hi all,
Please review this change that properly sets custom fields when creating Jira issues.
Best regards,
Robin
Progress
Issue
SKARA-257: Proper setting of custom fields in Jira issues
Approvers