# End-to-End Use Cases **URL:** https://community.exalate.com/c/use-case/6.md [Latest](https://community.exalate.com/latest.md) · [Categories](https://community.exalate.com/categories.md) · [Tags](https://community.exalate.com/tags.md) --- ## [About the End-to-End Use Cases category](https://community.exalate.com/t/about-the-end-to-end-use-cases-category/2223)
**Author:** [@Javier](https://community.exalate.com/u/Javier)\ **Replies:** 0\ **Last updated:** [November 3, 2024, 4:58pm UTC](https://community.exalate.com/t/about-the-end-to-end-use-cases-category/2223 "2024-11-03T16:58:37Z")
Complete sync solutions for real-world integration needs. Use this category to share, explore, and discuss complete synchronization use cases built with Exalate. Use cases typically include both outgoing and incoming s… --- ## [Bidirectional Sync Issue Links/Relations Between Jira Cloud and Azure Devops (Updated)](https://community.exalate.com/t/bidirectional-sync-issue-links-relations-between-jira-cloud-and-azure-devops-updated/8338)
**Author:** [@Javier](https://community.exalate.com/u/Javier)\ **Replies:** 0\ **Last updated:** [August 28, 2026, 8:45pm UTC](https://community.exalate.com/t/bidirectional-sync-issue-links-relations-between-jira-cloud-and-azure-devops-updated/8338 "2026-08-28T20:45:02Z")
This use case shows how to synchronize issue links and relationships bidirectionally between Jira Cloud and Azure DevOps. The scripts retrieve the relationships from each platform, identify the corresponding synchronize… --- ## [Jira Cloud — Populating a Mandatory Comment on a Workflow Transition Screen (Exalate)](https://community.exalate.com/t/jira-cloud-populating-a-mandatory-comment-on-a-workflow-transition-screen-exalate/8160)
**Author:** [@Sonal\_Otwani](https://community.exalate.com/u/Sonal_Otwani)\ **Replies:** 0\ **Last updated:** [June 22, 2026, 3:37pm UTC](https://community.exalate.com/t/jira-cloud-populating-a-mandatory-comment-on-a-workflow-transition-screen-exalate/8160 "2026-06-22T15:37:58Z")
1. Use case A client has configured their Jira Cloud workflow so that a transition (e.g. Resolve / move to Done) shows a transition screen with a mandatory Comment field. A user cannot complete the transition in the Jir… --- ## [Jira Cloud GitHub: Leveraging GitHub TaskLists to emulate the Epic-Child relationship from Jira](https://community.exalate.com/t/jira-cloud-github-leveraging-github-tasklists-to-emulate-the-epic-child-relationship-from-jira/5827)
**Author:** [@Dhiren](https://community.exalate.com/u/Dhiren)\ **Replies:** 2\ **Last updated:** [January 19, 2026, 7:49pm UTC](https://community.exalate.com/t/jira-cloud-github-leveraging-github-tasklists-to-emulate-the-epic-child-relationship-from-jira/5827 "2026-01-19T19:49:35Z")
Jira allows you to create complex hierarchy between issues to better organize your project. However, if you are syncing such a Jira project to GitHub, chances are you would want to maintain some semblance of this hierarc… --- ## [Salesforce ↔ Azure DevOps: Comments Synchronization](https://community.exalate.com/t/salesforce-azure-devops-comments-synchronization/7561)
**Author:** [@Sonal\_Otwani](https://community.exalate.com/u/Sonal_Otwani)\ **Replies:** 0\ **Last updated:** [December 8, 2025, 2:58pm UTC](https://community.exalate.com/t/salesforce-azure-devops-comments-synchronization/7561 "2025-12-08T14:58:17Z")
Salesforce ↔ Azure DevOps: Comments Synchronization Description Platforms: Salesforce to Azure DevOps, and vice-versa Summary: This guide explains how to synchronise comments between Salesforce and Azure DevOps using E… --- ## [Azure DevOps \<\> Jira Cloud Keep Issue hierarchy](https://community.exalate.com/t/azure-devops-jira-cloud-keep-issue-hierarchy/5801)
**Author:** [@francis](https://community.exalate.com/u/francis)\ **Replies:** 0\ **Last updated:** [November 17, 2024, 2:09pm UTC](https://community.exalate.com/t/azure-devops-jira-cloud-keep-issue-hierarchy/5801 "2024-11-17T14:09:03Z")
Epic → Feature → Story, Task → Sub-task In this documentation, I will show you how to keep the Epic link and issue link between issues and work items in Jira Cloud and Azure DevOps Depending on your instance you can use… --- ## [Jira Cloud Azure DevOps: Bi-directional hierarchy sync](https://community.exalate.com/t/jira-cloud-azure-devops-bi-directional-hierarchy-sync/5826)
**Author:** [@Dhiren](https://community.exalate.com/u/Dhiren)\ **Replies:** 0\ **Last updated:** [November 19, 2024, 6:32am UTC](https://community.exalate.com/t/jira-cloud-azure-devops-bi-directional-hierarchy-sync/5826 "2024-11-19T06:32:52Z")
Recently a client approached us with a very specific requirement of syncing their Epic-Story relationship from Jira Cloud to the Feature-Task relationship in Azure DevOps i.e. Epic (Jira) becomes a Feature (ADO). Stor… --- ## [Jira Cloud Jira OnPrem: Full Agile Synchronization](https://community.exalate.com/t/jira-cloud-jira-onprem-full-agile-synchronization/5828)
**Author:** [@Dhiren](https://community.exalate.com/u/Dhiren)\ **Replies:** 0\ **Last updated:** [November 19, 2024, 6:48am UTC](https://community.exalate.com/t/jira-cloud-jira-onprem-full-agile-synchronization/5828 "2024-11-19T06:48:41Z")
This use case is very often encountered when companies need to collaborate on a certain project but would prefer to continue to use their own systems. Exalate can bridge the gap by syncing all the agile objects and maint… --- ## [Jira Cloud Jira OnPrem: Syncing User Mentions across the systems](https://community.exalate.com/t/jira-cloud-jira-onprem-syncing-user-mentions-across-the-systems/5976)
**Author:** [@Dhiren](https://community.exalate.com/u/Dhiren)\ **Replies:** 0\ **Last updated:** [November 20, 2024, 6:57pm UTC](https://community.exalate.com/t/jira-cloud-jira-onprem-syncing-user-mentions-across-the-systems/5976 "2024-11-20T18:57:23Z")
When you are synchronizing two different systems, there is always a challenge of both systems having its own nuances that the integration needs to deal with. Considering this particular example of Jira OnPrem and Jira Cl…