...

For YNS the following two Backbone syncs are active:

• Backbone sync YNS project between Jira PWC US (YMC) (CON0000585) and Jira YME (EUYNS)

• Backbone sync between Jira YME EUYNS project and YIS project

The issues synced between both instances are limited to EU Rollout Projects only.

In short it means that any change done in Jira PWC JIRA or YME JIRA Jira YME  is synchronized to each other for agreed issues types, workstream and team.  
All YNS issues are connected and updated as soon as a change is done:  e.g. CON0000585-54579 <-> EUYNS-1546 <-> YIS-11225
In Jira YME in EUYNS project both Backbone Syncs are visible in the right panel under Backbone Issue Sync. 

Example: EUYNS-1546

...

The Yamaha-motor Next Stage Jira Project Management Policy includes information like purpose of Jira implementation, progress management and rules.
Note: This presentation explains full setup done for YNS in PWC US.  Jira YME instance YME  is limited to EU Rollout Projects information only.

...

In principle, particularly for the YME integration team (TRANSFORMERS), all work relates to specific PDD FEATURES. Under a FEATURE, the Project team will specify more specific PDDs.
In there, the YME teams involved in integration will collaborate. Collaboration with YME teams is only done in Jira YME Jira YIS project. Team information can be found under Team Procedures .

...

Issues are synced bidirectional, meaning the same data is existing in both instances.
Backbone detects each existing issue from Yamaha Motor Next Stage project (YNS) and creates a new issue with the same data in the other Jira instance. Afterwards, each change synchronizes between both issues. 

...

Jira YME: EUYNS-1546                                                                                                   Jira PWC US: CON0000585-54579

...

In Jira, the main person in charge and sub-person in charge will be assigned to each task.
All assigned persons need to exist in both Jira instances to prevent errors in Backbone Sync.

When the original issue is created in Jira PWC (CON0000585) then in Jira YME EUYNS the reporter will appear as ServiceAccountBackbone
Image Added

Backbone sync between Jira YME EUYNS project and YIS project 

Anchor
Backbone sync between Jira YME EUYNS project and YIS project Backbone sync between Jira YME EUYNS project and YIS project

...

• AVENGERS
• B2C-CDP
• B2C-DIGITALUM
• B2C-EPAM-DEVOPS
• B2C-EPAM-MOTORS
• B2C-EPAM-WAVERUNNERS
• CLOUD-RANGERS
• CRM-KANDO
• DRAGONBALL
• EU Accounting
• EU S&L (P&A)
• EU S&L (Units)
• EU S&L (WTY)
• LIGHTBEAM
• MARVELS
• QUICKSHIFTER
• TRANSFORMERS
• TRICITY
• WOLVERINE
• YAMALUBE

Fields "Reporter" and "Assignee" are not synced between EUYNS and YIS.
Reason for this is that all YME users must also exist in Jira PWC and this will cost to many licenses.

When the original issue is created in Jira PWC (CON0000585) or in Jira YME (EUYNS) the reporter will appear as ServiceAccountBackboneYIS-EUYNS

Image Added

Via the Backbone issue Sync panel at the right side you can see to which issue it has been synced in the other instance or YME project.

EUYNS-1546                                             YIS-11225   

The Backbone sync link internally via EUYNS and YIS is not working as this refers to a local host.
Please type the Issue Key number in the Search of Jira YME Jira to access this issue.
Image Added
Image Added

Big picture (project planning)

...

By adding Yamaha team as column and using JQL search Yamaha Team on name issues can easily being filtered out.
Example below for team Transformers TRANSFORMERS (Informatica implementation team)

Big Picture Configuration for administrators

Backbone Sync errors

If any Sync error appears or if you have questions why an issue is not synced between any of the Jira instances or Jira YME EUYNS-YIS project please contact a Jira Administrator.

Image Added

Sync errors will appear when an Issue type is moved to another issue type. This must always be done manually in both Jira instances and project as the (new) workflow needs to be mapped.

Common sync errors

• Issue type has been manually changed via move option in Jira PWC or Jira YME.  Please try to avoid moving issues to another issue type, instead cancel the wrongly created issue and create a new issue with the correct issue type! 
  • Action: If move is already done, perform the same Issue type move action in Jira PWC and Jira YME for all synced issues in all related Jira projects. If you do not have access to perform this action in Jira PWC and Jira YME please contact a Jira administrator.
    
    

Jira PWC CON0000585 ↔ Jira YME EUYNS

• Users in field "Assignee", "Member" or "Owner" is not known in both Jira instances 
  • Action: Contact a Jira Administrator
    
    
• Field "Workstream" is not filled 
  • Action: Add a EU Workstream value to the "Workstream" field. See synced workstreams under Backbone sync YNS project between Jira PWC US (YMC)  and Jira YME
    
    

Jira YME EUYNS ↔ Jira YME YIS

• Field "Workstream" is not filled 
  • Action: Add a EU Workstream value to the "Workstream" field.  See synced workstreams under Jira training Yamaha Motor Next Stage (EUYNS)
    
    
• Field "Client team" in EUYNS or "Yamaha Team" is not filled 
  • Action: Add a value to the "Client Team or Yamaha Team" field. See synced team names under Jira training Yamaha Motor Next Stage (EUYNS)