JIAR usage notes - material

Define issue as Story in JIAR
How to update the time of workitem
After entering the work item, click the + sign next to the event tracking column to

fill in the time
When creating Jira Agile, you are prompted to enter the borad name and project name
. From my point of view, it is recommended that the board name and project name be the same, which is the project name;
some people like to take the board name to XXX_RELEASE 1.0 or something, it is not necessary , you can use VERSION to identify, which should also be the responsibility of VERSION
How to close an Iteration
a. Enter work mode


b. Click complete
Custom workflow

5.1 requirements:
Story: open, resolved, close;
development tasks: open, in-progress, resolved, reopen, close

5.2 Add Story workflow item

summary: Adding workflow is actually sorting out and corresponding to three The relationship between entities, workflow, workflow scheme, project
workflow: the actual workflow defines
the workflow scheme: it is used to associate the workflow with the project ;
it is also the workflow associated issue type (Story, Task... ),
different issues can be associated with different workflows, so a project can have multiple workflow
projects: in the project, set the association relationship with the workflow scheme.

   5.2.1 Add Workflow
       a. Settings -> Questions -> Workflow Enter the Workflow Settings window
       b. Select the jira default workflow option, click Copy

       c. Enter the name and description

       d. Delete the IN-PROGRESS state

e. Get the following workflow

       f. The workflow is currently inactive


   5.1.2 Add workflow scheme item

5.1.2.1 Configure the relationship between workflow and project

        a. Settings -> Issues -> Workflow The scheme enters the workflow scheme setting window
      b. Find the workflow scheme of the corresponding project, click Edit

      c, and add workflow

       to add the previously created story workflow. Note that the story workflow is still inactive at this time;

5.1.2.2 Configuration work Relationship between Flow and Issue Type
a. Click Edit

b. Associate Issue Type

   5.1.3 How to Activate Jira Workflow - Associate Project with Workflow Scheme ➣ Go
to Project Management page, select Workflow -> Click Publish

➣ Click Associate
    ➣ Click Accept 5.1.4 to modify related errors (since the previous project already contains multiple workitems and workflows have been associated,



Change to a new workflow here, which will inevitably cause some problems)
I'm chasing, after the change, all workitems in the project have been emptied. The
root cause
is not emptied, but not visible. Here are the
solutions and steps
Go to Board -> Configuration -> Columns
and find that the previous todo status is wrong, (identified as issue), delete the wrong todo to

modify this problem, and then there is a new problem
this board is unable to use an Agile Simplified Workflow. root cause, because the previous Agile Simplified Workflow was created by default when the Agile Board was created, and the state of TODO needs to be used; the    solution is to make the project inapplicable to the Agile Simplifed Workflow , and the unmapped Status needs to be mapped, and the map after the map is completed. Status is


Later, when creating an issue, it still displays not visible. At this time, select Display.
Interface, interface scheme, question type Interface scheme

6.1 Requirements:
Story and Subtask need to be composed of different field types,
1) Story does not need time tracking,
2) Subtask, time tracking is required for task execution,
so it needs to be used for Story and Subtask Set different (problem interface) interface schemes;

6.2 Interface, interface scheme, question type interface scheme corresponds to logical relationship
    Interface: define which fields of a certain interface constitute the
      interface scheme : a one-to-many relationship with the interface, associated with multiple question operations Type<->Interface group
( The question operation types are divided into three categories: 1. New, 2. Edit, 3. View )
      Question interface scheme: It has a one-to-many relationship with the interface scheme, and is associated with multiple Question Type<-> interfaces Scheme group
(the issue type here indicates Story, new feature, defect... )
      project: The project is associated with the issue interface scheme, which is associated with the issue interface scheme, the interface scheme and the interface .
                 The implication is that it is related to the issue type <-> interface Scenario and Problem Action Type<-> interface
注意，最后一种界面的关联关系是最容易被忽略的，那就是工作流 <-> 界面之间的关系
( 这个解决的是，当问题类型发生工作流流转的时候，需要用到什么样的界面展示，
比如，从Open状态 -> Resolved 状态，填写表单的时候，用什么样的界面方案。)

6.2.1 界面 Screen
   定义某个界面有哪些字段构成
   ➣ 进入问题 -> 界面 -> 界面

   ➣ 点击右上角添加界面按钮，输入界面名称

   ➣ 配置你的界面，添加你想要的字段类型

   ➣ 建议使用复制功能，从 default screen 中直接复制过来修改。
                  至此，Story Screen 创建完成，

                  可见，My Story Screen 并没有关联任何的界面方案，下面，将会介绍如何定义界面方案

6.2.2 界面方案 Screen Scheme
               与界面是一对多的关系，关联多个问题操作类型 <-> 界面组
               ➣ 问题 -> 界面 -> 界面方案，点击添加界面方案

                  选择 My Story Screen，这里是生成默认的问题操作方式 <-> 界面的关联关系。
               ➣ 配置界面方案
                  点击右上角 Associate an Issue Operation with a Screen

                  实现针对不同的问题操作类型关联到不同的界面

                     如图，你可以针对不同的问题操作类型（创建、编辑、查看）指定不同的 Screen

6.2.3 问题界面方案 Issue Type Screen Scheme
               ➣ 点击添加问题界面方案按钮

                  选择之前新建的 My Story Screen Scheme，点击增加
              ➣ 点击右上角 Associate an Issue Type with a Screen Scheme 按钮

                 可见，这里是将不同的问题类型关联到不同的界面方案上
              ➣ 回过头来，查看界面，可以看到已经和 Issue Type Screen Scheme 关联上了


              ➣ 设置完成，可见现在还没有和任何的项目进行关联

                  接下来，演示如何将问题界面方案添加到项目中

6.2.4 项目关联 Issue Type Screen Scheme，并激活不同 Issue Type 关联不同的界面方案
              ➣ 管理 -> 项目

              ➣ 进入界面

              ➣ 点击右上角行为按钮，使用不同的方案

                 选择 My Story Issue Type Screen Scheme

                   由此可见，项目关联上了问题类型界面方案 ( 问题和界面方案的关联 )
                                    和界面方案 ( 问题操作类型和界面的关联方案）
6.2.5 工作流关联界面方案 - 解决工作流变更的时候的界面展示方式



        从界面中可以看到某个界面关联到了某个工作流
问题类型方案

7.1 要求
JIRA 提供的问题类型非常多，新功能、改进、BUG、TASK、Story、Subtask 等等，而我的项目只需要Epic、Story、Bug、Subtask，原因是，只有 Story 有 Story Point，所以我们需要对问题类型方案进行配置。

7.2 配置

系统 -> 问题 -> 问题类型

编辑和关联即可

JIAR usage notes - material

Guess you like