+ All Categories
Home > Software > Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

Date post: 11-Feb-2017
Category:
Upload: k15t-software-gmbh
View: 249 times
Download: 0 times
Share this document with a friend
41
BRIDGING THE GAP: TEAM COLLABORATION IN JIRA with Backbone - Issue Sync for JIRA
Transcript
Page 1: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

BRIDGING THE GAP: TEAM COLLABORATION IN JIRA with Backbone - Issue Sync for JIRA

Page 2: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

Atlassian Expertise Since 2002!

Hello my name is Matthias

Page 3: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA
Page 4: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA
Page 5: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA
Page 6: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA
Page 7: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

IT-Team

Software-Team

Business-Team

Page 8: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

External-Team

Page 9: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

BRIDGING THE GAP: TEAM COLLABORATION IN JIRA with Backbone - Issue Sync for JIRA

Page 10: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

External-Team

Page 11: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

#1 Provide Access To JIRA

Page 12: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

#2 Use a Shared Cloud Instance

Page 13: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

#3 Manual Replication

Page 14: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

a lot of companies work like that Believe it or not

Page 15: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

#4 Synchronization

Page 16: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

On the Same PageComplete Control

Workflows Without BordersTrusted and Proven

Fast Liftoff

Page 17: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

Bi-Directional IntegrationWhat to Sync - Define JQL

Issue Types and FieldsComments and Attachments

Distributed Workflow

Page 18: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

JIRA-TO-JIRA INTEGRATION

JIRA SERVICE DESK SCENARIO

PUBLIC-PRIVATE SYSTEM SCENARIO

SUPPLIER / OUTSOURCING SCENARIO

Page 19: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA
Page 20: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

Business-Team

Customer

IT-Team

Agents

Developer-Team

Collaborators

Page 21: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

IT-Team Developer-Team

Agents

Business-Team

Customer Collaborators

Page 22: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

IT-Team Developer-Team

Agents

COLLABORATION GAP

Different Requirements> Workflows > Fields > Custom JIRA Project

Linked Issues

Collaborators

Page 23: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

IT-Team Developer-Team

Agents

COLLABORATION GAP

Deployment> Public vs. Private installation

Outsourcing > 2nd and 3rd level

Collaborators

Page 24: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

BRIDGING THE GAP: TEAM COLLABORATION IN JIRA with Backbone - Issue Sync for JIRA

Page 25: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA
Page 26: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

CollaboratorsAgents

On the Same PageComplete Control

Workflows Without BordersTrusted and Proven

Fast Liftoff

Page 27: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

Bi-Directional IntegrationWhat to Sync - Define JQL

Issue Types and FieldsComments and Attachments

Distributed Workflow

CollaboratorsAgents

Page 28: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

JIRA-TO-JIRA INTEGRATION

JIRA SERVICE DESK SCENARIO

PUBLIC-PRIVATE SYSTEM SCENARIO

SUPPLIER / OUTSOURCING SCENARIO

CollaboratorsAgents

Page 29: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

Business-Team IT-Team Developer-Team

Customer Agents Collaborators

Page 30: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

Technical Details

Page 31: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

JIRA

DEVELOPED IN AN ENTERPRISE PROJECT

JIRA

Page 32: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

JIRA COMPATIBILITY BY DESIGN

JIRA REST API

JIRA REST API

2.0

v6.2 v7.x

Page 33: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

READY FOR CLOUD

JIRA REST API

CloudLATEST

JIRA REST APIv6.2

2.1

Page 34: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

READY FOR ENTERPRISE

JIRA REST API

v6.2 v7.x

JIRA REST API

E-Mail

2.soon

Page 35: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

BACKBONE SERVER

JIRA REST API

v6.x

Page 36: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

Roadmap

Page 37: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

2.0

JIRA-to- JIRA (Server -to- Server)

JIRA ServiceDesk -to- JIRA (Server -to- Server)

Issue Type MappingsField Mappings

Workflow MappingsComments

Attachments

Page 38: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

2.1

JIRA-to- JIRA (Server -to- Cloud)

JIRA ServiceDesk -to- JIRA (Server -to- Cloud)

Page 39: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

2.2

Attachment Filters Copy Integrations

Page 40: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

2.soon

Distributed Configuration (E-Mail Binding) Fine grained Permission Checking

Trusted Comments (user impersonation) K15t Licensing Scheme

Page 41: Bridging the Gap: Team Collaboration with Backbone – Issue Sync for JIRA

Atlassian Expertise Since [email protected]


Recommended