Bridging the Gap - B2B Integration for JIRA at Atlassian User Group München 2014

B2BCollaboration

Dev Team

* Projects * Workflows

Dev Team

Product Team

* Permission Schemes * Issue Level Security

Dev Team

Product Team

Entire Company* Field Level Security * Component Level Security

Dev Team

Product Team

Entire Company

Your Partner

Your Company

Your Product TeamYour Partner

Your JIRA

Your Partner

Your JIRA

B2BCollaboration

Your Partner

Your JIRA

Provide Access to Your System* Talking about the same things ? … YES * Working in your own system? … YES / NO

* Introduce Project Roles * Adapt all kind of Security Schemes * Adapt Workflows

Your PartnerYour Company

Share the same Project

* Talking about the same things ? … YES * Working in your own system? … NO

* Maintain privacy and security

/ Hosted

Your JIRA Your Partner

Working in two JIRAs - Manual Replication

* Talking about the same things ? … NO not at the same time * Working in your own system? … YES * Saving time and money? … NO

BUT a lot of companies work like that

* Talking about the same things * Maintain Privacy and Security * Painless Communication * Ready for BTF and On-Demand UseCases

Working in two JIRAs - Requirements

* Bi-directional integration * Define what information qualify for sync (JQL) * What data should be exchanged

* Fields * Attachments * Comment * Workflow status

* Define sync direction * Distributed workflow management * Automatic conflict resolution

Working in two JIRAs - Requirements

Backbone B2B Integration for JIRA

Working in two JIRAs - Backbone for JIRA

REST

Working in two JIRAs - Backbone for JIRA

REST

REST

Working in two JIRAs - Backbone for JIRA

REST REST

Working in two JIRAs - Backbone for JIRA

REST REST

FILE

Working in two JIRAs - Backbone for JIRA

Company A Company B Company C

REST

RESTFILE

DEMO

Get in touch with us contact@k15t.com @k15tsoftware www.k15t.com today - Eugen or Tobias