Francis Martens@idalkotools

Issue Clutter = Business Clutter

Multiple Entries

Time consumingError prone

Costly

Multiple Views

No single source of the truth means

hard to manage

Multiple Systems

Security concernsComplex for users

Expensive integration

Disconnected Issues

my place or

your place ?

Connected Issues

Business Orchestration requires Issue Orchestration

Unified Workflow

Cross-system issue integrity

Unified View

Identify bottlenecksMeasure & Improve

Managed Security

Each party defines what is private

or shared

2011 - SMTP based solution• Unidirectional synchronisation solution

– Event listener on site A sends a mail to site B (ScriptRunner)– JEMH on site B processes the mail and incorporate changes in the

solution• Conclusion

– + Simple communication model (everybody is sending emails)– + Straightforward implementation (couple of days)– - Email is not to be trusted (mails are dropped or out of sync)– - Difficult to expand

2013 – Custom Solution• Message bus based• Brittle to changes on either

end• Hardcoded logic• Hard to get agreement

– 7 meetings to agree on an orchestrated workflow

Questions to ask your vendor• How flexible is it ?• Is it complex to setup a complex synchronisation ?• How long does it take to synchronise an issue ?• What error resolution strategies does it offer ?• Is the sync status made visible ?• Is it forward compatible ?• What do you do in case of a DR scenario ?• How good is your support ?

Full non-blocking bi-directional JIRA 2 JIRA Synchronisation

Support any field, comments, attachments, work logs …

Link external facing JIRA with multiple internal trackers

Consolidate issue data from multiple team JIRA’s onto the master JIRA

Synchronise work logs - Keep track of outsourced budgets

Build real business orchestration solutions

Easy migration allowing to connect existing issues

Flexible groovy based script mapping

Implement complex mappings

Map multiple projects and issue types on the fly

Map status changes to comments (and the way around)

See if issue changes are properly synchronised.

JQL Functions to find all issues ‘under sync’

Advanced event based system ensures that all changes are captured in proper sequence.

Get notified in case of synchronisation errors

Error resolution subsystem allows to resume synchronisation from where it stopped.

Single-side connection based licensing

Support ****

Review taken from the table grid editor