...

Yamaha Motor Next Stage Projects (YNS) has been setup as supporting platform to check the progress between YMC and PwC at the same time in the YNS project.
By managing the project in Jira the progress is visualized and can be used for managing the relationship of tasks across teams, the relationships between stakeholders can be strengthened and appropriate methods can be considered within the YNS project.Jira PWC US is selected as source project from where all action items, development activities are recorded and distributed (synced) to Jira YME .
YME will maintain all work done for all EU rollout Project in YME Jira.

YME documentation related to YNS for SAP and Informatica and Team Procedures is stored under Confluence Space IF.

...

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

In short it means that any change done in Jira PWC US or Jira YME is synchronized to each other for agreed issues types , workstream and team. and workstream.
To trigger a issue to be synced with Jira YME YIS also the team field cannot be empty.

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 EUYNS project both Backbone Syncs are visible in the right panel under Backbone Issue Sync.

Example: EUYNS-1546

...

draw.io Diagram

border	true

diagramName	Jira backbone Sync YMC-YME-YME SCRUM
simpleViewer	false
width
links	auto
tbstyle	top
lbox	true
diagramWidth	886
revision	1113

*All agreed issue types

Yamaha Next Stage (YNS) Jira Project Management Policy

...

Backbone sync YNS project between Jira PWC US (YMC) and Jira YME
Anchor
Backbone sync YNS project between Jira PWC US (YMC) and Jira YME
Backbone sync YNS project between Jira PWC US (YMC) and Jira YME

The Jira Project name and configuration in both instances is similar: Yamaha Motor Next Stage project (YNS)

Only the project key differs:
PWC US: CON000585
Jira YME: EUYNS

Issues for EU Rollout Projects workstreams 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.

Reporter

Reporter is a mandatory field in Jira and is automatically filled when an issue is created.
As issues will be created by Backbone Sync this will be displayed as reporter in the synced issues.
Only in the Jira project where the issue originally has been created the original reporter (user) will be visible.

See below overview of the reporter set when Backbone sync is triggered for issue creation:

Issue created in Jira PWC CON0000585, reporter in Jira PWC CON0000585: Original reporter
Issue created in Jira PWC CON0000585, reporter in synced issue Jira YME EUYNS: ServiceAccountBackBone
Issue created in Jira PWC CON0000585, reporter in synced issue Jira YME YIS: ServiceAccountBackBoneYIS-EUYNS
Issue created in Jira YME EUYNS, reporter in Jira YME EUYNS: Original reporter
Issue created in Jira YME EUYNS, reporter in synced issue Jira PWC CON0000585: YNC Sync User
Issue created in Jira YME EUYNS, reporter in synced issue Jira YME YIS: ServiceAccountBackBoneYIS-EUYNS
Issue created in Jira YME YIS, reporter in synced issue Jira PWC CON0000585: YNC Sync User
Issue created in Jira YME YIS, reporter in synced issue Jira YME EUYNS: ServiceAccountBackBoneYIS-EUYNS

Image Added
Image Added
Image Added

Backbone Issue Sync panel

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

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

Synced Field values Jira PWC and Jira YME

Issue sync between Jira PWC and Jira YME is triggered based on the values in the following fields:

Issue type
Workstream

Issue Types

Jira issue synchronization between Jira PWC and Jira issue synchronization between PWC US and YME only supports specific issue types:

Action Items (stand alone tasks)
Tasks (originating from PROJECT/EPIC)
Sub-Task (originating from task)
Issues (originating from EPIC)
Risks (originating from EPIC)
EPICS (Project)
FEATURES (Project)
Decision (Project)
Story (originating from EPIC)
Defect (originating from EPIC)

Workstream

The issues synced between both Jira instances are limited to EU Rollout Projects workstreams only.
The “workstream” “Workstream” field in YNS Jira is used to distinguish which project the items are linked to and is mandatory to be filled for syncing an issue between Jira PWC and Jira YME.
All related EU Rollout Projects in YNS Jira can be found under the following workstreams:

EU Accounting
EU Master Data
EU Project Management
EU Rollout (Gr1_Ph1)
EU S&L
EU S&L (P&A)
EU S&L (Units)
EU S&L (WTY)
EU Technical Support

Field "Dependent Workstream" is also synced but is not mandatory for having an issue synced between Jira PWC and Jira YME.

Yamaha Motor Next Stage project (EUYNS)

...

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 Removed

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

...

Issue type
Workstream
Team (Client team/Yamaha Team)

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.