...
Note: You need the required permissions to delete requests. Deleting a request is irreversible.
Anchor | ||||
---|---|---|---|---|
|
There are several search options in Jira which can help if your are looking for an issue.
...
The flag for an issue is stored in a custom checkbox field named "Flagged", which has only one value: Impediment.
This means that you can use this JQL query to find flagged issues: Flagged = Impediment
...
A board displays your team's work as cards you can move between columns. You can see a team board as the colored glasses through which we look at project data - we can customize a board to show the exact data you want to see.
The data within projects are visible on this board and can be filtered and visualized per team.
In Jira Software, cards and the tasks they represent are called “issues”. Usually, your board reflects your team's process, tracking the status of work as it makes its way through your team's process.
There are two types of boards available:
Boards can be accessed via the Boards - View all boards in the top Navigation Bar.
All recent opened boards can be found in the Recent Boards list.
On the project sidebar you have the following options: Backlog, Active sprints, or Reports.
The Backlog of a Scrum board shows the issues for your project(s) grouped into a backlog and sprints. In the Scrum backlog, you can create and update issues, drag and drop issues to rank them, or assign them to sprints, epics, or versions, manage epics, and more. You would typically use the Scrum backlog when building a backlog of issues, planning a new version, and planning a sprint.
The Active sprints of a Scrum board displays the issues that your team is currently working on. You can create and update issues, and drag and drop issues to transition them through a workflow.
Reporting is an activity that you will be doing throughout a project. Jira Software has a range of reports that you can use to show information about your project, versions, epics, sprints, and issues.
In the Agile Scrum framework, focus lies on short iterations of work: planning what can be done within (at YME) 2 weeks of time.
The Kanban board is a board that was created using the "Kanban" preset .
Kanban is based on the continuous delivery of work. Rather than plan iterations, the flow of work is constantly monitored to ensure that there are always tasks being worked on. This means that when tasks are completed, new tasks are pulled into work-in-progress.
Use the Kanban board if your team focuses on managing and constraining work-in-progress.
On the project sidebar you have the following options: Kanban board, Backlog*, or Reports.
By default, Kanban boards have the Backlog column, where you plan work for your team. Planning work in a small column becomes difficult as more issues are added in the column.
By enabling and using the Kanban backlog, you have a bigger space to create and rank issues, and select issues for your team to start working on.
Reporting is an activity that you will be doing throughout a project. Jira Software has a range of reports that you can use to show information about your project, versions, epics, sprints, and issues.
In the Agile Kanban framework, focus lies on limiting multi-tasking: by choosing fewer items to start, it's possible to complete each more quickly.
If you wish to stop your DONE column from overflowing, there are two methods to limit it in time:
Your board admin can make either of these settings for you.
At the top of a team board you usually find Quick Filters. These are specifically designed for your team board.
By clicking one of these Quick Filters, you narrow the board filter, hiding some or many items to fit the Quick Filter criterion. Deactivate it by clicking it a second time.
It's possible to select multiple Quick Filters, narrowing your selection of items on the board further and further.
Your team board administrator can maintain Quick Filters for you: change them, or add new ones.
Whether you're working on a Scrum or Kanban board, you can click on any issue to view it in more detail.
Displayed Issue details are configured and customizable by your Board Administrator.
You can flag an issue to indicate that it's important, set it as impediment.
The card of a flagged issue is displayed in yellow in the Scrum backlog, Active Sprint of a Scrum board , Kanban backlog (if enabled) and, with the 'flag' icon replacing the priority icon.
You can also add a comment when you're adding a flag to or removing a flag from an issue. You may want to do this to indicate your reason for adding or removing the flag.
In the Issue Detail View, select Add flag and comment or Remove flag and add comment from the 'cog' drop-down. You can also right-click on the issue > Add flag and comment or Remove flag and add comment. After adding your comment, it will appear in the Comments section of the issue, with an indication that a flag was added or removed accordingly.
You must be a Jira administrator or a Board administrator for the board to modify its configuration. Any board user is able to view the board configuration.
Go to the desired board and select Board > Configure.
On the Board Configuration screen, select the desired tab (Columns, Swimlanes, etc).
...
Versions are points-in-time for a project. They help you schedule and organize your releases.
Once a version is created and issues are assigned to it, you can use several reports, e.g. the Change Log report, when managing the version.
The Change Log report, in particular, gives you a review of the released version, and is driven by the 'Fix For Version' field on each issue.
Versions can only be managed when you have Project administrator or Jira Admin permission including Edit issue permission.
At YME we use an Addon for Version management called Version manager so users without Project administrator or Jira administrator permissions can also use this functionality.
Versions set via Manage versions can be selected via drop-down fields 'Fix Version/s' and 'Affects Version'.
Choose Manage Versions in the left menu. The Versions page is displayed, showing a list of versions and each version's status. From here you can manage the project's versions as described on this page.
From here you can manage the project's versions as described on following Atlassian page Managing Versions .
A version is a set of features and fixes released together as a single update to your product. By default, Kanban boards do not require issues to be pre-assigned to versions. This is because Kanban is designed for a continuous flow of work, rather than set iterations.
On a Kanban board, you can choose to release a version at any point in time — the version will contain all issues that are complete at that time. You also specify the name of a new version at the time of the release.
For information on how to release a version on a Kanban board, see Deploying a release.
If your team is using the Kanban backlog for your Kanban project, you can use the Versions panel to manage versions.
Click Backlog. If the Versions panel is not showing, click VERSIONS on the left side of the board (aligned vertically) to open it.
Add a new version | Click Create version (you will need to hover over the 'VERSIONS' panel to show this link), enter the version details, and create it. * The Start Date is used to give you a more accurate Version Report in cases where you might plan a version many weeks or even months in advance, but not actually commence work until closer to the release date. * The End Date is used to calculate the days remaining in a release on the Release Hub. |
---|---|
Update a version's details | For the version name, click the arrow next to the name, then choose Edit name. For other fields (e.g. Description), click the field to edit it. |
Add an issue to a version | Drag and drop the issue onto the version in the 'VERSIONS' panel. |
Remove an issue from a version | Drag and drop the issue onto Issues without versions in the 'VERSIONS' panel. |
Filter issues by version | Click the version in the 'VERSIONS' panel to show only issues in that version. Click All issues to remove the filter. Alternatively, click Clear all filters next to the column's name. |
Screenshot: viewing versions in the Backlog
You can use the JQL fixVersion field to search for a version's issues — see Search for details.
A version is a set of features and fixes released together as a single update to your application. Assigning issues to versions helps you plan the order in which new features (stories) for your application will be released to your customers.
In Jira Software, you can view your issues according to which version they belong to. You can also drag-and-drop issues into a version to assign them to it, which you should do before you start work on the issues. This helps you plan your upcoming versions, which may span multiple sprints.
Go to the Backlog of your Scrum project.
Click VERSIONS on the left side of the board (aligned vertically) to open it.
Add a new version | Click Create version (you will need to hover over the 'VERSIONS' panel to show this link), enter the version details, and create it. * The Start Date is used to give you a more accurate Version Report in cases where you might plan a version many weeks or even months in advance, but not actually commence work until closer to the release date. * The End Date is used to calculate the days remaining in a release on the Release Hub. |
---|---|
Update a version's details | For the version name, click the arrow next to the name, then choose Edit name. For other fields (e.g. Description), click the field to edit it. |
Add an issue to a version | Drag and drop the issue onto the version in the 'VERSIONS' panel. |
Remove an issue from a version | Drag and drop the issue onto Issues without versions in the 'VERSIONS' panel. |
Filter issues by version | Click the version in the 'VERSIONS' panel to show only issues in that version. Click All issues to remove the filter. Alternatively, click Clear all filters next to the column's name. |
You can use the JQL fixVersion field to search for a version's issues — see Search for details.
A board displays your team's work as cards you can move between columns. You can see a team board as the colored glasses through which we look at project data - we can customize a board to show the exact data you want to see.
The data within projects are visible on this board and can be filtered and visualized per team.
In Jira Software, cards and the tasks they represent are called “issues”. Usually, your board reflects your team's process, tracking the status of work as it makes its way through your team's process.
There are two types of boards available:
Boards can be accessed via the Boards - View all boards in the top Navigation Bar.
All recent opened boards can be found in the Recent Boards list.
On the project sidebar you have the following options: Backlog, Active sprints, or Reports.
The Backlog of a Scrum board shows the issues for your project(s) grouped into a backlog and sprints. In the Scrum backlog, you can create and update issues, drag and drop issues to rank them, or assign them to sprints, epics, or versions, manage epics, and more. You would typically use the Scrum backlog when building a backlog of issues, planning a new version, and planning a sprint.
The Active sprints of a Scrum board displays the issues that your team is currently working on. You can create and update issues, and drag and drop issues to transition them through a workflow.
Reporting is an activity that you will be doing throughout a project. Jira Software has a range of reports that you can use to show information about your project, versions, epics, sprints, and issues.
In the Agile Scrum framework, focus lies on short iterations of work: planning what can be done within (at YME) 2 weeks of time.
The Kanban board is a board that was created using the "Kanban" preset .
Kanban is based on the continuous delivery of work. Rather than plan iterations, the flow of work is constantly monitored to ensure that there are always tasks being worked on. This means that when tasks are completed, new tasks are pulled into work-in-progress.
Use the Kanban board if your team focuses on managing and constraining work-in-progress.
On the project sidebar you have the following options: Kanban board, Backlog*, or Reports.
By default, Kanban boards have the Backlog column, where you plan work for your team. Planning work in a small column becomes difficult as more issues are added in the column.
By enabling and using the Kanban backlog, you have a bigger space to create and rank issues, and select issues for your team to start working on.
Reporting is an activity that you will be doing throughout a project. Jira Software has a range of reports that you can use to show information about your project, versions, epics, sprints, and issues.
In the Agile Kanban framework, focus lies on limiting multi-tasking: by choosing fewer items to start, it's possible to complete each more quickly.
If you wish to stop your DONE column from overflowing, there are two methods to limit it in time:
Your board admin can make either of these settings for you.
At the top of a team board you usually find Quick Filters. These are specifically designed for your team board.
By clicking one of these Quick Filters, you narrow the board filter, hiding some or many items to fit the Quick Filter criterion. Deactivate it by clicking it a second time.
It's possible to select multiple Quick Filters, narrowing your selection of items on the board further and further.
Your team board administrator can maintain Quick Filters for you: change them, or add new ones.
Whether you're working on a Scrum or Kanban board, you can click on any issue to view it in more detail.
Displayed Issue details are configured and customizable by your Board Administrator.
You can flag an issue to indicate that it's important, set it as impediment.
The card of a flagged issue is displayed in yellow in the Scrum backlog, Active Sprint of a Scrum board , Kanban backlog (if enabled) and, with the 'flag' icon replacing the priority icon.
You can also add a comment when you're adding a flag to or removing a flag from an issue. You may want to do this to indicate your reason for adding or removing the flag.
In the Issue Detail View, select Add flag and comment or Remove flag and add comment from the 'cog' drop-down. You can also right-click on the issue > Add flag and comment or Remove flag and add comment. After adding your comment, it will appear in the Comments section of the issue, with an indication that a flag was added or removed accordingly.
You must be a Jira administrator or a Board administrator for the board to modify its configuration. Any board user is able to view the board configuration.
Go to the desired board and select Board > Configure.
On the Board Configuration screen, select the desired tab (Columns, Swimlanes, etc).
Instructions how to Configure a Board can be found on the following Atlassian page: Configuring a board
General: Includes Board general and filter settings. Board name and Administrator. The Board filter(s) determine which issues appear on the board. It can be based on one or more projects, or custom JQL depending on your needs.
Columns: (1) Columns can be added, removed, reordered and renamed. Columns are based upon global statuses and can be moved between columns. Minimum and maximum constraints can be set for each mapped column.
Swimlanes: (2) A swimlane is a row on the board that can be used to group issues. Swimlane type can be changed below and will be saved automatically. Note: queries will not be lost when changing to another swimlane type.
Quick Filters: (3) Quick Filters can be used to further filter the issues in the board based on the additional JQL query.
Card colors: (4)Choose a method for assigning colors to your cards. If no method is selected, the cards will not have a colored edge. Any changes to the color configuration for a method are saved immediately, so you can switch back to it later if you wish.
Card layout: (5) Cards can be configured to show up to three extra fields.
Working days: These settings allow you to highlight or exclude non-working days from reports and gadgets.
They apply to the following reports: Burndown Chart, Sprint Report, Epic Report, Version Report, Control Chart; and the following gadgets: Sprint Health Gadget, Burndown Gadget.
Issue Detail View: (6) Add, delete or reorder fields on the Issue Detail View.
Agile Tools & Filters: Backlog settings, Search bar settings
You can find your board administrator via
Under General (left panel) > Administrators you can find the name(s) of your Team Board administrator(s). They are your first point of contact if you want anything changed on your Team Board.
Jira fundamentals (free Atlassian training, self-paced, 90 minutes, certification option)
Via the help button in the main navigation bar at the top rights side you can select Keyboard Shortcuts.
Additional to the above:
Board shortcut: When you have an item selected and press "." on the keyboard, the 'more' menu pops-up, allowing you to quickly change (for example) the issue status.
Jira add-ons/plugins are software that a Jira administrator can install to improve Jira's functionality.
At Yamaha Motor Europe N.V. we have the following add-ons installed:
General apps that could be used in a Jira project or used by a Jira Admin or Project Admin
Secure Admin for Jira (Jira Admin only)
Addons specifically used by Service Management Projects:
Addons specifically used for by Software projects:
General: Includes Board general and filter settings. Board name and Administrator. The Board filter(s) determine which issues appear on the board. It can be based on one or more projects, or custom JQL depending on your needs.
Columns: (1) Columns can be added, removed, reordered and renamed. Columns are based upon global statuses and can be moved between columns. Minimum and maximum constraints can be set for each mapped column.
Swimlanes: (2) A swimlane is a row on the board that can be used to group issues. Swimlane type can be changed below and will be saved automatically. Note: queries will not be lost when changing to another swimlane type.
Quick Filters: (3) Quick Filters can be used to further filter the issues in the board based on the additional JQL query.
Card colors: (4)Choose a method for assigning colors to your cards. If no method is selected, the cards will not have a colored edge. Any changes to the color configuration for a method are saved immediately, so you can switch back to it later if you wish.
Card layout: (5) Cards can be configured to show up to three extra fields.
Working days: These settings allow you to highlight or exclude non-working days from reports and gadgets.
They apply to the following reports: Burndown Chart, Sprint Report, Epic Report, Version Report, Control Chart; and the following gadgets: Sprint Health Gadget, Burndown Gadget.
Issue Detail View: (6) Add, delete or reorder fields on the Issue Detail View.
Agile Tools & Filters: Backlog settings, Search bar settings
You can find your board administrator via
Under General (left panel) > Administrators you can find the name(s) of your Team Board administrator(s). They are your first point of contact if you want anything changed on your Team Board.
Jira fundamentals (free Atlassian training, self-paced, 90 minutes, certification option)
Via the help button in the main navigation bar at the top rights side you can select Keyboard Shortcuts.
Additional to the above:
Board shortcut: When you have an item selected and press "." on the keyboard, the 'more' menu pops-up, allowing you to quickly change (for example) the issue status.
Jira add-ons/plugins are software that a Jira administrator can install to improve Jira's functionality.
At Yamaha Motor Europe N.V. we have the following add-ons installed:
General apps that could be used in a Jira project or used by a Jira Admin or Project Admin
Secure Admin for Jira (Jira Admin only)
Addons specifically used by Service Management Projects:
...
...
JSU Automation Suite (JSU) includes additional workflow conditions, validators, preconditions, post functions and custom fields.
This addon is used by Jira Administrators and Project administrators to automate repetitive business processes and manual tasks in an easy–to–use, no-code environment within Jira Workflows.
Documentation for this addon is supplied by vendor Beecom: JSU OvervieuwOverview
ProForma allows you to quickly create user-friendly forms within Jira issues or requests. Using forms on Jira issues allows you to include all of the fields you need, without custom fields or complex configurations.
Organize fields in a way works your team, control what information is visible to whom, and include as many forms per issue/request as needed. All form data is stored securely in your Jira instance.
...
...
Secure Admin allows Jira Administrators to restrict access to the top-level admin tabs, sub tabs under any top level tab and project admin tabs.
This allows an administrator to give access to particular administration functions without giving access to all admin screens.
Features include:
This Jira addon was implemented to allow easy reporting on how long an issue has remained in a specific status.
You can use the addon in two ways. The first method is to go into the addon and fill in search criteria for the items you wish to investigate:
For example:
The second method is to look at the sidebar (on the right side of the screen). For each issue the facts regarding Time in Status are shown:
...
Because we use the Free version of this addon, it is possible that no data is shown. If this occurs, simply refresh the screen after a few minutes:
More detailed instructions for Status Time Free app is supplied by the vendor: Status Time Reports App.
Timesheets Reports and Gadges addon provides Flexible time tracking and reporting of time spent on Projects, Epics or Initiatives broken down by Days or Users, with Time Sheet and Project Pivot reports and gadgets for Jira dashboard or Confluence, Time Sheet Email, Worked Time Chart gadget, REST endpoint and workedIssues JQL function.
Instructions how to use this addon is supplied by the vendor: Prime Timesheets for Jira Server and Data Center
Instructions how to use the Time sheet and Logging Time how it is used at Yamaha can be found below:
Time Reports for Jira Server and Data Center allow you to view tracked time in different ways with multiple reports and gadgets. There are also multiple convenient ways to log your time in the reports and gadgets, as well as directly in Jira issues.
...
If a mistake has been made or a description is incomplete this can be modified in the time sheet report or under the Work Log activity.
...
Documentation is supplied by the vendor Adaptavist: ScriptRunner for Jira
Secure Admin allows Jira Administrators to restrict access to the top-level admin tabs, sub tabs under any top level tab and project admin tabs.
This allows an administrator to give access to particular administration functions without giving access to all admin screens.
Features include:
This Jira addon was implemented to allow easy reporting on how long an issue has remained in a specific status.
You can use the addon in two ways. The first method is to go into the addon and fill in search criteria for the items you wish to investigate:
For example:
The second method is to look at the sidebar (on the right side of the screen). For each issue the facts regarding Time in Status are shown:
Status Time Free app is the free and limited version of Status Time Reports app.
Status Time Free app has arate limiting of 1 request per 10 seconds for Issue Details View and 1 search per 10 seconds for Reporting. If rate limiting is hit, reporting is limited to 10 issues.
Because we use the Free version of this addon, it is possible that no data is shown. If this occurs, simply refresh the screen after a few minutes:
More detailed instructions for Status Time Free app is supplied by the vendor: Status Time Reports App.
Timesheets Reports and Gadges addon provides Flexible time tracking and reporting of time spent on Projects, Epics or Initiatives broken down by Days or Users, with Time Sheet and Project Pivot reports and gadgets for Jira dashboard or Confluence, Time Sheet Email, Worked Time Chart gadget, REST endpoint and workedIssues JQL function.
Instructions how to use this addon is supplied by the vendor: Prime Timesheets for Jira Server and Data Center
Instructions how to use the Time sheet and Logging Time how it is used at Yamaha can be found below:
Time Reports for Jira Server and Data Center allow you to view tracked time in different ways with multiple reports and gadgets. There are also multiple convenient ways to log your time in the reports and gadgets, as well as directly in Jira issues.
If a mistake has been made or a description is incomplete this can be modified in the time sheet report or under the Work Log activity.
Version manager for Jira plugin limits rights for all version managers to his 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 used by for How to-Manage Versions.
Choose Manage Versions in the left panel. The Versions page is displayed, showing a list of versions and each version's status. From here you can manage the project's versions as described on this page.
From here you can manage the project's versions as described on this page. Managing Versions
...
Version manager for Jira plugin limits rights for all version managers to his 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'.
...
Xray for Jira is a Test Management tool (app) that provides the structure to organize, plan, and report with accuracy on the progress of testing as well as the readiness to deploy.
...