Why should you use exalate to setup cross company issue tracking processes

1. Cross company issue tracking
www.exalate.com
info@exalate.com

2. Raise issues on one issue tracker,
Resolve them on the next

3. Link external facing JIRA with multiple internal trackers

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

5. Connect with your
customers, suppliers and
partners.
Enable cross company issue
tracking processes

6. Benefits of connected Issues
Business Orchestration requires Issue Orchestration
Unified Workflow
Cross-system issue
integrity
Unified View
Identify bottlenecks
Measure & Improve
Managed Security
Each party defines
what is private
or shared

7. Straight-forward connection based licensing

8. Features

9. Full non-blocking bi-directional JIRA 2 JIRA Synchronisation
Support any field, comments, attachments, work logs …

10. Flexible groovy based script mapping

11. Robust synchronisation engine ensures all changes are
synchronized

12. Know that the synchronisation succeeded

13. Build real business orchestration solutions

14. Synchronise work logs - Keep track of outsourced budgets

15. Easy migration allowing to connect existing issues

16. Implement complex mappings

17. Map multiple projects and issue types on the fly

18. Map status changes to comments (and the
way around)

19. JQL Functions to find all issues ‘under sync’

20. Get notified in case of synchronisation errors

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

22. Top notch support from iDalko
Review taken from the table grid editor