Page History
...
For now, these Information Systems projects will keep on using their current of way of working. With time and proper preparation, they will migrate into YIS.
CAB and ET will be phased out completely, with the Jira project closing once the process is changed. The B2B and B2C projects will be integrated into YIS project.
...
These projects will continue to fulfil an Information Systems function separate to YIS:
| Project | Key | Project lead |
|---|---|---|
| Internal Audit | IA | René van der Pal |
| Yamaha Applications Support Desk | SD | Jira administrator |
| Yamaha Motor Next Stage Project | EUYNS | Kees Trommel |
| Yamaha Portfolio Board | YPM | René van der Pal |
These are business projects, and will also remain separate from YIS:
| Project | Key | Project lead |
|---|---|---|
| YME P&A Customer Support | PACS | Ingrid de Vries-Bogers |
| YMES Corporate | YMESC | Eva Bonilla Parra |
2. Jira YIS for Agile software development
...
A PO board follows Epics across the board in a Kanban flow, using the YIS Epic statusses:
4. More complex Jira features
4.1 Jira SD-> B2C-Incident ticket creation
As discussed with Patrick a new functionality in Jira SD project has been created for B2C.
If a SD ticket is in progress a linked B2C-Incident ticket can now be created via Workflow-Create B2C-Incident button.
This means that CAB can now be skipped for Incidents/Bugs.
This option is only available for Consumer Applications team, not for Epam.
With this option many fields will be copied, like previously was done for CAB.
See below fields that will be copied/set:
Unfortunately it is not possible to copy all comments, but last comment and the comment entered in the comment screen that pops up if this transition is used will both be copied to the new B2C incident.
4.2 Manage versions
A new plugin has been installed called Version Manager for Jira. With the installation of this plugin, rights for all version managers have been limited to this specific functionality without the need for administer Jira-project permission.
Jira Projects are currently only configured by Jira Admins and not by specific Project Admins.
Users with "Manage Versions" permission will now see an additional item in the project sidebar 
.
This new item provides a user interface to create, edit, order, delete, release and archive versions for this project.
Versions set via Manage versions can be selected via drop-down fields 'Fix For Version' and 'Affects Version'.
Please find on the following link instructions for How to-Manage Versions and the Naming convention.
Overview
Content Tools