解决了

Jira用于任务和子任务是什么?举个例子来解释下。

  • 2023年7月20
  • 7回复
  • 122的浏览量
anuvip
Userlevel 6
徽章 + 2
  • anuvip
  • 0.8跨声速
  • 20个回复

Jira用于任务和子任务是什么?举个例子来解释下。

图标

最佳答案bhomiajayesh2023年7月21日11:57

\t

What are Tasks and Subtasks in Jira Used for? Give an example to explain the context.<\/p>\t<\/div><\/content-quote>

Jira<\/strong>: One of the most effective and widely used tools in the testing industry is Jira. It enables us to prioritize, plan, and keep track of the numerous issues.<\/p>

One of its features is task and sub-task.<\/p>

Task<\/strong>: In plain English, it refers to the work that needs to be completed. Jira uses the same meaning.<\/p>

Here's an illustration:<\/p>

Let's say a Jira story with the title \"Mobile App - Trade In flow (Apple Watch, iPhone, Mac and iPad)\"<\/strong> has been added.<\/p>

After reading the user story, it becomes clear what things\u00a0<\/strong>need\u00a0to be done by the appropriate parties (such as the developer and QA) in order to finish it. The word \"things<\/strong>\" in this context denotes \"task<\/strong>\".<\/p>

Suppose that after reading the story, the following tasks emerge:<\/p>

Task 1<\/strong>: UI design.
Task 2<\/strong>: API creation.
Task 3<\/strong>: Writing Code.
Task 4<\/strong>: Testing.<\/p>

Therefore, we may say that a task is any action needed to fulfil a user story.<\/p>

Sub-task<\/strong>: A sub-task is a subset of a task, so in order to finish the task, we must first finish every sub-task in the task.<\/p>

In continuation with above example.<\/strong><\/p>

The tester will divide each task\/assignment (logical one) into smaller ones when conducting tests.\u00a0<\/p>

Suppose following sub-task emerges:<\/p>

Sub-task 1<\/strong>: Test the trade in flow for iPhone.
Sub-task 2<\/strong>: Test the trade in flow for Mac.
Sub-task 3<\/strong>: Test the trade in flow for Apple Watch.
Sub-task 4<\/strong>: Test the trade in flow for iPad.<\/p>

Hence, we can say that the task is automatically completed once all of the sub-tasks have been completed.<\/p>

Likewise, once all the tasks are finished, automatically the story gets completed.<\/p>

Thus, in my opinion, the work that must be done in Jira to finish a story is referred to as a task, and the work that must be done to finish a task is referred to as a sub-task.<\/p>","className":"post__content__best_answer"}">

查看原始
质量的主张,一些
What are Tasks and Subtasks in Jira Used for? Give an example to explain the context.<\/p>","quoteUsername":"anuvip","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

7回复

年代

Jira用于任务和子任务是什么?举个例子来解释下。

JIRA问题是一个标准的和独立的问题。但JIRA促进分解成逻辑sub-issues。它可以以多种方式实现。

任务,任务是代表所做的工作需要一天或在一个小块。

子任务——子任务是一项工作,需要完成一个任务。

示例1
我们有一票账户在Salesforce对象创建相关的功能,但有多事情需要做:
——创建字段
——创建福莱希页面
——为必填字段验证
——链接联系人
——地址

所以他们是一个票账户创建对象:

  1. 任务-字段创建分配给资源1
    ——子任务创建所有必需的字段验证——分配给resource1
  2. 任务——链接的联系——分配给资源2
    ——子任务同步字段b / w——分配给资源2
  3. 任务-链接的地址分配给资源3
    ——子任务创建字段类型的地址和同步——分配给资源3


一个例子我们可以把相关的QA -

示例2
我们有一个故事,有一个任务来实现测试或测试文档,测试文档本身是一种活动,可能需要一个星期完成。说,它包括以下几个方面:

测试计划文档,需要2天。测试用例文档- 2天,测试计划评审——½天和测试用例评审- 1天。另外,假设有两个资源。

在这种情况下,我们可以创建一个JIRA的打字任务“测试文档”下,有以下四子任务:

  1. 测试计划文档-资源分配到1
  2. 测试用例文档-资源分配到2
  3. 测试计划评审,分配给资源2
  4. 测试用例评审,分配给资源1

通过这样做,很容易有一个更好的洞察进度任务明智和resource-wise相当父任务分解成子任务。

\t
\t

What are Tasks and Subtasks in Jira Used for? Give an example to explain the context.<\/p>\t<\/div>\t<\/div><\/content-quote>

JIRA issue is a standard and standalone issue. But JIRA facilitates broken down into logical sub-issues. And It can be achieved in multiple ways.

Task- A task is represent the work needs to done by a day or in a small piece of time.

Sub-task- \u00a0Subtask is a piece of work that is required to complete a task.

Example 1
We have a ticket related to a functionality Account Object creation in Salesforce, but there is a multiple things needs to be done:
-\u00a0 Create fields
-\u00a0 Create Flexi Page
-\u00a0 Put Validation for mandatory fields
-\u00a0 Link of contacts
-\u00a0 Addresses<\/p>

So Their is a ticket for Account Object creation:<\/p>

  1. Task - for fields creation\u00a0\u2013 assigned to resource 1
    \t\u00a0 - Subtask for validation creation for all required fields\u00a0\u2013 assigned to resource1<\/li>\t
  2. Task - Link of Contact\u00a0\u2013 assigned to resource 2
    \t\u00a0 - Subtask to sync fields b\/w them\u00a0\u2013 assigned to resource 2<\/li>\t
  3. Task - Link of Address\u00a0\u2013 assigned to resource 3
    \t\u00a0 - Subtask to create type of addresses and syncing of fields\u00a0\u2013 assigned to resource 3<\/li><\/ol>


    One more example we can put related to QA -

    Example 2
    We have a story and for that we have a Task to achieve Testing or Test Documentation, Test documentation by itself is an activity that might take a week to finish.\u00a0 Say, it involves the following aspects:

    Test plan documentation which takes 2 days. Test case documentation \u2013 2 days, Test plan review \u2013 \u00bd day and Test case review \u2013 1 day. \u00a0Also, assume that there are 2 resources.<\/p>

    In this case, we can create a JIRA issue of the typing task for \u201cTest documentation\u201d and have the following four subtasks under it:<\/p>

    1. Test plan documentation \u2013 assigned to resource 1<\/li>\t
    2. Test case documentation \u2013 assigned to resource 2<\/li>\t
    3. Test plan review- assigned to resource 2<\/li>\t
    4. Test case review- assigned to resource 1<\/li><\/ol>

      By doing so, it is easier to have a better insight into the progress task wise and resource-wise by breaking a sizeable parent task into sub-tasks.<\/p>","quoteUsername":"Shelja Sharma","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

N

Jira有多个问题跟踪所有的工作项目。任务和子任务其中之一。任务是一个独立的问题类型,而子任务需要父母的问题。

任务,一个任务是一个独立的问题在Jira类型。任务允许您快速描述和划分的工作需要由您的团队——所有在一个单一的故事。

例如,故事为现有的应用程序开发新特性。得到这个功能你可以发布个人的发展,测试和发布任务。

子任务,当t问太大而复杂的任务可以被分解成逻辑sub-issues Jira称为“子任务”。

示例1
我们有一个故事相关的数据迁移在Salesforce对象从不同的组织

我们进一步分为以下任务


——布局的对象
——创建的对象
——字段字段的权限

进一步的任务划分为子任务

布局的对象——子任务QA测试场景和测试用例创建和测试执行

Jira have multiple\u00a0issues to track all the work of project.\u00a0Task and Subtask one of them.\u00a0<\/span>Task is an independent issue type while a Sub-task needs a parent issue.<\/p>

\u00a0<\/p>

Task -\u00a0A task is a\u00a0standalone issue type in Jira.\u00a0<\/span>Tasks allowing you to quickly describe and divided\u00a0the work that needs to be done by your\u00a0team \u2013 all in a single Story.<\/p>

For example-\u00a0<\/span>Story to develop a new feature for an existing application. To get that feature released you could have individual pieces of the development, testing, and release as tasks.\u00a0<\/p>

\u00a0<\/p>

Sub-task - When t<\/span>ask is too big and complex then the task can be broken down into logical sub-issues known as \u2018Sub-tasks\u2019 in Jira.<\/p>

\u00a0<\/p>

Example 1
We have a story related to a data migration of Object from different org in Salesforce\u00a0<\/p>

We further divide into below task\u00a0<\/p>


-\u00a0 Layout\u00a0of object
-\u00a0\u00a0Create fields of object
-\u00a0 Field permission of\u00a0fields<\/p>

\u00a0<\/p>

Further divided task into sub-task<\/p>

\u00a0<\/p>

\u00a0 Layout\u00a0of object - Subtask for QA\u00a0Test Scenario & Test Case Creation and\u00a0Test Execution
\u00a0<\/p>","quoteUsername":"Nareshnathawat99","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

年代

在我看来,Jira用来跟踪许多不同类型的问题。其中的一个类型“任务”。
一个任务可以被定义为一个小的,截然不同的、独立的作品。
子任务是孩子下创建一个父任务的问题。

例如,让我们考虑一个场景:一个团队正致力于一个用户故事,需要配置后端设置。在开始工作之前对用户故事,将会创建一个任务处理后端配置。

任务:配置后端设置

在这个配置任务,需要关注几个具体方面。例如,切换按钮,设置预定义的税率,指定国家的名字,和配置正确的服务器和地区。所有这些可以进一步分类的子任务。

子任务1:切换按钮
子任务2:设置预定义的税率
子任务3:指定国家名称
子任务4:配置正确的服务器和地区

利用子任务,团队可以有效地解决每个不同方面的主要任务,导致用户故事的成功实现。

In my opinion, Jira is used to track many different types of issues. One of those types is 'Task'<\/strong>.
A Task Can be defined as a small, distinct, independent piece of work.
Subtasks are child issues that are created under a parent task.
\u00a0<\/p>

For instance, let's consider a scenario where a team is working on a user story that needs configuring backend settings. Prior to commencing work on the user story, a Task will be created to handle the backend configurations.
\u00a0<\/p>

Task: <\/strong>Configure Backend Settings<\/p>

Within this configuration task, several specific aspects need attention. For example, toggling a button, setting predefined tax rates, specifying the country name, and configuring the correct server and region. All these can be further categorized a sub-tasks.
\u00a0<\/p>

Subtask 1:<\/strong> Toggle the button
Subtask 2:<\/strong> Set predefined tax rates
Subtask 3:<\/strong> Specify the country name
Subtask 4:<\/strong> Configure the correct server and region
\u00a0<\/p>

By utilizing subtasks, the team can efficiently address each distinct aspect of the main task, contributing to the successful implementation of the user story.<\/p>","quoteUsername":"Sparsh","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

mmario.ffrohlich
Userlevel 2
徽章 + 2

从我自己的经验,我们(在公司我目前工作)同意,我们将使用任务描述和跟踪的发展更大的特性,我们使用子任务跟踪小块的特性。

例子:

任务:

创建一个新菜单项和相关表单,将用来跟踪商务旅行

子任务:

  1. 创建菜单项,应仅管理员可见
  2. 创建具有以下特征的形式…
  3. 开发一种方法,XYZ
  4. …
  5. …

我们发现构建这样的工作给了我们最好的概述功能正在开发,同时它能帮助我们测试人员应对每时间特性的一部分。当然,任务不考虑完成,直到所有子任务完成,直到最后一个测试周期是成功完成

这是一个我,马里奥!
From my own experience, we have (in a company I\u2019m currently working at) agreed that we\u2019ll use tasks to describe and track the development of a larger feature while we use subtasks for tracking smaller chunks of said feature.\u00a0<\/p>

\u00a0<\/p>

Example:<\/em><\/u><\/p>

Task:\u00a0<\/strong><\/em><\/u><\/p>

Create a new menu item and related form that\u2019ll be used to track business trips<\/p>

\u00a0<\/p>

Subtasks:<\/strong><\/u><\/em><\/p>

  1. Create the menu item that should be only visible to admins\u00a0<\/li>\t
  2. Create the form that has the following characteristics\u2026<\/li>\t
  3. Develop a method that will do XYZ<\/li>\t
  4. ...<\/li>\t
  5. \u2026<\/li><\/ol>

    We found that structuring the job like this gave us the best overview of the feature being developed, while it helps us testers to tackle one part of the feature per time. Of course, task isn\u2019t considered complete until all the subtasks are finished and until the final testing cycle is successfully\u00a0completed\u00a0<\/p>","quoteUsername":"mmario.ffrohlich","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

年代

。

.<\/p>","quoteUsername":"Shelja Sharma","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">
B
Userlevel 5

Jira用于任务和子任务是什么?举个例子来解释下。

Jira:一个最有效的和广泛使用的工具在测试行业Jira。它使我们能够优先考虑、计划和跟踪的众多问题。

它的特点之一是任务和子任务。

任务:说白了,它指的是工作要完成。Jira使用相同的含义。

这里有一个例子:

假设一个Jira的故事的标题“移动应用程序——贸易流(苹果手表,iPhone, Mac和iPad)”已被添加。

阅读用户故事之后,就清楚的事情需要通过适当的政党(如开发人员和QA)为了完成它。这个词的事情“在这种情况下表示”任务”。

假设在阅读这个故事,以下任务:

任务1:UI设计。
任务2:API创建。
任务3:编写代码。
Task 4:测试。

因此,我们可以说任何行动任务需要完成一个用户故事。

子任务:一个任务的子任务是一个子集,所以为了完成这项任务,我们必须首先完成每个子任务的任务。

继续上面的例子。

测试人员将每个任务/赋值(逻辑)划分为较小的时候进行测试。

假设子任务后出现了:

子任务1:测试iPhone的贸易流动。
子任务2:测试Mac的贸易流动。
子任务3:测试苹果的贸易流的手表。
子任务4:测试iPad的贸易流动。

因此,我们可以说,任务是自动完成一次所有的子任务已经完成。

同样,所有的任务都完成后,自动完成的故事。

因此,在我看来,Jira完成的工作必须完成一个故事被称作一个任务,而必须完成的工作任务被称为子任务。

\t

What are Tasks and Subtasks in Jira Used for? Give an example to explain the context.<\/p>\t<\/div><\/content-quote>

Jira<\/strong>: One of the most effective and widely used tools in the testing industry is Jira. It enables us to prioritize, plan, and keep track of the numerous issues.<\/p>

One of its features is task and sub-task.<\/p>

Task<\/strong>: In plain English, it refers to the work that needs to be completed. Jira uses the same meaning.<\/p>

Here's an illustration:<\/p>

Let's say a Jira story with the title \"Mobile App - Trade In flow (Apple Watch, iPhone, Mac and iPad)\"<\/strong> has been added.<\/p>

After reading the user story, it becomes clear what things\u00a0<\/strong>need\u00a0to be done by the appropriate parties (such as the developer and QA) in order to finish it. The word \"things<\/strong>\" in this context denotes \"task<\/strong>\".<\/p>

Suppose that after reading the story, the following tasks emerge:<\/p>

Task 1<\/strong>: UI design.
Task 2<\/strong>: API creation.
Task 3<\/strong>: Writing Code.
Task 4<\/strong>: Testing.<\/p>

Therefore, we may say that a task is any action needed to fulfil a user story.<\/p>

Sub-task<\/strong>: A sub-task is a subset of a task, so in order to finish the task, we must first finish every sub-task in the task.<\/p>

In continuation with above example.<\/strong><\/p>

The tester will divide each task\/assignment (logical one) into smaller ones when conducting tests.\u00a0<\/p>

Suppose following sub-task emerges:<\/p>

Sub-task 1<\/strong>: Test the trade in flow for iPhone.
Sub-task 2<\/strong>: Test the trade in flow for Mac.
Sub-task 3<\/strong>: Test the trade in flow for Apple Watch.
Sub-task 4<\/strong>: Test the trade in flow for iPad.<\/p>

Hence, we can say that the task is automatically completed once all of the sub-tasks have been completed.<\/p>

Likewise, once all the tasks are finished, automatically the story gets completed.<\/p>

Thus, in my opinion, the work that must be done in Jira to finish a story is referred to as a task, and the work that must be done to finish a task is referred to as a sub-task.<\/p>","quoteUsername":"bhomiajayesh","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

anuvip
Userlevel 6
徽章 + 2

所有的回答都好,这是一个可以和Shelja之间的战斗。这两种解释的例子,但可以给出的答案是更接近现实,Shelja给出的答案是更普遍。

由于可以回答是更真实,我选择他作为最好的回答。

质量的主张,一些
All Answers are good and it was a close fight between Jayesh and Shelja. Both explained with examples, but Jayesh\u2019s answer was more near reality and Shelja\u2019s answer was more general.<\/p>

Due to Jayesh\u2019s answer is more real, I chose his\u00a0as best answer.<\/p>","quoteUsername":"anuvip","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote & Reply","Share":"Share"}}}">

回复


Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">

金宝搏app官网下载
Baidu