Cross company issue tracking slides
Download as PPTX, PDF0 likes146 views
The document discusses an issue tracking synchronization solution by Idalko, highlighting its flexibility, autonomy, and reliability in syncing various platforms using scripting capabilities. It emphasizes ease of integration into workflows, transaction-based operations, and the availability of extensive documentation and support for users. Various use cases, including synchronization between service desks and software projects, are also mentioned, demonstrating the solution's adaptability to different scenarios.
Cross company issue tracking slides
- 3. Sync anything to anything
- 4. • Operation • Post Function – to integrate in the workflow • JQL for automated triggers • API
- 7. Characteristics of a good issue tracking synchronization solution FLEXIBILITY AUTONOMY RELIABILITY SUPPORT
- 8. Flexibility Look for a future proof solution
- 9. Implement almost any sync case • Status to comment • Single Service Desk project to multiple Software projects • Service Desk replication • Agile Board sync • Multi level escalation • … “As flexible as Jira Itself”
- 10. issue.customFields."Remote Assignee".value = replica.assignee ? replica.assignee.displayName + " (" + replica.assignee.email + ")" Flexibility through scripting
- 11. Future proof • Start simple with Synchronisation Templates • Add additional functionality as required thanks to the scripting capability • Exalate allows to sync anything • Scripting engine allows to access the whole Jira process space (on server) ie. Synchronisation of Insight objects • Some limitations on Jira Cloud and HP QC/ALM • New trackers coming up • ServiceNow, Sales Force, Sysaid, Autotask, …
- 12. Autonomy
- 17. Transaction based sync engine • All synchronisation operations are transaction based • Change Order is respected • Any operation can be paused and resumed whenever required • Engine supports Exalate, Unexalate, Clean-up operations
- 18. What’s the effort Months, Weeks, Days …
- 30. Workshop • 2 hours expert advice to get started with your synchronisation use case • Expected • Environment available (1 or 2 instances, addon installed and activated) • Use case described
- 32. The most flexible synchronization tool on the planet
Editor's Notes
- #2: I would like to make the case to you today for automatic synchronization between issue-trackers. More precisely what pains get created for you when you're using separated issue-trackers or task management systems. And how resolving them creates so much more efficiency and productivity in your work-process, I'll run you through a couple of different use cases relevant to you. And show you exactly how synchronization will solve these problems. And of course, we'll also run you through a demo of exactly how to synchronize multiple issue-trackers. *Suggestions & notes Stefaan: I would like to make the case to you today for automatic synchronization between issue-trackers. More precisely, what pains get created for you when you're using separated issue-trackers or task management systems. Some of these pains you’ll be “painfully” aware of and others you might not have been conscious of, but nonetheless have been causing you a ton of head-aches. We’ll discuss how resolving them creates so much more efficiency and productivity in your work-process, I'll run you through a couple of different use cases relevant to you. And show you exactly how synchronization will solve these problems and save you tons of time in the process. And if you stick around to the end, we'll run you through a live example of exactly how you can synchronize multiple issue-trackers.