Jump to content

Search the Community

Showing results for tags 'jira'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Hornbill Platform and Applications
    • Announcements
    • Blog Article Discussions
    • General Non-Product Discussions
    • Application Beta Program
    • Collaboration
    • Employee Portal
    • Service Manager
    • Project Manager
    • Supplier Manager
    • Customer Manager
    • Document Manager
    • Configuration Manager
    • Timesheet Manager
    • Live Chat
    • Board Manager
    • Mobile Apps
    • System Administration
    • Integration Connectors, API & Webhooks
    • Performance Analytics
    • Hornbill Switch On & Implementation Questions
  • About the Forum
    • Announcements
    • Suggestions and Feedback
    • Problems and Questions
  • Gamers Club's Games
  • Gamers Club's LFT

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Organisation


Location


Interests


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype

Found 11 results

  1. Can I request an enhancement to the extend the JIRA iBridge integration to be able to trigger an 'transition' as it is called by Atlassian. In our case we are wishing to trigger the re-opening transistion from Hornbill. https://community.atlassian.com/t5/Answers-Developer-Questions/Can-anyone-let-me-know-if-I-can-re-open-an-incident-using-JIRA/qaq-p/533765 Cheers Martyn
  2. 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
  3. 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
  4. @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
  5. @Steve G Would it be possible to form the JIRA 'Comment Issue' to return a status parameter similar to the 'Update Issue' so we can then branch in the workflow based on the outcome. We are to get around the absence of this on the 'Create Issue' node as we can check if the 'key' parameter is set as a means to determine if the integration step was successful. Cheers Martyn
  6. @Steve G Could the current 'Create Issue' node be updated to allow the passing of 'Labels' when creating an issue. The current 'Desk' implementation I am trying to replicate as part of moving a new part of the business over to Hornbill inserts the hyperlink back to the original 'Desk' case in as a label in creation of the case in JIRA. Cheers Martyn
  7. 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
  8. Integration bridge now throws an exception when creating Jira tickets from Hornbill integration Bridge. iBridge Method: /Atlassian/Jira Cloud/Create Issue.m Error: Jira Error: summary: Field 'summary' cannot be set. It is not on the appropriate screen, or unknown. description: Field 'description' cannot be set. It is not on the appropriate screen, or unknown.... It has come suddenly, first seen today and has worked flawlessly for a quite a while. Have Atlassian changed the API so iBridge is no longer usable or is error within Business Process?
  9. Hi Just calling on the collected expertize of the community to help me get Atlassian Integration working. What i'm trying to do is use the Business Process and integration bridge to create a form/template that contains information that will be pushed to Jira. Something like this. Hornbill Request ID: (Taken from Flowcode variable) Steps to reproduce: (Here the Analyst fills in the steps necessary) Expected Result: (Here the Analyst fills in the info) Actual Result: (Here the Analyst fills in the info) The contents of the form would then be added to the Description Field in the Integration Parameters (see attached screenshot) First I just used the Description Flowcode Information but R&D blocked it since the quality of the created Jira was too low and they wanted something along the lines above. Any help is appreciated.
  10. We have an on-prem Atlassian JIRA installation which is externally facing over https:. The current iBridge JIRA integration is based on Atlassian hosted service where you only specify the domain within their hosted environment, whereas we would want to later the endpoint to point URL as a whole to point to our on-prem installation. Would it be possible to re-use the current JIRA integration but make it use a on-prem set of endpoints? Cheers Martyn
  11. I need some help connecting guest.ui.app.com.hornbill.servicemanager.integration.jira.issueType and guest.ui.app.com.hornbill.servicemanager.integration.jira.projectName to a change ticket since these will be chosen when creating the Jira from within Hornbill. My question is: How do I add this information to the business process since it's dynamic.
×
×
  • Create New...