Jump to content

Search the Community

Showing results for tags 'jira cloud'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Hornbill Platform and Applications
    • OpenForWork
    • Announcements
    • Blog Article Discussions
    • General Non-Product Discussions
    • Application Beta Program
    • Collaboration
    • Employee Portal
    • Service Manager
    • IT Operations Management
    • Project Manager
    • Supplier Manager
    • Customer Manager
    • Document 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 6 results

  1. 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
  2. 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
  3. @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
  4. I am attempting add a Label to a JIRA Issue using the JIRA Cloud 'update Issue' integration node. I am passing the mandatory key field and a value in the Labels attribute, but the update is not adding the label to the issue. I tested this with both the injections for the values from variables as well as hard coding as below. I am wondering if the Labels element which is a new addition is using the wrong attribute type/dialog, as it is different to the way you set 'Labels' when creating the case using the 'Create Issue' option. Cheers Martyn
  5. @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
  6. When using the JIRA Cloud iBridge Integration - Comment Issue, how do you inject the 'key' of the item in JIRA you want to comment on, as there does not appear to be a variable to inject this? Is it hard coded to use the External Reference? Cheers Martyn
×
×
  • Create New...