Never worked with Jira before? No problem. In this chapter we cover some of the basics, so you know how to get started.
Data inside Jira is organised in 'projects'. A project is a collection of items that relate to the same topic.
YME uses Jira mostly for IT work. As such, you can see that most projects relate to specific applications, for example for B2B or B2C.
Three projects are different, and relate to the future YME way of working:
The data within projects can be filtered and visualised per team, in specific team boards. There are two flavours available: Scrum boards and Kanban boards.
Scrum board
In the Agile Scrum framework, focus lies on short iterations of work: planning what can be done (at YME) within 2 weeks of time.
Kanban board
There are different issue-types in Jira. Let's have a look how to recognise these, and what to use each for.
The easiest way to look at issues is on a team board, but it's also possible to Search or use Dashboards. These will be explained in the more advanced topics below.
When closing an item, you are often prompted to fill in the mandatory field for Fix/Version.
Jira fundamentals (free, self-paced, 90 minutes, certification option)
Jira beginner's guide to Agile (free, self-paced, 90 minutes, certification option)
Upon request of PMO team a multi select field Yamaha team(s) for Issue type Programme and Project has been created.
This field replaces the old Team Yamaha field for these two Issues types. If assistance for a bulk update is required, please contact a Jira Administrator.
The Yamaha Team single select field is only needed to be filled for the creation of Deliverables or an Enhancement ticket.
Team(s) can be selected via a drop down menu and pressing CTRL to select multiple teams.
When no values are set, select the edit button to add field values.
Upon request of Architect Working Group A User Picker field for Responsible Architect has been setup.
This field will be used by the Architect Working Group to select the Responsible Architect for Programme and Project.
When no value is set, select the edit button.
This field works similar as the Assignee field. When you start typing, suggestions will be made of matching users. Select the user to confirm your choice.
When set it will appear in the people section on the right hand side:
New field SD Classification has been created. This field replaces the current EPIC’s used in Servicedesk.
Problem with the current epics is that these are having to many linked issues and as result these cannot being opened anymore or transitioned through the workflow.
The old values will be set for all tickets to the new field and when done below epics will be closed.
! This change has effect on (Dashboard) filters and boards. Please check your personal filters and change the selection of the epics to the new field SD Classification value.
