Jira Integration : Connection Alias field not showing up in Flow Designer Action - Create Issue ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2023 11:07 AM
I am trying integrate JIRA in my ServiceNow PDI. I have created Credentials, Connection and credentials as shown below
In flow-designer, when I create Create Issue Action, I do not see Connection Alias field. Can someone help me in this. I have seen similar issues being asked in the community, could not find the solution. Any idea ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2023 09:52 AM
Hi Indyguy
Please check permissions for that particular field. Jira Spoke needs to be able to edit it.
Can I please recommend you Exalate, which is a decentralized tool that makes integrations like this way more straight-forward. I have been using it for a while and it works really good!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2023 02:07 PM
Can you help me how can I check the permission for the filed Connection Alisa (Connection & Credential Aliases)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2023 02:49 AM
Hi @indyguy,
You can consider a less technical alternative for ServiceNow and Jira integration - OpsHub’s free Community Edition, that integrates standard entities. An Atlassian partner and a ServiceNow certified integration tool, OpsHub offers a federated integration platform that can help ease your integration journey.
OpsHub also takes care of the following use cases:
-Format retention: ServiceNow uses HTML text formatting, while Jira uses Wiki markup text formatting. OpsHub retains the format when integrating data between ServiceNow and Jira.
-Assignment group – Jira project mapping: Jira users use Projects, whereas ServiceNow users often use 'Assignment Group' or some other field, for organizing their data. With OpsHub, data can be mapped across different Jira projects based on the ServiceNow Assignment group.
-Data Granularity: OpsHub also integrates history between ServiceNow and Jira. E.g., between the two syncs, if the user modifies the status from Open -> In Progress -> Resolved in Jira, OpsHub allows users to see the exact transition (Open -> In Progress -> Resolved) happening in ServiceNow too.
-Field-level conflict management: If you are looking to integrate data bidirectionally, data may be updated simultaneously in ServiceNow and Jira, causing conflicts. OpsHub supports Field-level conflict management to maintain consistent data across ServiceNow and Jira.
Supported entities: All System and Custom Tables on ServiceNow and all System & Custom Issue Types, Sub-Task Types, Version, and Worklog on Jira are supported by the OpsHub.
You can reach out to OpsHub’s integration experts for an initial consultation on discussion on your use case and planning of integration strategy.
Thanks,
Vishal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2023 02:38 PM
My question was related to JIRA Spoke only.. Not an alternative solution 🙂😀😞