...
The issues synced between both instances are limited to EU Rollout Projects only.
In short it means that any change done in PWC JIRA or YME JIRA 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.
Example: EUYNS-1546
Visual overview Backbone Sync PWC and YME
draw.io Diagram | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Loading of the presentation will take a while, please download the presentation to view the slides.
View file | ||||
---|---|---|---|---|
|
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 YME Jira YIS project.
Hereunder, also naming convention is mentioned for PDD, epics etc.
...
Via the Backbone issue Sync panel at the left side you can see to which issue it has been synced in the other instance.
Jira YME: EUYNS-613 1546 Jira Jira PWC US: CON0000585-4638154579
Jira issue synchronization between PWC US and YME only supports specific issue types:
...
Software Development within YME is done in project Yamaha IS Projects (YIS). YIS Documentation can be found on the following page: Jira training for Yamaha IS Projects (YIS).
Yamaha Motor Next Stage project (YNS) related issues between EUYNS and YIS are synced bidirectional, meaning the same data is existing in both YME Jira projects.
Backbone sync detects each existing issue from any of the two projects and creates a new issue with the same data in the other Jira Project. Afterwards, each change synchronizes between both issues.
As only work for Yamaha (scrum) teams should be visible in YIS the sync between EUYNS and YIS is limited on the following field values which are mandatory to be filled:
...
Below detailed field values are included in the sync:
Issue Types
EUYNS | <-> | YIS |
---|---|---|
EPIC | <-> | EPIC |
STORY | <-> | STORY |
TASK | <-> | TASK |
SUB-TASK | <-> | SUB-TASK |
DEFECT | <-> | BUG |
Workstreams
...
Via the Backbone issue Sync panel at the left side you can see to which issue it has been synced in the other instance or YME project.If any error occur this will be visible in the Backbone troubleshooting section of the addons configuration which is monitored by Jira Administrators at YME Instance. In case questions about a issue error sync please reach out to a Jira Administrator.
Software Development within YME is done in project Yamaha IS Projects (YIS). Documentation can be found on the following page: Jira training for Yamaha IS Projects (YIS).
To monitor the progress for software development for SAP and Informatica related to the Yamaha Next Stage (YNS) project is
...
In YIS the following relation of issue types is used:
Epic will be created per interface and these will be linked to EUYNS project to track progress.
Stories will be used for the design and development
Sub-tasks can be created under the Story to break down the work done.
After creation of a YIS EPIC open the issue and create 3 Issue links via +
Issue Link screen will open:
Make the following selection in the screen:1. This issue: select one of the tree below:
2. Issue: select Issue Key EUYNS Epic
3. Press Link to confirm
...
EUYNS-1546 YIS-11225
The link internally via EUYNS and YIS is not working this refers to a local host.
Please type the Issue Key number in the Search of YME Jira to access this issue
When opening it will look as follow:
This epic link will reflect in Big Picture which is used by YME Management for project planning and managing.
...