Search the Community
Showing results for tags 'create issue'.
Extended the current JIRA Cloud and On-Premise iBridge integration methods for Create and Update to allow access to the standard field 'versions' which is a multiselect array type. Not able to populate or update this using the custom field array type option. As this is very often a mandatory field in JIRA as it is used for development/release management, we are not able to raise requests where this is the case. Cheers Martyn
As per previous post (link at bottom) this is an enhancement requests for the addition of an option for 'SelectList' along with the current 'Text' and 'Number' options in the JIRA Create and Update Issues methods, 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 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
I am now looking to integrate to a JIRA Cloud instance as well as on premises, but have struck a problem with creating a test request as the integration process is failing, but the error in the logs is not given any indication of the why. I can create a request manually using the same credentials with only specifying the Summary, Description and Priority. I suspect the issue is the priority value but cannot be sure as there is not detailed error/response information being provided. Is there any additional logging we can check to help diagnose where it is failing? Cheers Martyn