Martyn Houghton Posted January 14, 2020 Posted January 14, 2020 @Steve G I am able to to successfully use the JIRA -> Create Issue Method to create issues in our cloud based JIRA instance where the form does not contain any mandatory fields of type 'Option' or 'Multi Select Array'. I am trying to implement logging of 'Support Item' issue type in our JIRA instance from Service Manager. The create issue form has both a mandatory 'Customer' field with prescribed options and a multi select field for versions. I have tried populating both but the JIRA Create Issue method fails. As there is no error logged I cannot determine whether it is failing on both or just one of them, as both are mandatory. How can I diagnose this further? Cheers Martyn
Martyn Houghton Posted January 21, 2020 Author Posted January 21, 2020 @Steve G The issue appears to be that the 'versions' field is not a custom field, but a standard one in the JIRA schema of type array/multi-select. Therefore the prefix applied of 'customfield_xxxx' when using the custom array parameter will not work. I will raise a new forum post for this to be added as an enhancement., whilst I still try to resolve the issue with the other Customer Field. Cheers Martyn
Martyn Houghton Posted January 21, 2020 Author Posted January 21, 2020 Enhancement raised on post below.
Martyn Houghton Posted January 21, 2020 Author Posted January 21, 2020 In terms of the actual custom field with options, the issue appears to be the way the parameter is passed to the API call. I have tried passing the value id and value itself but neither work. "iBridge Method: /Atlassian/Jira Cloud/Update Issue.m Error: Jira Error: customfield_10714: Could not find valid 'id' or 'value' in the Parent Option object...." I suspect their needs to be an additional option of 'SelectList' along with the current 'Text' and 'Number' options, so that the api call format below can be used. https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/#creating-an-issue-examples Cheers Martyn
Steve G Posted January 21, 2020 Posted January 21, 2020 Hi @Martyn Houghton, I've added these, and the other 2 posts, to the list. I'll let you know once we've had chance to have a look at them. Cheers, Steve
Martyn Houghton Posted January 21, 2020 Author Posted January 21, 2020 @Steve G Thanks for the update. Taken me a while to break down the different issues. Cheers Martyn
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now