Jira 简明教程

JIRA - Quick Guide

JIRA - Overview

JIRA 是用于项目管理、错误跟踪、问题跟踪和工作流的 Incident Management Tool 。JIRA 基于以下三个概念 - 项目、问题和工作流。

JIRA is an Incident Management Tool used for Project Management, Bug Tracking, Issue Tracking and Workflow. JIRA is based on the following three concepts – Project, Issue and Workflow.

Important Points to Note

以下要点解释了 JIRA 的一些有趣细节。

The following points explain some interesting details of JIRA.

JIRA is an incident management tool.
JIRA is developed by Atlassian Inc., an Australian Company.
JIRA is a platform independent tool; it can be used with any OS.
JIRA is multi-lingual tool − English, French, German, Japanese, Spanish, etc.
JIRA supports MySQL, Oracle, PostgreSQL and SQL server in the backend.
JIRA can be integrated with many other tools − Subversion, GIT, Clearcase, Team Foundation Software, Mercury, Concurrent Version System and many more.

License and Free Trial

以下几点说明了 JIRA 工具的合法性。

The following points describes the legalities of the JIRA Tool.

JIRA is a commercial tool and available as a Trial version for a limited time.
To utilize JIRA services, a license is required.
JIRA provides free license for academic projects.
A 15-day trial version is available for an individual person to use.

Use of JIRA

以下是 JIRA 最重要的用途。

Following are some of the most significant uses of JIRA.

JIRA is used in Bugs, Issues and Change Request Tracking.
JIRA can be used in Help desk, Support and Customer Services to create tickets and track the resolution and status of the created tickets.
JIRA is useful in Project Management, Task Tracking and Requirement Management.
JIRA is very useful in Workflow and Process management.

JIRA - Core Features

下表详细说明了一些最重要且最常用的功能，以便更好地理解。

The following table explains some of the most important and commonly used features in detail for better understanding.

Sr.No	Core Features & Description
1	Boards JIRA supports Scrum and Kanban boards. These boards provide an immediate snapshot of the project to the team. Helps to quickly review the progress of the project and see the status of the individual tasks. Board workflow can be customized to fulfil the way a team wants to proceed.
2	Business Project Template JIRA supports n number of business templates to manage simple tasks and complex tasks like workflow. Template can be customized based on the team and their approach. Ex: Workflow can be customized based on each team’s approach. Every step is accounted and team can move to achieve their goals.
3	Task Details Tasks can be defined at the individual level to track the progress. Status of every task, comment, attachment and due dates are stored in one place.
4	Notifications An email can be sent for a particular task to the users. Voting and watching features to keep an eye on the progress for the stakeholders. Use @mention to get the attention of a specific team member at Comments/Description. User will instantly notify if something is assigned or if any feedback is required.
5	Power Search JIRA supports a powerful search functionality with Basic, Quick and Advanced features. Use the search tool to find answers like due date, when a task was last updated, what items a team member still needs to finish. Project information at one place, search within a project.
6	Reports JIRA supports more than a dozen reports to track progress over a specific timeframe, deadlines, individual’s contribution, etc. Easy to understand and generate different reports those help to analyze how the team is going on. Easy to configure these reports and display the matrices to the stakeholders.
7	Scale with Team Growth JIRA supports any business team and any project irrespective of size and complexity.
8	Add -Ins JIRA supports more than 100 add-ins to connect with different software to make work easy. Wide range of add-ins makes it as universal across the globe.
9	Multilingual JIRA supports more than 10 languages those are widely used as English (US, UK, India), French, German, Portuguese, Spanish, Korean, Japanese and Russian.
10	Mobile App JIRA is available as a Mobile Application as well. It is available on Google Play Store and App Store (iTunes) of Apple. Easy to stay connected with the team while moving anywhere with notification, comments and project activity.

JIRA - Project

项目包含问题；JIRA 项目可以被称为是一个问题集合。JIRA 项目有多种类型。例如 −

A Project contains issues; a JIRA project can be called as a collection of issues. A JIRA Project can be of several types. For example −

Software Development Project
Marketing Project
Migration to other platform project
Help Desk Tracking Project
Leave Request Management System
Employee Performance System
Website Enhancement

Create a New Project

要创建项目，用户应以 JIRA 服务台管理员身份登录，然后单击项目 → 创建项目。

To create a project, the user should login as a JIRA Service Desk Admin and then Click on Project → Create Project.

以下屏幕截图显示了如何从仪表板访问 Create Project 按钮。

The following screenshot shows how to reach to the Create Project button from the Dashboard.

选择适合你需求、遵循你的流程的项目类型。

Choose the type of Project that suits your requirement and the process it should follow.

以下屏幕截图显示了 JIRA 中可用的项目类型。

The following screenshot displays the type of projects available in JIRA.

选择项目类型后，单击下一步。用户将根据选择看到项目的流程。在此，我们已经选择了 Basic Software development 。

Once the type of project is selected, click on Next. The user will see the flow of the project based on the selection. Here, we have selected Basic Software development.

上方的截图显示了在上述步骤中选择的项目可用的问题类型和工作流程 −

The following screenshot displays the available issue types and the workflow for the chosen project in the step mentioned above −

单击选择按钮，输入项目名称并确认用户希望显示在所有问题中的参考代码。完成后，单击提交按钮。

Click on the Select button, enter the name of the project and confirm the Key that the user wants to display as a reference in all the issues. Once this is done, click on the Submit button.

以下屏幕截图显示了在创建项目之前提供的详细信息字段。

The following screenshot displays the fields to provide details before the creation of a project.

包含问题的页面将显示出来。以下屏幕截图显示了是否存在与新创建项目链接的任何问题。

The page having issues will display. The following screenshot displays whether any issues are linked with a new created project.

JIRA - Issues

JIRA 是一种项目管理工具，并使用问题来跟踪所有任务。问题有助于跟踪项目中所有的基础工作。从本质上讲，在 JIRA 中，所有技术性、非技术性、支持性或任何其他类型的项目工作或任务都记录为问题。

JIRA is a project management tool and uses issues to track all the tasks. An issue helps to track all works that underlie in a project. In real time, every work or task either technical, non-technical, support or any other type of a project in JIRA are logged as an issue.

问题可依赖于组织和要求 −

An issue can be dependent on the organization and requirements −

Story of a project
Task of a story
Sub-task of a story
A defect or bug can be an issue
Helpdesk Ticket can be logged as issue
Leave Request

以下屏幕截图显示了开放问题的基本页面和信息 −

The following screen shot shows the basic page and information of an open issue −

JIRA - Workflow

在 JIRA 中，工作流用于 track the lifecycle of an Issue 。工作流是在问题生命周期中其状态和转换的记录。状态表示特定时间的阶段。问题在特定时间只能处于一个状态，例如已打开、待完成、已完成、已关闭、已分配等。

In JIRA, workflow is used to track the lifecycle of an Issue. Workflow is a record of statuses and transitions of an issue during its lifecycle. A status represents the stage of an issue at a particular point. An issue can be in only one status at a given point of time like Opened, To Do, Done, Closed, Assigned, etc.

当问题从一种状态移动到另一种状态时，转换是一种连接两种状态的链接。对于要在两种状态之间移动的问题，必须存在转换。简单来说，转换是对问题进行的某种工作，而状态是对该问题的工作的影响。

A transition is a link between two statuses when an issue moves from one status to another. For an issue to move between two statuses, a transition must exist. In a simple way, a transition is some kind of work done on the issue, while status is the impact of work on that issue.

Example

截至目前，已创建一个问题并将其打开。当被指派者开始处理该问题时，该问题会移至 In Progress status 。在此，转换是开始工作，而问题的状态现在是进行中。

As of now, an issue is created and opened. When the assignee starts working on the issue, the issue moves to the In Progress status. Here, the transition is starting the work, while the status of the issue is now progressive.

JIRA 工作流具有在问题创建后立即跟踪的以下阶段 −

JIRA workflow has the following stages to track as soon as an issue is created −

Open Issue − After creation, the issue is open and can be assigned to the assignee to start working on it.
In Progress Issue − The assignee has actively started to work on the issue.
Resolved Issue − All sub-tasks and works of that Issue are completed. Now, the issue is waiting to be verified by the reporter. If verification is successful, it will be closed or re-opened, if any further changes are required.
Reopened Issue − This issue was resolved previously, but the resolution was either incorrect or missed a few things or some modifications are required. From Reopened stage, issues are marked either as assigned or resolved.
Close Issue − The issue is considered as finished, resolution is correct as of now. Closed issues can be re-opened later based on the requirement.

JIRA 工作流可以指为 Defect Lifecycle 。它遵循相同的概念；唯一的区别在于它对所有问题都是通用的，而不仅仅限于缺陷。

JIRA Workflow can be referred as a Defect Lifecycle. It follows the same concepts; the only difference is that it is generic for all issues rather than limited to Defects only.

下图显示了标准工作流 −

The following diagram shows a standard workflow −

转换是一种单向链接，如果问题在两个状态之间反复移动，则应创建两个转换。

A transition is a one-way link, if an issue moves back and forth between two statuses; two transitions should be created.

Example − 在关闭和重新打开状态之间存在双向转换。在项目完成之前，如果需要进行任何修改，则可以重新打开已关闭问题，而如果在其他问题中注意到了其他工作，则可以不进行任何特定工作直接关闭重新打开的问题。

Example − There are two-way transitions between closed and re-opened statuses. A closed issue can be reopened if any modifications are required at any time until the project completes, while a re-opened issue can be closed directly if additional work is taken care in another issue and no specific work has been done on the re-opened issue.

JIRA - Installation

在这一章中，我们将学习如何安装系统上的 JIRA。

In this chapter, we will learn how to install JIRA on your system.

Important Points to Note

JIRA is a web application that provides a private website to an individual or a set of requested users belonging to the same company/project.
JIRA can be run as a Windows Service at the server side.
JIRA is a pure Java based application and supports all OS platforms like Windows, Linux of different versions or MAC, etc., those satisfy JDK/JRE requirements.
JIRA supports all famous browsers like Chrome, IE, Mozilla and Safari.
It supports Mobile browsers as well in mobile views.

System Requirements

由于 JIRA 是一个网络应用程序，因此遵循客户端/服务器的概念。这意味着 JIRA 可以在服务器上集中安装，而用户可通过来自任意计算机的网站使用网络浏览器与其交互。

Since JIRA is a web-application, it follows the concept of client/server. It means that JIRA can be installed centrally on a server and users can interact with it through web-browsers using a website from any computer.

Browser − JavaScript should be enabled, the user is recommended not to use any script-blocking tool like NoScript to access full functionality of JIRA.
JDK/JRE − It is recommended to update JRE/JDK with the latest version. JIRA 6.4 recommends using JRE/JDK version 8.

由于我们的范围是作为最终用户使用 JIRA 应用程序，因此可以忽略服务器端要求。

Since our scope is to consume the JIRA application as end users, we can ignore the server side requirements.

Installation at the Server Side

JIRA follows the Client/Server concept. At the server side, JIRA must be installed before using it as end user.
At the server side, JIRA must connect with relation database to store issues/application data.
Download the JIRA Windows Installer.exe file from the following link − https://www.atlassian.com/software/jira/download?_ga=1.28526460.1787473978.1 488778536.
Select the OS type and click on Download.

以下屏幕截图显示如何为特定操作系统下载 .exe 文件。

The following screenshot shows how to download the .exe file for a specific OS.

运行 .exe 文件以运行安装向导。以下屏幕截图显示下载的 .exe 文件。

Run the .exe file to run the installation wizard. The following screenshot shows the downloaded .exe file.

单击 .exe 文件后，将显示 Run 确认弹出窗口，单击“运行”。以下屏幕截图显示“运行”确认弹出窗口。

After clicking the .exe file, the Run confirmation pop-up displays, click on RUN. The following screenshot shows the RUN confirmation pop-up.

显示以下 JIRA 安装向导，单击“下一步”。

The following JIRA installation wizard displays, click on Next.

选择适当的安装选项，如以下屏幕截图所示，然后单击“下一步”。

Choose the appropriate installation option as shown in following screenshot and then click on Next.

安装摘要显示了安装目录、主页目录、TCP 端口等，如下面的屏幕截图所示。

The installation summary is displayed with the Destination Directory, Home Directory, TCP Ports, etc., as shown in the following screenshot.

单击“安装”。JIRA 将开始安装，如下面的屏幕截图所示。完成安装需要几分钟时间。

Click on Install. JIRA will start installing as displayed in following screenshot. It takes a couple of minutes to finish the installation.

安装后，如果选中“立即启动 JIRA Software 7.3.4”复选框，JIRA 将自动启动。然后单击“下一步”，如果没有选中，则可以使用相应的 Windows 开始菜单快捷方式进行访问。

After installation, JIRA will be started automatically if the check box to “Start JIRA Software 7.3.4 now” is checked. Then click on Next, if not, it can be accessed using the appropriate Windows Start Menu shortcut.

单击“完成”按钮。

Click the Finish button.

安装程序将在开始菜单上创建以下快捷方式 −

The installer will create the following shortcuts on the start menu −

Access JIRA
Start JIRA Server
Stop JIRA server
Uninstall JIRA

以下屏幕截图显示上述快捷方式 −

The following screenshot shows the above-mentioned shortcuts −

选择许可证类型并输入组织名称，如下面的屏幕截图所示 −

Select the license type and enter organization name as shown in following screenshot −

单击“生成许可证”。

Click on Generate License

将显示确认弹出窗口，如下面的屏幕截图所示。单击“是”。

A confirmation pop-up will display as shown in the following screenshot. Click on Yes.

设置管理帐户，如下面的屏幕截图所示。

Set up the administration account as displayed in the following screenshot.

JIRA 会自动完成如下所示的设置：

JIRA will automatically finish the setting-up as shown below −

一旦 JIRA 完成设置并在服务器上开始运行，用户就可以从具有 JIRA 服务器网络访问权限的任何计算机上的浏览器访问它。

Once JIRA finishes the setup and starts running in the server, the user can access it from a browser on any computer with network access to the JIRA server.

JIRA - Free Trials Setup

JIRA 提供 15 天至 1 个月的基本功能免费试用。JIRA 还有其他计划，具有不同的高级特性和插件。成本取决于用户数量。

JIRA provides 15 days to 1-month free trials of basic features. JIRA has other plans as well with different advanced features and add-ins. The cost depends on the number of users.

通过访问 https://www.atlassian.com/software/jira/try ，用户可以看到试用目的的各种可用计划。

By visiting https://www.atlassian.com/software/jira/try, a user can see different available plans for trying purposes.

Setup for Free Trials

要设置免费试用，用户必须在以下链接上注册 - https://id.atlassian.com/signup?application=&tenant=&continue 或在其已有帐户的情况下登录。

To setup a free trial, the user has to Sign up on the following link − https://id.atlassian.com/signup?application=&tenant=&continueor login if he already has an account.

以下屏幕截图显示了在 Atlassian 账户中注册的必需字段。

The following screenshot shows required fields to sign up in Atlassian account.

用户必须登录电子邮件帐户，并通过单击 JIRA-Atlassian 发送的链接来验证帐户。下一步是转到 https://www.atlassian.com/software/jira/try 并单击网页右下角的 Create now 按钮。

The user has to log into the email account and verifies the account by clicking on the link sent by JIRA-Atlassian. The next step is to go to https://www.atlassian.com/software/jira/try and click on Create now button, which is at the bottom right hand of the webpage.

以下屏幕截图显示 JIRA 可供试用的不同计划。

The following screenshot shows different plans available for trial of JIRA.

以下屏幕截图显示了为免费试用选择的计划的详细信息。

The following screenshot shows the details of the chosen plan for a free trial.

用户填写完所有详细信息以及示例网站名称后，必须单击 Start now 按钮。以下屏幕截图显示如何声明您的网站并提供您的凭据以启动它。

Once the user fills in all the details along with the sample website name, user has to click on the Start now button. The following screenshot shows how to claim your site and provide your credentials to start it.

启动请求的示例 JIRA 网站需要几分钟时间。完成之后，将显示 JIRA 登录页面，并且用户可以在浏览器的地址栏中看到给定的示例网站名称。用户现在可以直接访问此链接以导航到 JIRA。以下屏幕截图显示了 JIRA 的登录页面。

It will take a few minutes to start the requested sample JIRA website. Once it is done, the JIRA login page will display and the user can see the given sample website name in the browser’s address bar. The user can now directly access this link to navigate to JIRA. The following screenshot shows the login page of JIRA.

JIRA - Login

要登录到 JIRA，请前往您的示例网站。这将打开一个登录页面。填写您注册的电子邮件地址/用户名和密码。单击登录按钮。以下屏幕截图展示了如何使用您的凭据登录到 JIRA。

To login to JIRA, go to your sample website. It will open a login page. Fill in your registered email address/username and Password. Click on the Login button. The following screenshot shows how to login into JIRA using your credentials.

Common Login Errors

在任何登录不成功的情况下，会显示一条错误消息。下面的屏幕截图展示了用户在凭据不匹配或不正确的情况下接收到的错误消息。

In case of any unsuccessful login, an error message displays. The following screenshot shows the error message a user receives, if the credentials are not matching or incorrect.

要纠正此情况，请单击“无法访问您的帐户”，然后选择适当的选项并填写详细信息。单击电子邮件。以下屏幕截图展示了用户忘记用户名时如何恢复用户名。

To rectify this scenario, click on “Unable to access your account”, then select the appropriate option and fill in the details. Click on email. The following screenshot shows how to recover the username, in case the user has forgotten it.

用户会收到一封包含其用户名详细信息或重置密码链接的电子邮件。

The user will get an email with the details of his username or a link to reset the password.

Successful Login

在成功登录后，系统仪表板将显示帐户是否与管理员相关联的任何项目，或者用户是否可以创建示例项目（如前几章所述）。

On a successful login, the system dashboard will display if the account is associated with any project by the admin, or if a user can create a sample project as explained in the earlier chapters.

以下屏幕截图在成功登录后展示了 JIRA 的欢迎页面/仪表板。

The following screenshot displays the welcome page/dashboard of JIRA on a successful login.

JIRA - Dashboard

登录到 JIRA 后，仪表板是显示的第一个页面。仪表板由管理员自定义。基于角色，管理员可以设置 JIRA 的访问权限。甚至管理员有权更改 JIRA 的颜色和徽标。

After logging into JIRA, the Dashboard is the first page that shows up. The Dashboard is customized by the Admin. Based on the roles, the admin can set the access of JIRA. Even the admin has the right to change colors and the logo of JIRA.

Important Points of the Dashboard

以下是用户在使用 JIRA 仪表板之前应了解的部分最重要的要点 -

Following are some of the most significant points the users should understand before using the JIRA Dashboard −

The navigation bar, present at the top of the JIRA page, will be the same across all the pages/screens of JIRA. Dashboard, Projects, Issues, Boards and Create are the main links. These links have many sub-links to navigate other functionalities.
Navigation bar contains links that provides a quick access to the most useful functions of JIRA.
Just under navigation bar, there is a System Dashboard.
The information provided in the system dashboard area can be customized by the Admin.
By default, it has three main sections – Introduction, Assigned to Me (displays Issues list assigned to users) and Activity Stream (Activities done by the users).

以下屏幕截图显示了 JIRA 仪表板页面的概述 -

The following screenshot shows the overview of the Dashboard page of JIRA −

Types of Projects

“项目”链接有几个子链接，为了更好的理解，对这些链接进行了详细解释 -

The Projects link has several sub-links, which are explained in detail for better understanding −

Current Project − It displays the name of the Project where the user is currently in or is viewing the dashboard of the project. By clicking at Project name, it will display the list of issues associated with the project.
Recent Project − It displays the name of the recent project that the user has accessed, if exists, where the user can navigate by clicking on the project listed under this header.
Software − It is the sub-link to navigate the list of projects, which are listed in the Project Type as Software.
Business − It is also a project-type. By clicking here, it will display the list of business project types.
View all Projects − It displays all the projects, which are associated with the logged in user.
Create Project − This link is usually accessed by the Admin or it depends on various roles. If this link is visible, a user can create a new project by following the instructions given there.

以下屏幕截图显示了“项目”类别下的不同子链接。

The following screenshot shows the different sub-links under the Project category.

Types of Issues

它有许多子链接可访问其他功能。以下屏幕截图显示了“问题”导航下可用的子链接。

It has many sub links to access other functionalities. The following screenshot shows different available sub-links under Issue navigation.

Search for Issues − It navigates to the search page, where the user can provide search criteria to narrow down the results.
Recent Issues − It displays the list of issues that are recently viewed by the user.
Import issue from CSV − This feature allows the user to import the details of issues by uploading a CSV file and mapping the fields.
My open issues − It is the filter section, which displays issues those are open and assigned to the logged-in user.
Reported by me − This filter section displays the issues, which are already created by the logged-in user.
Manage filters − It helps to customize the filter and narrow down the results. It displays any saved filters/ favorites filters.

Types of Boards

看板是项目遵循的流程的展示。如果项目遵循敏捷方法，它可能是最著名的敏捷看板，或者也可能是看板。

Boards are showcase of process that is followed by Project. It could be the most famous Agile Board if the project is following the agile methodology or it might be the Kanban board as well.

Recent Board − It displays the recent project board accessed by the user.
View all boards − It displays all available project boards.

以下屏幕截图显示了看板部分下可用的不同子链接。

The following screenshot shows the different sub-links available under the board section.

The Create Button

通过单击“创建”按钮，它显示了 create form 以记录 Issue。

By clicking on the Create button, it displays the create form to log an issue.

以下屏幕截图显示了创建 Issue 所需的字段和其他字段 −

The following screenshot shows required fields and other fields to create an issue −

The Feedback Link

导航栏的右侧有一个反馈链接（如下面的屏幕截图所示）。通过单击该链接，用户将获得一个表单，他可以填写摘要、说明、姓名和电子邮件来提供反馈。

There is a feedback link at the right side of the navigation bar (as highlighted in the following screenshot). By clicking on link, user gets a form where he can provide feedback by entering Summary, Description, Name and email.

以下屏幕截图显示了仪表板中反馈链接的位置。

The following screenshot shows the location of the Feedback link present in the Dashboard.

以下屏幕截图显示了提供反馈所需的字段和可选字段。

The following screenshot shows the required and optional fields to provide feedback.

一旦填写完所有字段，单击“提交”，它将成功发布反馈。

Once all the fields are filled, click on Submit, it successfully posts the feedback.

The Help Link

帮助链接提供了有关 JIRA 的其他有用文档。通过单击“关于 JIRA”，它还提供了 JIRA 的详细信息。同样，此链接还通过单击“新增功能”提供新版本功能。键盘快捷键为用户提供了很多有用的键盘导航，从而节省了时间。以下屏幕截图显示了帮助链接和其中可用的不同子链接。

The Help link provides different useful documentation about JIRA. It provides the details of JIRA as well by clicking on “About JIRA”. Similarly, this link also provides new release features by clicking on “What’s new”. Keyboard shortcuts have much useful keyboard navigation for users that saves time. The following screenshot shows the Help link and different sub-links available in it.

User Profile Button

通过单击个人资料链接，用户可以查看其个人资料详细信息并管理此部分。通过单击“注销”，用户将返回登录页面，并且在不重新登录的情况下将无法访问项目详细信息。

By clicking on the profile link, the user can view his profile details and manage this section. By clicking on Logout, the user will get back to the login page and will not be able to access the project details without logging in again.

以下屏幕截图显示了“用户个人资料”部分下的可用功能 −

The following screenshot shows available functionality under User-Profile section −

单击编辑符号，用户将能编辑简介详细信息，例如——总结详细信息、偏好设置等。以下屏幕截图显示了如何单击每个部分的编辑（以红色轮廓突出显示）图标来编辑简介。

By clicking on the edit symbol, the user will be able to edit profile details like – Summary Details, Preferences, etc. The following screenshot shows how to edit the profile by clicking on the Edit (highlighted in red outline) icon at each section.

在右侧，用户可以看到已登录用户执行的活动流。

On the right side, the user can see the activity stream performed by the logged in user.

JIRA - Issue Types

由于 JIRA 跟踪所有任务、子任务，甚至作为问题的任务，因此有几种类型的任务可识别任务并对相似任务进行分类。

Since JIRA tracks all the tasks, the sub-tasks or even a work as an Issue, there are several types of Issues to identify the work and categorize the similar issues.

任务分类如下 -

An Issue is classified as follows −

Sub-Task − This is the sub-task of an issue. In a logged issue, there can be different tasks to resolve it, which are called as sub-tasks.
Bug − A problem that impairs or prevents the functions of the product.
Epic − A big user story that needs to be broken down. Created by JIRA Software - do not edit or delete.
Improvement − An improvement or enhancement to an existing feature or task.
New Feature − A new feature of the product, which is yet to be developed.
Story − A user story. Created by JIRA Software - do not edit or delete.
Task − A task that needs to be done to achieve team’s goal.

如果用户以管理员身份登录并导航到设置 → JIRA 管理员 → 问题，则将显示所有列出的问题类型。以下屏幕截图显示了 JIRA 中所有可用的问题类型。

If a user logs in as Admin and navigate to Settings → JIRA Administrator → Issues, all the listed issue types will display. The following screenshot shows all the available issue types in JIRA.

Issue Type Schemes

问题类型方案确定哪些问题类型对项目或项目集可用。它还可以管理指定问题类型在用户界面中呈现的顺序，同时在 JIRA 中创建问题。一旦项目添加到 JIRA 中，就会生成问题类型方案。

An issue type scheme determines which issue types will be available to a project or set of projects. It also manages specifying the order in which the issue types will present in the user interface of JIRA, while creating an Issue. An issue type scheme generates as soon as the project is added in the JIRA.

在此，一个方案默认命名为默认问题类型方案，其他的是项目方案。默认问题类型方案是全局问题类型的列表。所有新创建的问题类型将自动添加到该方案。以下屏幕截图显示了不同项目的 Issue 类型方案。

Here, one scheme is by default named as the Default Issue Type Scheme and others are project schemes. The default issue type scheme is the list of global issue types. All newly created issue types will automatically be added to this scheme. The following screenshot shows Issue type schemes of different projects.

通过单击右上角的添加问题类型方案按钮，用户可以添加用户定义的方案。

By clicking on the Add Issue Type Scheme button at the top right hand corner, the user can add a user defined scheme.

从可用问题类型列表中输入当前方案的名称、说明和选择问题类型。以下屏幕截图显示了如何通过提供必需和可选字段来添加新的类型方案。

Enter the Name, Description and Select the Issue Type for the Current scheme from the Available issue type list. The following screenshot shows how to add a new type schema by providing the required and optional fields.

单击保存。新建的方案将出现在列表中。以下屏幕截图显示了添加新的问题类型后页面的显示方式 -

Click on Save. The new schema will appear in the list. The Following screenshot shows how the page display after adding a new Issue Type schema −

通过点击“编辑”，用户可以编辑详细信息。通过点击“关联”，用户可以将此方案关联到一个项目。复制和删除用于复制和删除同一方案。

By clicking on Edit, the user can edit the details. By clicking on Associate, the user can associate this scheme to a project. Copy and Delete is used for copying and deletion of the same scheme.

JIRA - Screens

View Screen

这是字段的排列和表示，以便在创建新问题或修改现有问题和通过一个状态向另一个状态转换问题时在 UI 中显示。如果用户以管理员身份登录并导航到设置 → 问题 → 屏幕，他们将能够看到所有可用的屏幕。以下屏幕截图显示了不同项目的可用屏幕。

It is the arrangement and representation of fields to display in UI whenever a new issue is created or existing issues are modified and issue transitioned through one status to another. If a user logs in as Admin and navigate to Settings → Issues → Screens, he will be able to see all the available screens. The following screenshot shows the available screen for different projects.

通过点击配置，用户将能够看到此屏幕的所有可用字段。而以有序的方式排列时，它将在 UI 中显示。以下屏幕截图显示如何配置屏幕字段。

By clicking on configure, the user will be able to see all the available fields with this screen. Whereas, in the organized/arranged way of order, it will display at the UI. The following screenshot shows how to configure the screen fields.

Screen Schemes

屏幕方案提供了一个选择字段的选项，应该在选择特定问题类型时显示。屏幕方案使用问题类型屏幕方案与问题类型进行映射。它可以与一个或多个项目关联。只有在任何问题类型屏幕方案不使用屏幕方案时才能将其删除。用户可以通过单击添加屏幕方案按钮添加新的屏幕方案。以下屏幕截图显示了可用性项目的不同屏幕方案。

Screen schemes provides an option to choose fields, which should display when a particular issue type is selected. A screen scheme is mapped with issue type using the Issue Type Screen Scheme. It can be associated with one or more project. A screen scheme can be deleted only when it is not used by any Issue Type screen scheme. The user can add a new screen scheme by clicking on the Add Screen Scheme button. The following screenshot shows the different screen schemes available for the listed projects.

提供所有详细信息并单击添加按钮。以下屏幕截图显示了如何添加新的屏幕方案。

Provide all details and the click on the ADD button. The following screenshot shows how to add a new screen scheme.

JIRA - Issue Creation

要在 JIRA 中创建问题，用户应该在项目中拥有创建问题权限。管理员可以添加/删除权限。

To create an issue in JIRA, the user should have Create Issue permission in the project. Admin can add/remove the permission.

Steps to Follow

单击导航栏中的创建按钮以打开创建问题对话框。

Click on the Create button in the navigation bar to open the create issue dialogue box.

为了完成创建问题的过程，我们应该遵循以下给出的指针。

To complete the process of creating an issue, we should follow the pointers given below.

Select the Project where the issue is.
Select the type of issue, whether it is a bug/new feature/story, etc.
Write a one-line summary to provide the overall idea about the issue.
Write the details of the issue in the Description field. Explain the issue, so that stockholders can understand every detail of the issue.
To create a similar type of issue in the same project and issue type, check the checkbox of “Create another” otherwise keep it as unchecked.
After entering all the details, click on the Create button.

以下屏幕截图展示了如何通过提供必需和可选项详细信息来创建问题。

The following screenshot shows how to create an issue by providing the required and optional details.

如果“创建另一个”复选框未选中，在点击“创建”按钮后，用户必须导航到仪表板，并且右侧将显示一个弹出窗口，其中包含 issue id 和 summary 。

If the “Create another” checkbox is not checked, after clicking on the Create button, the user will have to navigate to the Dashboard and a pop-up will display on the right side with an issue id and summary.

以下屏幕截图展示了如何知道问题是否成功创建。

The following screenshot shows how to know whether the issue is successfully created or not.

如果在点击“创建”按钮时勾选了“创建另一个”复选框，用户将获得一个包含 issue id 的新创建问题页面。

If the “Create another” checkbox is checked while clicking on the Create button, the user will get a new create issue page along with the issue id.

以下屏幕截图展示了用户勾选“创建另一个”框的情况下的页面。

The following screenshot shows the page, if the user has checked the “Create another” box.

Configure Fields

要向“创建问题”表单中添加其他字段，请点击页面右上角的“配置字段”。以下屏幕截图展示了如何在“创建问题”页面中配置字段。

To add other fields in the Create Issue form, click on “Configure fields” at the top right hand side of the page. The following screenshot shows how to configure the fields in the Create Issue page.

点击 Configure fields 按钮后，将显示一个下拉框，点击“自定义”。以下屏幕截图展示了在 Custom 选项卡下的可用字段。

After clicking on the Configure fields button, a drop down box will be displayed, click on Custom. The following screenshot shows the available fields under the Custom tab.

通过勾选和取消勾选复选框以显示和隐藏，字段将从表单中添加或清除。以下屏幕截图展示了在 All 选项卡下的可用字段。

By checking and unchecking the checkboxes to show and hide, fields will be added or cleared from the form. The following screenshot shows the available fields under the All tab.

现在导航到“创建问题”，所有基于选项的字段都将显示在弹出的表单中。以下屏幕截图展示了在“创建问题”页面中配置的字段。

Now navigate to Create Issue, all fields based on choices will be displayed in the form that shows up. The following screenshot shows the configured fields in the Create Issue page.

以下是对“创建问题”表单中的字段的说明。

The fields in the Create Issue form are explained below.

Priority − Issue creator can set the priority to resolve the issue as High, Medium, Low, and Lowest.
Labels − It is similar to Tag; it helps in filtering out specific types of issues.
Linked Issue − It links other issues that are either dependent on this issue or this issue is dependent on them. Options in dropdowns are – block, is blocked by, duplicate, clone, etc.
Issue − User can link the issue by the Typing ID or summary of those that are related to the linked issue field.
Assignee − The person who is responsible to fix this issue. Assignee name can be entered by the issue creator.
Epic Link − An Issue creator can provide an epic link, if the issue belongs to any of those.
Sprint − The user can define in which sprint, this issue belongs to, when this issue should be addressed.

在下一章，我们将学习如何克隆问题。

In the next chapter, we will learn how to clone an issue.

JIRA - Clone an Issue

克隆意味着复制。克隆一个 issue 意味着在同一个项目中创建一个副本 issue。已克隆的 issue 可以被视作一个新 issue，并像其他 issue 一样进行编辑。

Cloning means to copy. To clone an issue means to create a duplicate issue within the same project. A cloned issue can be treated as a new issue and edited like other issues.

在克隆 issue 时，我们应该考虑以下几点。

We should consider the following points while cloning an issue.

A cloned issue is completely a separate issue from the original issue.
Any action or operation taken on the original issue does not have any impact on the clone issue and vice-versa.
The only connection between the original and clone is the link that is created.
Information that is carried from the original issue to clone issue is as follows −
Information that is not cloned −

Steps to Follow for Cloning

打开一个要克隆的 JIRA issue。在屏幕出现后，选择更多→克隆。以下屏幕截图显示了如何访问克隆功能。

Open a JIRA issue that is supposed to be cloned. Select More → Clone when the screen appears. The following screenshot shows how to access the Clone functionality.

在克隆屏幕中，向用户提供了一些选项，如下所示：

In the clone screen, there are a few options given to the users, which are as follows −

A user can change the summary while cloning it.
If the issue contains links to other issues, a user can check the checkbox to contain the clone issue or uncheck if the user does not want to be a part of the clone issue.
If the issue has sub-tasks, the user can select/deselect the checkbox to contain the sub-tasks in clone or not.
The same is applicable for attachment as well.
It also gives an option, whether to carry or not – the sprint value to the new clone issue.

以下屏幕截图显示了如何通过提供必要详细信息来克隆 issue。

The following screenshot shows how to clone an issue by providing the necessary details.

下一步是单击创建。它将显示克隆 issue 的详细信息。如果用户在创建时未更改克隆字词，则它将在摘要、链接和子任务中可见。以下屏幕截图显示了已克隆的 issue 的显示方式。

The next step is to click on Create. It will display the clone issue details. If the user does not change the clone words while creating, it can be visible in the summary, links and sub-tasks. The following screenshot shows how a cloned issue is displayed.

JIRA - Create a Subtask

一个问题可以通过完成不同的带有不同人员的任务来完成，例如开发、质量保证、用户验收测试、业务、支持等等。为了跟踪每个部门的进度，在问题中创建子任务并分配给相关人员。一旦所有子任务都已解决，就可以将问题标记为已完成。

An issue can be completed by performing many tasks with different persons like Dev, QA, UAT, Business, Support, etc. To track the progress in each department, sub-tasks are created in an issue and assigned to the concern person. Once all the sub-tasks are resolved, the issue can be marked as completed.

Points to Note for Creating a Subtask

创建子任务时需要考虑以下几点：

The following points are to be considered when creating a subtask.

All subtasks are an essential part of their parent issue.
All subtasks are visible on the main screen of the parent issue.
Subtasks always belong to the same project as their parent issue.
Subtask has all fields that are present in the standard issue.
Subtasks cannot have a subtask of their own.

Steps to Follow for Creating a Subtask

在创建子任务时，我们应该考虑以下步骤：

We should consider the following steps when creating a subtask.

Open an issue where subtasks should be created.
Select More → Create Subtask. Create subtask page will display.

以下屏幕截图显示了如何访问“创建子任务”功能。

The following screenshot shows how to access the Create Subtask functionality.

在所有必需的字段中输入详细信息，然后单击“创建”。以下屏幕截图显示了带有必需和可选字段的 Create Subtask Form 。

Enter the details in all the required fields and then click on Create. The following screenshot shows the Create Subtask Form with the required and optional fields.

一旦子任务创建，它将在“主问题”页面→“子任务”部分中可用。以下屏幕截图显示了如何在问题中查看子任务。

Once a subtask is created, it will be available on the Main Issue page → Subtask section. The following screenshot shows how to view a subtask in an issue.

JIRA - Convert Issue To Subtask

在本章中，我们将了解如何将问题转换为子任务。为此，我们应该遵循以下过程。

In this chapter, we will understand how to convert an issue to a subtask. For doing this, we should follow the procedure given below.

首先，导航并单击问题，该问题需要转换为子任务。选择“更多”→“转换为子任务”。以下屏幕截图显示了如何导航到“转换为子任务”。

To begin with, navigate and click to the issue, which needs to be converted into a subtask. Select More → Convert to subtask. The following screenshot shows how to navigate to convert to sub-task.

选择将对该子任务进行标记的父问题。以下屏幕截图显示了如何将问题转换为子任务。

Choose the parent issue in which this subtask will be tagged. The following screenshot shows how to convert the issue into a sub-task.

单击“下一步”。如果问题的状态不是新问题类型允许的状态。将显示“选择——新建状态”。选择新状态并单击“下一步”按钮。

Click on Next. If the status of the issue is not an allowed status for the new issue type. Select – New Status will be displayed. Select a new status and click on the Next button.

“更新字段”屏幕将提示输入任何其他字段，如果需要。否则，系统将提示一条消息——“所有字段都将自动更新”。单击“下一步”。

Update Fields screen will be prompted to enter any additional fields, if they are required. Otherwise, a message will be prompted as – 'All fields will be updated automatically'. Click on Next.

以下屏幕截图显示了如何在“子任务”中转换问题。

The following screenshot shows how to convert the issue in sub-tasks.

显示“确认”屏幕。它将显示原始值和新值。单击“完成”。

The Confirmation screen is displayed. It will display the original values and the new values. Click on Finish.

以下屏幕截图显示了如何在“子任务”中转换问题。

The following screenshot shows how to convert the issue in sub-tasks.

将显示原始问题。现在它是子任务。父级的工单号现在显示在屏幕顶部。以下屏幕截图显示了从问题成功转换后子任务的显示方式。

The original issue will be displayed. Now it is a sub-task. The parent’s issue number is now displayed at the top of the screen. The following screenshot shows how the sub-task displays after successful conversion from an issue.

Convert an Issue to a Subtask

在将问题转换为子任务时，我们应该考虑以下几点。

We should consider the following points while converting an issue to a subtask.

An issue cannot be converted into a subtask if it has its own subtask.
To convert such an issue into a subtask, we should first convert all the subtasks of issues into a standard issue and after that convert the issue into a subtask.
Subtasks cannot be moved from one issue to another directly.
To move a subtask from one issue to another, first convert all sub-tasks into issues and then again, convert issues to subtasks by giving the parent issue name while converting.

在下一章中，我们将学习如何将子任务转换为问题。

In the next chapter, we will learn how to covert a subtask to an issue.

JIRA - Convert Subtask to Issue

要将子任务转换为问题，我们应该首先导航到需要转换成问题的子任务。然后，选择更多 → 转换到问题。以下屏幕截图展示了如何导航到“转换到问题”。

To convert a subtask to an issue, we should first navigate to the subtask that needs to be converted into an issue. Then, Select More → Convert to issue. The following screenshot shows how to navigate at Convert to Issue.

首先，单击“选择问题类型”选项的下拉框，选择问题类型（即，标准问题类型），然后单击“下一步”按钮。

To begin with, click on the drop down box of the Select Issue Type option, choose the type of the issue (i.e., a standard issue type) and click on the Next button.

以下屏幕截图展示了如何将子任务转换为问题。

The following screenshot shows how to convert a sub-task to an issue.

如果子任务的状态不是新问题类型允许的状态，那么将显示 Select New Status 屏幕。选择一个新状态，然后单击“下一步”按钮。

If the status of the subtask is not an allowed status for the new issue type, then the Select New Status screen is displayed. Select a new status and click on the Next button.

在下一步中，将提示 Update Fields 屏幕输入任何其他必需的字段。否则，将显示一条消息，说明：“所有字段都将自动更新”。单击 Next 。

In the next step, the Update Fields screen will be prompted to enter any additional fields if they are required. Otherwise, a message will display stating – 'All fields will be updated automatically'. Click on Next.

以下屏幕截图展示了如何将子任务转换至问题。

The following screenshot shows how to convert a subtask in to an issue.

Confirmation 屏幕显示。它将显示原始的值和新的值。单击 Finish 。

The Confirmation screen is displayed. It will display the original values and the new values. Click on Finish.

以下屏幕截图展示了如何将子任务转换至问题。

The following screenshot shows how to convert a subtask to an issue.

问题将显示出来。它不再是子任务。屏幕顶部不再显示父问题编号。

The issue will be displayed. It is no longer a subtask. There is no longer a parent issue number displayed at the top of the screen.

以下屏幕截图展示了从子任务转换后问题将如何显示。

The following screenshot shows how the issue will display after conversion from a subtask.

JIRA - Create Issue using CSV

用户可以使用称为 CSV 的逗号分隔文件一次创建多个问题。CSV 文件是表示制表符分隔数据的文本文件，并通过逗号分隔不同的节。

A User can create multiple issues at a time using Comma separated file known as CSV. The CSV files are text files those represent tabulated data and separate different sections by commas.

他们有两个步骤，需要从 CSV 中导入数据，而还存在第三方可选步骤，如下所列。

They have two-step process that requires importing the data from a CSV, while a third optional step is also present, which are listed below.

Prepare a CSV file.
Import the CSV file into the system.
Save the configuration for future use.

Prepare the CSV File

创建 CSV 文件时必须考虑以下几点。

While creating a CSV file the following points must be considered.

每个 CSV 文件都应该有一行标题，其中包含摘要列。第一行是标题行并表示创建问题页面的字段。 Example − 摘要，被指派人，报告人，优先级，描述，sprint，“测试套件”，Ashish，Ashish，1，等。

Each CSV file should have a heading row with a summary column. The first row is the heading row and represents the fields of the create issue page. Example − Summary, Assignee, Reporter, Priority, Description, sprint, “Test Suite”, Ashish, Ashish, 1, etc.

Use double quote marks (“) in the CSV file to capture data that appears in multip.le lines. For Example − upon import, JIRA will treat the following CSV as a single record: Summary, Description, Status, "Login issue", "This is on a new line", Open
While importing issues from a CSV file, the Project Name and Project Key are important columns in CSV. In addition, the name of these fields should match exactly as they are present in JIRA.

Import the CSV File

要导入 CSV 文件，我们应该按照以下步骤操作。

To import the CSV file, we should follow the steps given below.

Step 1 − 选择问题 → 从 CSV 导入问题，以打开批量创建设置页面。

Step 1 − Select Issues → Import Issues from CSV to open the Bulk Create Setup page.

以下屏幕截图显示了如何访问从 CSV 导入问题的功能。

The following screenshot shows how to access the Import issues from the CSV functionality.

Step 2 − 在“设置”页面上，选择 CSV 源文件。如果您没有配置文件，或者您想要创建新的配置文件，那么不要选中“使用现有配置文件”复选框。

Step 2 − On the Setup page, select CSV Source File. Do not check the “Use an existing configuration file” check box, if you do not have a configuration file or if you want to create a new configuration file.

配置文件规定了 CSV 文件标题行中的列名称和 JIRA 应用程序中的字段之间的映射。

Configuration files specify a mapping between column names in the CSV file’s header row and fields in the JIRA application.

以下屏幕截图显示了批量创建设置页面，用户在其中浏览并上传 CSV 文件。

The following screenshot shows the Bulk create setup page, where the user browses and uploads the CSV file.

Step 3 - 如果用户选中“使用现有配置文件”复选框，JIRA 会要求指定现有配置文件。

Step 3 − If the user checks the checkbox of “Use an existing configuration file”, JIRA will ask to specify an Existing Configuration File.

以下屏幕截图显示了如何使用现有配置文件。

The following screenshot shows how to use an existing configuration file.

Step 4 - 如果用户未选择此选项，则在 CSV 文件导入向导结束时，JIRA 会要求创建配置文件，此配置文件可用于随后的 CSV 导入。

Step 4 − If the user does not select this option, then at the end of the CSV file import wizard, JIRA will ask to create a configuration file, which can be used for subsequent CSV imports.

单击“下一步”按钮 → CSV 文件导入向导的“设置”步骤将显示。填写必填栏位。如果 CSV 文件使用除逗号外的不同分隔符，请在 CSV 分隔符字段中指定该字符。如果分隔符为“制表符”，可以使用“/t”格式输入。

Click on the Next button → the Settings step of the CSV file import wizard will display. Complete the required fields. If the CSV file uses a different separator character other than a comma, specify that character in the CSV Delimiter field. If the separator is a 'Tab', this can be entered using the format '/t'.

以下屏幕截图显示了如何提供 csv 文件的设置 -

The following screenshot shows how to provide settings of csv file −

Step 5 - 单击“下一步”按钮继续执行 CSV 文件导入向导的映射字段步骤。在此步骤中，用户必须将 CSV 文件的列标题映射到所选 JIRA 项目中的字段。选择后，勾选映射字段值复选框。

Step 5 − Click on the Next button to proceed to the Map field’s step of the CSV file import wizard. Here, the user has to map the column headers of the CSV file to the fields in the selected JIRA project. After selection, tick the check box for Map field value.

CSV 字段应映射到 JIRA 摘要字段。这可确保创建的问题有摘要。

A CSV field should map to the JIRA summary field. This ensures the issues created have a summary.

以下屏幕截图显示了如何将 CSV 字段映射到 JIRA 字段 -

The following screenshot shows how to map CSV fields with JIRA fields −

Step 6 - 单击“下一步”按钮，CSV 文件导入向导的映射值步骤将显示。在此导入向导步骤中，用户可以选择将哪些特定 CSV 字段值映射到哪些特定 JIRA 字段值。

Step 6 − Click on the Next button, the Map values step of the CSV file import wizard will display. On this step of the import wizard, the user can select which specific CSV field values to map to which specific JIRA field value.

Fields whose Map Field Value check boxes were selected in the previous step will be presented on this page.
If the CSV field has a username (e.g. Reporter or Assignee) and does not select the Map Field Value check box for this field in the previous step of the CSV file import wizard, then the importer will map imported usernames from the CSV file to (lowercase) JIRA usernames.

以下屏幕截图显示了如何映射值。

The following screenshot shows how to map values.

Step 7 - 单击“验证”按钮，它将验证已导入的数据并在需要时显示任何错误或警告，否则将显示使用该文件可能成功导入多少数据。

Step 7 − Click on the Validate button, it will validate the imported data and display if any errors or warnings are required, otherwise it will display how many successful imports are possible with the file.

以下屏幕截图显示了 CSV 文件的成功验证。

The following screenshot shows the successful validation of CSV file.

Step 8 - 现在，单击“开始导入”按钮。导入器将显示更新，例如导入正在进行中，然后在导入完成后显示一条成功消息。

Step 8 − Now, Click the Begin Import button. The importer will display updates like import is in progress, then a success message when the import is completed.

以下屏幕截图显示了使用 CSV 文件创建了多少问题 -

Following screenshot shows how many issues are created using CSV file −

Step 9 - 单击“检查已创建的问题”，它将显示使用 CSV 创建的问题列表。

Step 9 − Click on the Check Created issues, it will display the list of issues those are created using the CSV.

以下屏幕截图显示了使用 CSV 文件创建的新问题列表。

The following screenshot shows the list of newly created issues using the CSV file.

JIRA - Edit an Issue

要在 JIRA 中编辑问题，用户必须导航到要编辑的问题，并单击问题以打开该页面。下一步是单击 Edit 按钮，它位于查看问题页面左上角。它将打开一个编辑问题页面，该页面类似于创建页面。

To edit an issue in JIRA, the user has to navigate to the issue, which is required to edit and the click on the issue to open the page. The next step is to click on the Edit button, which is present at the top left hand side of the view issue page. It will open the edit issue page that is similar to the create page.

以下屏幕截图展示了如何访问 Edit 功能。

The following screenshot shows how to access the Edit functionality.

或者，将鼠标悬停在字段上并单击 Pencil Icon 以在线编辑该特定字段。

Or, hover the mouse over the field and click on the Pencil Icon to edit the specific field inline.

以下屏幕截图演示了如何编辑特定字段而不点击主编辑按钮 -

The following screenshot shows how to edit a specific field without clicking on main edit button −

在编辑问题页面的相应字段中修改问题详细信息。以下屏幕截图显示了编辑页面，以更新问题的详细信息。

Modify the issue details in the corresponding field of the edit Issue page. The Following screenshot shows the edit page to update details of an issue.

更新完成后，单击更新按钮。用户将能够在查看问题页面中看到已编辑的文本/字段。

Once the update is completed, click on the Update button. The user will be able to see the edited text/fields in the View Issue Page.

以下屏幕截图显示了更新的详细信息 -

The Following screenshot shows the updated details −

JIRA - Email an Issue

在本章中，我们将学习如何在 JIRA 中发送电子邮件 issue。用户可以将 issue 发送给其他 JIRA 用户。有两种方法可以做到这一点：

In this chapter, we will learn how to email an issue in JIRA. A user can email an issue to other JIRA users. There are two ways to do it −

By share an issue and
By mention these users in issue’s Description or Comment field.

让我们现在详细讨论每一个这些。

Let us now discuss each of these in detail.

Sharing an Issue

首先，用户应该导航到需要分享的问题并点击查看该问题。点击页面右上角的 Share Symbol 。以下屏幕截图显示了在问题页面中共享选项出现的位置 −

To begin with, the user should navigate to the issue that is required to share and click to view the issue. Click on the Share Symbol on the top right hand side of the page. The following screenshot shows where the sharing option present at issue page −

您可以通过输入其用户名或他们全部或部分在 JIRA 中注册的全名来撰写 JIRA 用户姓名，或输入您想要与他们共享问题的个人的电子邮件地址。

You can write the JIRA users’ name by typing their usernames or partially/all of their full names as registered with JIRA or type the email addresses of the individuals with whom you would like to share the issues.

当用户开始输入 JIRA 用户的用户名或姓名，或先前指定的电子邮件地址时，将出现一个用户的自动完成下拉列表。

When the user starts typing a JIRA user’s username or name, or a previously specified email address, an auto-complete dropdown list of users appears.

以下屏幕截图显示如何提供电子邮件地址或从自动完成建议中进行选择。

The Following screenshot shows how to provide email addresses or select from the auto-completion suggestions.

添加可选的备注。点击 Share 向导部分中的 Share 按钮。以下屏幕截图显示如何向用户分享/通过电子邮件发送问题。

Add optional note. Click on the Share button present in the Share wizard section. The following screenshot shows how to share/email an issue to a user.

Mention Users in Description / Comment

在问题的 Description 或 Comment 字段中，输入“@”，然后输入 JIRA 用户的用户名或他们全部或部分在 JIRA 中注册的全名的前几个字符。

In the issue’s Description or the Comment field, type '@' and then the first few characters of the JIRA user’s username or partially/all of their full name as registered with JIRA.

当用户开始输入时，建议用户的列表将出现在字段下方的下拉列表中。用户应根据引用的用户完全输入 JIRA 用户的用户名，或从下拉列表中建议的用户列表中进行选择。

As the user starts typing, a list of suggested users will appear in a dropdown list below the field. The user should select based on the referenced users by completely typing the JIRA user’s username or choose from the list of suggested users in the dropdown list.

以下屏幕截图显示如何在说明中提及用户的姓名/电子邮件。

The following screenshot shows how to mention the user’s name/email in the description.

点击提交字段。JIRA 将向该用户发送一封电子邮件，表明您在那问题中提到了他们。

Click on submit the field. JIRA will send that user an email message indicating that you mentioned them on that issue.

以下屏幕截图显示如何提交在说明中提及的用户的电子邮件。

The following screenshot shows how to submit mentioning the user’s email in the description.

JIRA - Label an Issue

一个标签用于对一个问题进行分类。它类似于 Twitter、Facebook 或其他社交网站中使用的标签 (#)。它还有助于搜索问题。在查看问题时，标签会出现在问题的详细信息部分。

A Label is used to categorize an issue. It is similar to the hashtag (#) used in twitter, Facebook or other social sites. It also helps while searching an issue. While viewing an issue, the label appears in the detail section of the issue.

以下屏幕截图展示了标签出现在问题详细信息页面中的位置。

The following screenshot shows where the labels are present in the issue detail page.

一旦用户单击标签，即 WFT，它将显示具有相同标签的问题列表。

Once the user clicks on the label i.e. WFT, it will display the list of issues having the same label.

以下屏幕截图展示了如何使用标签名称搜索问题：

The following screenshot shows how to search issues using label names −

Add and Remove Labels

要添加或移除标签，用户必须前往查看问题页面，并选择需要添加标签的问题。单击更多 → 标签。将出现一个对话框。

To add or remove labels, a user has to go to the View Issue page and select the issue that needs to add labels. Click on More → Labels. A dialogue box will appear.

以下屏幕截图展示了如何访问标签特性。

The following screenshot shows how to access the Label features.

开始键入标签并从建议中进行选择。以下屏幕截图展示了如何添加标签。

Start typing the label and select from the suggestions. The following screenshot shows how to add labels.

要 ‘Delete’ 标签，请单击出现在标签名称旁边的关闭 (x) 标记。以下屏幕截图展示了如何删除一个现有标签：

To ‘Delete’ a label, click on the close (x) sign, which appears beside the label name. The following screenshot shows how to delete an existing label −

单击更新按钮。已向一个问题添加/从一个问题移除标签，并且可以在查看问题页的 Detail Section 中进行验证。

Click on the Update button. Labels are added / removed from an issue and can be verified in the Detail Section of the View Issue Page.

以下屏幕截图展示了在哪里验证已更新的标签。

The following screenshot shows where to verify the updated labels.

JIRA - Linking Issues

当两个问题互相具有某种类型的依赖性时，该特性非常有用，例如，它们是副本或相互关联，上游下游依赖性或阻碍问题。

This feature is very useful when two issues have some type of a dependency on each other as if they are duplicates or relate to each other, upstream downstream dependency or blocking issues.

Create a Link to Another Issue

为了创建至另一个问题的链接，用户必须导航至问题并单击查看问题页面。然后单击更多→ Link 以显示链接对话框页面。

For creating a link to another issue, the user has to navigate to the issue and click on the View Issue Page. After that, click More → Link to display link dialogue page.

以下屏幕截图展示了如何访问链接特性−

The following screenshot shows how to access Link feature −

在对话框的左侧选择 JIRA 问题项，从下拉列表中选择“此问题”。以下屏幕截图展示了通过提供详细信息链接问题的过程。

Select JIRA Issue item in the left side of the dialogue and select “This issue” field from the dropdown list. The following screenshot shows how to link an issue by providing the details.

下一步是选择/搜索问题。以下屏幕截图展示了如何将问题添加为另一个问题的链接。

The next step is to select/search issue. The following screenshot shows how to add an issue as a link in another issue.

添加注释；它不是必须的，然后单击 Link 。查看问题页面显示，用户可以下拉并验证所链接的问题是否显示在 Issue 链接部分中。

Add the comment; it is optional and then Click on Link. The View Issue page shows up and the user can go down and verify whether the linked issue is displayed or not under the Section Issue links.

以下屏幕截图展示了如何查看父问题中的链接问题−

The following screenshot shows how to view linked issue in parent issue −

Deleting a Link

要删除链接，用户应该进入查看问题页面并进入包含链接的那个问题。下拉并前往 Issue 链接部分。将鼠标悬停在应该删除的链接上，然后单击删除图标。

To delete a link, a user should go to the View Issue page and to that issue which contains the links. Scroll down and go to Issue Links section. Hover the mouse over the link that should be deleted and then click on the Delete icon.

以下屏幕截图展示了如何删除链接−

The following screenshot shows how to delete a link −

确认弹出窗口将显示，单击删除按钮。以下屏幕截图展示了删除的确认弹出窗口。

A confirmation pop-up will display; click on the Delete button. The following screenshot shows the confirmation pop-up for deletion.

JIRA - Move an Issue

JIRA 有一个功能，可以将一个问题从一个项目移到另一个项目。让我们通过以下步骤了解用户如何执行此操作。

JIRA has a feature to move an issue from one project to another project. Let us understand with the following steps, how a user can do it.

Steps to Follow

进入要移到另一个项目的查看问题页面。选择更多 → 移动。以下屏幕截图显示了如何访问移动功能 −

Go to the View Issue page that needs to move into another project. Select More → Move. The following screenshot shows how to access Move feature −

在 Move Issue 向导的第一步中，选择新项目（问题将移至该项目中），并在需要/希望时更改问题类型。单击 Next 继续。

In the first step of the Move Issue wizard, select the new project where the issue will move, and if required/desired, change the issue type. Click on Next to continue.

以下屏幕截图显示了选择项目和问题以进行移动的步骤 −

The following screenshot shows Select Project and Issues step to move −

如果需要更改问题的状态，则用户可以转到选择状态页面。选择问题的新状态，并单击下一步按钮继续。

If there is a need to change the status of the issue, the user can go to Select Status page. Select the new status for the issue and click on the Next button to continue.

如果需要为任何必需自定义字段指定值，则会显示更新字段页面。为每个字段指定期望值，并单击下一步继续。

If required to specify the values for any required custom fields, the Update Fields page is displayed. Specify the desired values for each field, and click on Next to continue.

以下屏幕截图显示了在移动问题之前（如果需要）的更新字段步骤。

The following screenshot shows the Update Fields step, if required before moving an issue.

确认页面将显示所有更改。如果用户想要修改任何更改，请单击左侧菜单中的相应步骤以返回该向导页面。然后，单击 Move 按钮将问题移至目标项目。

The confirmation page will display with all the changes. If a user wants to revise any of the changes, click the appropriate step in the left hand side menu to return to that page of the wizard. After that, click on the Move button to move the issue to the target project.

以下屏幕截图显示了在移动前确认详细信息的确认步骤 −

The following screenshot shows confirmation step to confirm details before moving −

问题将移至目标项目并显示在屏幕上。可以进一步编辑此问题以进行其他更改。以下屏幕截图显示了成功移动问题后一个新项目和一个问题类型。

The Issue will be moved to the target project and displayed on screen. This Issue can be further edited to make additional changes. The following screenshot shows a new project and an issue type after the successful moving an issue.

JIRA - View/Change History

在本章中，我们将了解如何在 JIRAN 中查看和更改历史记录。历史记录是对问题上执行的所有活动进行的记录。一些最常见的情况是 −

In this chapter, we will learn how to view and change history in JIRAN. History is the record of all the activities performed on issues. Some of the most common instances are −

Creator of the issue
Changes to an issue field
Attachment of a file
Deletion of comment/Work log
Addition/deletion of links

在历史记录中，用户可以查看以下信息。

In a history record, a user can view the following information.

User name who made the changes
Time while the changes was made
If an issue field is changed, new and old values of that field

Steps to View History

要在 JIRA 中查看历史记录，用户应执行以下步骤。

To view history in JIRA, the user should follow the steps given below.

Go to View Issue Page to see change history
Scroll down to Activity section
Click on History tab

以下屏幕截图显示了如何查看历史记录。

The following screenshot shows how to view History.

JIRA - Watch and Vote on Issue

在本章中，我们将了解如何在 JIRA 中对问题进行投票和关注。

In this chapter, we will understand how Voting and Watching is done on an issue in JIRA.

Voting on an Issue

JIRA 具有称为“投票”的功能，用于对该问题的偏好提供意见，无论它是否已解决或完成。

JIRA has a feature called as Vote to provide the opinion on the preference for that issue, whether it is resolved or completed.

Admin needs to add permission for users to use this feature.
Go to the View Issue page where voting is required.
Click Vote for this issue to instantly vote for that issue.

以下屏幕截图显示了投票字段在问题详情页面中的位置−

The following screenshot shows where Votes field is present at issue detail page −

Note - 由于用户此处没有投票权限，因此用户无法查看投票字段旁边的链接。

Note − Since the user does not have permission here to vote, the user is not able to view the link beside Votes field.

Watching an Issue

JIRA 具有这样的功能：允许用户/利益相关者随时关注问题，只要该问题有任何更新或更改。如果有任何问题，它会向列为该特定问题的观察者发送通知/电子邮件。

JIRA has a feature that allows users/stakeholders to keep an eye on the issue, whenever there is any update or changes in that issue. If there is any the issue, it sends notification/emails to those who are listed as watchers for that specific issue.

Admin needs to add permission for users to use this feature.
Go to the view issue page that the user wants to watch.
Click on the “Start Watching this issue” link to be listed as watchers.

以下屏幕截图显示了 Watchers 字段在问题详情页面中的位置。

The following screenshot shows where the Watchers field is present in the Issue Detail page.

现在，将显示 1 （观察者）而不是零个观察者，并带有链接“停止关注此问题”以取消观察者身份。以下屏幕截图显示了更新后的观察者数量−

Now instead of zero watchers, there will be 1 (watcher) displayed along with the link “Stop watching this issue” to delist as watchers. The following screenshot shows the updated number of watchers −

用户可以单击 1 ，它允许将其他用户也添加为观察者。在 Add watchers 框中开始键入用户名并从自动完成功能框中选择。该用户将列为观察者。

The user can click on 1, it allows to add other users as well to the list as watchers. Start typing the user name in the Add watchers box and select from the autocomplete box. The user will be listed as watchers.

以下屏幕截图显示了如何通过提供用户详细信息添加新观察者。

The following screenshot shows how to add a new watcher by providing the user’s detail.

JIRA - Search

JIRA 拥有强大且高效的搜索功能。用户可以使用各种搜索类型在项目、版本和组件中搜索问题。JIRA 允许保存搜索条件，以便下次用作过滤器；甚至还可以与他人共享这些过滤器。

JIRA has powerful and very efficient search functionalities. A user can search issues across Projects, Versions and Components using various search types. JIRA allows saving the search criteria to utilize next time as filters; even these filters can be shared by others as well.

Types of Searching Options

JIRA 有几种基本方法来搜索问题。其中最重要的如下所述。

JIRA has a couple of fundamental ways to search issues. The most important ones are as follows.

Basic Search
Quick Search

现在，让我们详细了解这两种搜索类型。

Let us now understand both of these search types in detail.

Basic Search

JIRA 中的基本搜索是一种用户友好界面，可轻松用于查找问题。它在后端使用 JQL 查询。要在 JIRA 中进行基本搜索，用户必须按照以下步骤操作。

Basic Search in JIRA is a user-friendly interface that can be used easily to find out the issues. It uses the JQL queries in the backend. To do a basic search in JIRA, the user has to follow the steps given below.

Step 1 − 导航至问题 → 搜索问题。以下屏幕截图演示如何访问搜索问题功能 −

Step 1 − Navigate to issues → Search Issues. The following screenshot shows how to access the Search for Issues feature −

Step 2 − 显示搜索页面。如果有任何现有的搜索条件，请单击新建过滤器来重置它。以下屏幕截图演示如何定义新的搜索条件。

Step 2 − A search page displays. If it has any existing Search criteria, then click on the New Filter to reset it. The following screenshot shows how to define a new search criteria.

Step 3 − 根据不同字段（例如项目、类型、状态和已分配）设置搜索条件。然后单击更多并选择任何字段以使用其他字段进行搜索。以下屏幕截图显示了可以设置哪些条件来搜索问题。

Step 3 − Set the search criteria against different fields like Project, Type, Status and Assigned. Then click on More and select any field to search with additional fields. The following screenshot shows what all criteria’s can be set to search issues.

Step 4 − 如果用户希望针对任何特定的文本、关键字进行搜索，请开始在 Contains text 框中键入。以下屏幕截图演示如何在问题中搜索特定文本。

Step 4 − If the user wants to search against any specific text, keywords, start typing in the Contains text box. The following screenshot shows how to search specific text in issues.

Contains text − 用户可以在所有基于文本的字段中使用通配符或运算符来搜索特定字符串。例如 −

Step 5 − A user can use wildcards or operators in all text based fields to search specific strings. For example −

Single character wildcard - te?t
Multiple characters wildcard – win*
Boolean operators - "atlassian jira" || confluence

根据不同的搜索条件，将显示以下结果。以下屏幕截图显示了已搜索问题的列表。

Based on different search criteria, the following result is displayed. The following screenshot shows the list of searched issues.

How to Save a Search

要保存已搜索的条件，用户应按照以下步骤操作。

To save the searched criteria, the user should follow the steps given below.

Step 1 - 单击页面顶部的“另存为”。以下屏幕截图显示了如何保存搜索条件，以备将来使用。

Step 1 − Click on Save As at the top of the page. The following screenshot shows how to save the search criteria for future use.

Step 2 - 输入筛选器名称，然后单击“提交”。以下屏幕截图显示了保存之前如何提供新搜索条件的名称。

Step 2 − Type the filter name and click on Submit. The following screenshot shows how to provide a name of new search criteria before saving.

Step 3 - 筛选器将出现在“搜索页”左侧的“收藏筛选器”下，它将有几个选项，如 - 重命名、删除、复制和从收藏中移除。以下屏幕截图显示了已保存的搜索条件和可执行的可用操作。

Step 3 − A Filter will appear on the left side of the Search Page under the Favourite filters and it will have a few options like – Rename, Delete, Copy and Remove from Favourites. The following screenshot shows the saved search criteria and the available actions to perform.

Quick Search

快速搜索是定义搜索条件最快的途径。它是一个文本框，用户可以在其中输入密钥、文本或任何内容，它会开始在当前项目中搜索完全匹配项并提供结果。

The quick search is the fastest way to define search criteria. It is a text box where the user enters the key, text or anything and it starts searching for the exact matches in the current project and provides the result.

“快速搜索”框位于导航器的右上角。以下屏幕截图显示了如何访问“快速搜索”功能。

The Quick Search box is available on the top right hand corner of the navigator. The following screenshot shows how to access the Quick Search feature.

Smart Querying

快速搜索选项通过最少的键入执行智能搜索。它识别以下单词，并向用户提供几个选项进行选择。

The quick search option performs smart searches with minimal typing. It recognizes the following word and gives out several options to the user to choose.

my − This word searches issues assigned to the logged-in user.

以下屏幕截图显示了快速搜索中的不同智能查询。

The following screenshot shows different smart querying in a quick search.

以下是部分最常用的智能查询选项：

Some of the most commonly used smart querying options are as follows −

r:me − Finds issues reported by the logged-in user.
r:abc − Finds issues reported by user – abc.
r:none − Finds issues with no reporter.
<project name> or <project key> − Finds issues within the given project name or finds issues having the same project key.
Overdue − Finds issues those are overdue before today.
Created:, updated:, due: − These smart searches finds issues with Created, Updated, or Due Date using the prefixes created:, updated:, or due:, respectively. For the date range, use today, tomorrow, yesterday, a single date range (e.g. '-1w'), or two date ranges (e.g. '-1w,1w'). Date ranges cannot have spaces between them. Valid date/time abbreviations are: 'w' (week), 'd' (day), 'h' (hour), 'm' (minute).
C: − Finds issues with a particular component.
V: − Finds issues with a particular version.
Ff: − Finds issues with a Fixed For version.
* − Wildcard can be utilized with any of the above queries to find issues.

JIRA - Advanced Search

除了前一章中解释的搜索类型外，JIRA 还有一些高级搜索选项，可以使用以下三种方式执行。

Apart from the type of searches explained in the previous chapter, JIRA also has a few advanced search options, which can be performed using the following three ways.

Using Field Reference
Using Keyword Reference
Using Operators Reference

上面提到这三处进行了详尽的解释。

These above-mentioned three ways have been explained in detail below.

用户在执行任何高级搜索时应考虑以下几点。

The user should consider the following points while performing any advanced search.

Advanced search uses structured queries to search for JIRA issues.
Search results displays in the Issue Navigator.
Search results can be exported to MS Excel and many other available formats.
Save and Subscribe features are available to advanced searches.
An advanced search uses the JIRA Query Language known as JQL.
A simple query in JQL consists of a field, operator, followed by one or more values or functions. For example, the following simple query will find all issues in the "WFT" project −

Project = "WFT"

JQL supports SQL like syntax such as ORDER BY, GROUP BY, ISNULL() functions, but JQL is not a Database Query Language.

Using Field Reference

字段引用表示 JIRA 问题中表示字段名称（包括自定义字段）的单词。语法为：

A field reference means a word that represents the field name in the JIRA issue including the custom fields. The syntax is −

<field name> <operators like =,>, <> “values” or “functions”

运算符将字段值与右侧显示的值进行比较，以便查询仅检索到为真结果。

The operator compares the value of the field with value presents at right side such that only true results are retrieved by query.

Go to Issues → Search for Issues in the navigator bar.

下面的屏幕截图显示了如何导航搜索部分。

The following screenshot shows how to navigate the Search section.

如果存在现有的搜索条件，请单击新建筛选器按钮以重置该条件。下面的屏幕截图显示了如何从一个新的条件开始：

If there is an existing search criterion, click on the New Filter button to reset the criteria. The following screenshot shows how to start with a new criteria −

使用字段、运算符和值键入查询，例如 issueKey = “WFT-107” 。

Type the query using the Field, Operator and Values like issueKey = “WFT-107”.

还有其他字段——受影响版本、受让人、附件、类别、注释、组件、创建、创建者、描述、到期、环境等。只要用户开始键入，自动完成功能将有助于以定义的格式书写。

There are other fields as well – Affected Version, Assignee, Attachments, Category, Comment, Component, Created, Creator, Description, Due, Environment, etc. As soon as the user starts typing, the auto-complete functionality helps to write in the defined format.

下面的屏幕截图显示了如何使用高级功能添加字段名称条件。

The following screenshot shows how to add Field Name criteria using advanced features.

Operator selection ——下面的屏幕截图显示了如何选择运算符。

Operator selection − The following screenshot shows how to select operators.

下一步是输入值，然后单击搜索符号。下面的屏幕截图显示了如何添加值和搜索。

The next step is to enter the value and then click on the Search symbol. The following screenshot shows how to add values and search.

以下屏幕截图显示了基于设置的条件的搜索结果。

The following screenshot shows the search result based on criteria set.

Using Keyword Reference

在这里，我们将了解如何使用关键字引用以及它的优点。

Here, we will understand how to use a keyword reference and what its advantages are

JQL 中的关键字：

A keyword in JQL −

joins two or more queries together to form a complex JQL query.
alters the logic of one or more queries.
alters the logic of operators.
has an explicit definition in a JQL query.
performs a specific function that defines the results of a JQL query.

关键字列表：

List of Keywords −

AND − ex - status = open AND priority = urgent And assignee = Ashish.
OR − ex – duedate < now() or duedate is empty.
NOT − ex – not assignee = Ashish .
EMPTY − ex - affectedVersion is empty / affectedVersion = empty.
NULL − ex – assignee is null.
ORDER BY − ex – duedate = empty order by created, priority desc.

与字段引用类似，一旦用户开始输入，自动完成功能有助于获得正确的语法。以下屏幕截图显示了如何添加关键字。

Similar to field reference, as soon as the user starts typing, the auto-complete functionality helps to get the correct syntax. The following screenshot shows how to add keywords.

单击搜索符号，它将提供搜索结果。以下屏幕截图显示了基于条件集的结果。

Click on the Search symbol and it will provide the search results. The following screenshot shows the result based on a criteria set.

Using Operators Reference

运算符用于比较左侧的值和右侧的值，使只有真结果显示为搜索结果。

Operators are used to compare values of the left side with the right side, such that only true results display as the search result.

List of Operators

Equals: =
Not Equals: !=
Greater Than: >
Less Than: <
Greater Than Equals: ⇒
Less than equals: =<
IN
NOT IN
CONTAINS: ~
Does Not contain: ! ~
IS
IS NOT
WAS
WAS IN
WAS NOT IN
WAS NOT
CHANGED

与字段和关键字引用类似，这些运算符还可以用来增强搜索结果。

Similar to the Field and the Keyword Reference, these operators can also be used to enhance the search results.

JIRA - Reports

JIRA 在项目中提供不同类型的报告。它有助于分析任何项目的进度、问题、障碍和及时性。它还有助于分析资源利用率。

JIRA provides different types of reports within a project. It helps to analyze the Progress, Issues, Showstoppers and Timeliness of any Project. It also helps to analyze the resource utilization as well.

How to Access Reports

要访问 JIRA 中的报告，用户应转向项目 → 选择具体项目。以下屏幕截图显示了如何导航至具体项目。

To access reports in JIRA, the user should go to Project → choose Specific project. The following screenshot shows how to navigate to a specific project.

点击页面左侧的报告图标。它将显示 JIRA 支持的所有报告。以下屏幕截图显示了如何访问报告部分。

Click on the Reports icon on the left side of the page. It will display all the reports supported by JIRA. The following screenshot shows how to access the Report section.

当用户点击切换报告时，它将显示报告列表。以下屏幕截图显示了可供快速切换的报告列表。

When the user clicks on Switch report, it will display the list of reports. The following screenshot shows list of reports available for quick switch.

Type of Reports

JIRA 已将报告分成了四个级别，即：-

JIRA has categorized reports in four levels, which are −

Agile
Issue Analysis
Forecast & Management
Others

让我们现在详细讨论上述报表类别的功能。

Let us now discuss the features of the above-mentioned report categories in detail.

Agile

以下是敏捷报告的功能列表。

Following are the list of features of Agile Reports.

Burn down Chart − Track the total work remaining, also whether sprint is achieving the project goal or not.
Sprint Chart − Track the work completed or pushed back to the backlog in each sprint.
Velocity Chart − Track the amount of work completed from sprint to sprint.
Cumulative Flow Diagram − Shows the statuses of issues over time. It helps to identify high-risk issues or unresolved important issues.
Version Report − Track the projected release date for a version.
Epic Report − Shows the progress towards completing an epic over a given time.
Control Chart − Shows the cycle time for the product, its version or the sprint. It helps to identify whether data from the current process can be used to determine future performance.
Epic Burn Down − Track the projected number of sprints required to complete the epic.
Release Burn Down − Track the projected release date for a version. It helps to monitor whether the version will release on time, so mandatory action can be taken if work is falling behind.

Issue Analysis

以下是问题分析的功能列表。

Following are the list of features of Issue Analysis.

Average Age Report − Displays the average age in days of unresolved issues.
Created Vs Resolved Issue Report − Display the number of issues created vs the number of issues resolved in given period.
Pie chart Report − Shows a pie chart of issues for a project grouped by a specified field.
Recently Created Issue Report − Shows the number of issues created over a time-period for a project and how many of those were resolved.
Resolution Time Report − Displays the average time taken to resolve issues.
Single Level Group by Report − .It helps to group the search results by a field and see the overall status of each group.
Time since Issues Report − It helps to track how many issues were created, updated, resolved, etc., over a time-period.

Forecast & Management

以下是预测和管理类型报告的功能列表。

Following are the list of features of Forecast and Management type of reports.

Time Tracking Report − Shows the original and current time estimates for issues in the current project. It can help to determine whether work is on track for those issues.
User Workload Report − Shows the time estimates for all unresolved issues assigned to a user across projects. It helps to understand how much a user is occupied, whether overburdened or has less work.
Version Workload Report − Displays how much outstanding work is remaining per user and per issue. It helps to understand the remaining work of a version.

除了这些之外，还有其他类型的报告通常是饼形图，我们将在后续章节中详细讨论。

In addition to these, there are other types of reports that generally have a pie chart in them, which we will discuss in detail in the subsequent chapters.

JIRA - Workload Pie Chart

工作负载饼图显示一个饼图，其中显示了某个特定项目的全部问题。让我们了解如何在 JIRA 中使用它。

A workload pie chart displays a pie chart showing all the issues for a specific project. Let us understand how to use it in JIRA.

Generate a Report

为了生成一份报告，用户应遵循以下步骤。

To generate a report, the user should follow the steps given below.

Step 1 − 转至项目 → 选择特定项目。单击菜单左侧的报告图标。转至“其他”部分，并单击工作负载饼图报告，如下面的屏幕截图所示。

Step 1 − Go to Project → choose the Specific project. Click on the Report icon on the left side of the menu. Go to ‘Others’ section and click on Workload Pie Chart Report as shown in the following screenshot.

Step 2 − 选择要为其生成报告的项目或问题过滤器。在统计类型中，选择要根据其生成饼图的字段名称。选择要报告的时间字段，例如当前估计、原始估计或花费的时间。

Step 2 − Select Project or issue filter for which to generate the report. In the Statistic Type, select the field name on which the pie chart will be formed. Select the Time Field to report on as Current Estimate, Original Estimate or Time Spent.

以下屏幕截图显示了如何通过提供详细信息来生成报告。

The following screenshot shows how to generate a report by providing details.

Step 3 − 单击 Next 以生成报告。以下屏幕截图显示了生成报告的外观。

Step 3 − Click on Next to generate the report. The following screenshot shows how the generated report looks like.

JIRA - Created vs Resolved Issues

它显示了在给定时间段内创建的问题与已解决的问题的数量。它有助于了解总体积压是否正在朝着解决方案迈进。

It displays the number of created issues versus resolved issues over a given time-period. It helps to understand whether the overall backlog is moving towards resolution or not.

Generate a Report

为了生成一份报告，用户应遵循以下步骤。

To generate a report, the user should follow the steps given below.

Step 1 - 进入“项目”→“选择特定的项目”。点击菜单左侧的“报表”图标。进入“问题分析”并点击“已创建的问题与已解决的问题报表”。以下屏幕截图显示了如何访问“已创建的问题与已解决的问题”报表 -

Step 1 − Go to Project → choose a specific project. Click on the Report icon on the left side of the menu. Go to Issue Analysis and click on Created Vs Resolved Issues Report. The following screenshot shows how to access the Created Vs Resolved issues report −

Step 2 - 选择需要生成报表的项目或问题筛选器。选择时间段以查看每日、每周、每月、每季度、每年等可用于下拉列表中的报表。输入 Days Previously 字段中的天数以在图表中显示。选择 Yes 或 No 进行累计总计。从下拉列表中选择显示版本为“所有版本”。

Step 2 − Select the Project or the issue filter for which the report has to be generated. Select the time-period to see reports like Daily, Weekly, Monthly, Quarterly, Annually, etc., available in the dropdown box. Enter the number of days in the Days Previously field to show in the graph. Select Yes or No for Cumulative totals. Select Display Versions as All Versions from the dropdown list.

以下屏幕截图显示了如何通过选择不同的可用字段生成报表。

The following screenshot shows how to generate report by selecting different available fields.

Step 3 - 点击“下一步”生成报表。以下屏幕截图显示了生成的报表是什么样子的。

Step 3 − Click on Next to generate the reports. The following screenshot shows how the generated report looks like.

创建的问题以红色显示，而解决的问题以绿色显示。

The created issues are displayed in red, while the resolved issues are in green color.

JIRA - Burndown Chart

显示在给定时间范围内完成冲刺目标的总剩余工作量。它帮助团队管理进度并做出相应响应。此图表是敏捷 - Scrum 方法论的一个重要特性。

It displays the total work remaining to achieve the sprint goal for a given time to sprint. It helps the team to manage the progress and respond accordingly. This chart is an important feature of Agile – Scrum methodology.

Generate a Report

为了生成一份报告，用户应遵循以下步骤。

To generate a report, the user should follow the steps given below.

Step 1 − 转至项目 → 选择特定项目。单击菜单左侧的报告图标。转至敏捷并单击燃尽图。以下屏幕截图显示如何访问燃尽图。

Step 1 − Go to Project → choose a Specific project. Click on the Report icon on the left side of the menu. Go to Agile and click on Burndown chart. The following screenshot shows how to access a Burndown Chart.

Step 2 − 它显示冲刺的燃尽图，例如团队如何向承诺的任务推进。红线显示剩余的工作量，而灰线显示已承诺的任务。与冲刺开始时的承诺相比，团队可以看到他们在冲刺进度方面的状况。用户可以通过从下拉列表中进行选择来更改冲刺和 Y 轴。

Step 2 − It displays the Burndown chart of the sprint like how the team is progressing towards a committed task. The red line displays how much work is remaining, while the grey line shows the committed tasks. The team can see where they stand in terms of the progress of sprint as compared to the commitment at the starting of that sprint. The user can change the Sprint and Y-axis by selection from a dropdown.

以下屏幕截图显示燃尽图在冲刺方面的外观。

The following screenshot shows how the Burndown chart looks like sprint wise.

Step 3 − 在报告的第二部分，它显示数据，如冲刺的开始日期，添加的所有问题，逐日解决了多少问题，问题的故事点是什么，以及逐日剩余多少故事点。此数据用于创建图表。以下屏幕截图显示用于生成图表的数据。

Step 3 − In the second part of the report, it displays data like what is the sprint start date, what all issues were added, day by day how many issues resolved, what story points of the issues are, and day-by-day how many story points are remaining. This data is utilized to create the chart. The following screenshot shows the data that is used to generate the chart.

Note − 与这些报告非常类似，还可以生成其他报告。

Note − Quite similar to these reports, other reports can also be generated.