
Experience a seamless, real-time and bi-directional HP ALM Jira Integration
Syncing of issues and defects happens automatically in real-time, bi-directionally between HP QC/ALM, Jira (cloud, server, DC) and other trackers like ServiceNow, Zendesk, Github and more.
Custom fields, attachments, comments,... Control exactly what to share & who to share it with. Thus keeping confidential data private & secure. Secondly, no team needs to change their workflow to synchronize.
Have a question? Our support team of true heroes will assist you any step of the way. We know this is important to you. So reach us through live chat, Email, service desk or the Atlassian forum. Whatever you prefer.
Syncing of issues and defects happens automatically in real-time, bi-directionally between multiple Jira's (cloud and/or server) and HP QC ALM. Jira Service Desk support. Multi-project scenario's.
Custom fields, attachments, comments,... Control exactly what to share & who to share it with. Thus keeping confidential data private & secure. Secondly, no team needs to change their workflow to synchronize.
Have a question? Our support team of true heroes will assist you any step of the way. We know this is important to you. So reach us through live chat, Email, service desk or the Atlassian forum. Whatever you prefer.
More details
Exalate for HP ALM/QC is not a Jira app, but an HP ALM add-on to complement to the “Jira Issue Sync & more” app.
In order for your synchronization to work, you have to also install “Exalate Jira Issue Sync & more” on your Jira instance. This app can be found here.
Exalate for HP ALM supports:
- Bi-directional, secure sync
- Sync all data, including custom fields, attachments, comments and work logs
- Respects comment visibility for all use cases
- Each party defines what is private or shared
- Easy to get started
- Works out of the box
- No intermediate server needed
- As configurable as Jira itself through a flexible scripting engine
- Cut delays with instant synchronisation
- Upgrade flexibly - forward compatibility built in by design
- The sync panel provides your users the guarantee that the synchronisation completed successfully
- Supports Jira Cloud to Cloud sync
More details
Are you looking for a flexible issue sync solution to implement cross organisation issue tracking ?
Exalate provides a flexible synchronization engine such that issues are automatically and securely synced - between multiple Jira's & HP QC - wherever hosted.
Benefit from a unified view and integrated workflow!
Some properties
- Bi-directional, secure sync
- Sync all data, including custom fields, attachments, comments and work logs
- Respects comment visibility for all use cases
- Each party defines what is private or shared
- Easy to get started
- Works out of the box
- No intermediate server needed
- As configurable as Jira itself through a flexible scripting engine
- Cut delays with instant synchronisation
- Upgrade flexibly - forward compatibility built in by design
- The sync panel provides your users the guarantee that the synchronisation completed successfully
- Supports Jira Cloud to Cloud sync
Reviews for cloud
(0)Sign in to write a reviewReviews for server
(0)Sign in to write a reviewReviews for Data Center
(0)Sign in to write a reviewCloud Pricing
Server Pricing
Data Center Pricing
This app is sold by a third-party vendor.
Let us know that you'd like to manage this app's billing on your Atlassian invoice.This app is sold by a third-party vendor.
Contact the vendor to evaluate or purchase this app.Pricing FAQ
- What does 'paid-via-vendor' mean?
Paid-via-vendor apps are licensed and purchased directly through the vendor who makes this app.
Payment for paid-via-vendor apps is not handled by Atlassian.
- Will paid-via-vendor transactions be on my Atlassian invoice?
Paid-via-vendor transactions are not managed by Atlassian. This means transactions for paid-via-vendor apps will not be on your Atlassian invoice.
Pricing FAQ
- What does 'paid-via-vendor' mean?
Paid-via-vendor apps are licensed and purchased directly through the vendor who makes this app.
Payment for paid-via-vendor apps is not handled by Atlassian.
- Will paid-via-vendor transactions be on my Atlassian invoice?
Paid-via-vendor transactions are not managed by Atlassian. This means transactions for paid-via-vendor apps will not be on your Atlassian invoice.
iDalko provides support for this app.
iDalko provides support for this app.
Vendor support resources
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Vendor support resources
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Jira Cloud • Released 2018-02-27
Summary
Bug fixes and improving usability
Details
In this release we have improved the usability of the product by making some bug fixes and improvements
Versions
Version 1.0.2 • Jira Server 6.3 - 7.7.4 • Released 2018-01-25
Summary
Bug fixes and improving usability
Details
In this release we have improved the usability of the product by making some bug fixes and improvements
Installation
- Check the documentation about the step by step installation of HP QC Node - here
- Go to the installation page and follow the proposed steps.
- Install Exalate on the other side of the connection by selecting another connector on the Exalate Integrations Page.