受托人领域对许多人来说意味着许多事情。 更好的名称可能是“负责任的用户”。 我与我的客户讨论了3起案件:

A. number of assignees = 0 JIRA has an Allow Unassigned issues option but I discourage use of that because if a work item isn t owned by anyone it tends to be ignored by everyone.

B. number of assignees = 1 The default case

C. number of assignees > 1 Who is responsible for the work item represented by the issue? The best case I ve seen for this is that when an issue can be handled by any one person in a team, so before triage the issue is assigned to everyone in that team. I think a better approach is to create a JIRA user with an email address that sends to the whole team, and assign it to that user. Then a member of the team can have the issue assigned to them in particular.

改变一个受让人案件的历史记录在历史表格中。 该案中没有任何损失。

我常常有一个故事/特征,可以分为多个发展者。 他们将单独指定子公司,但除非有一位领导开发商,否则将让所有参与者都参与。 我实际上没有意识到,我可以做多项任务,因为 t!

我认为,另一个情况是制定合理的方案。

我在寻求解决这一问题的办法时,曾打过这个问题。 自2006年以来 我想这样做,我猜想我把案件算作回答你的问题: 我只真的想要一个受让人,从目前从事某一问题的人的角度来看,但我想追踪一个问题的整个生命周期。 对我们来说,这可以意味着:

1. A support person receives a report from a customer, creates an issue
2. An issue-wrangler reviews the issue to make sure it s valid, not duplicated, has all appropriate details, etc.
3. A developer implements/fixes the issue
4. A tester performs whatever tests are appropriate (in our case, mostly extending our automated testsuite to additionally test the feature/fix)
5. An operations person rolls out the new version to a test environment
6. A support person informs the customer, who does his own tests with the new version in the test environment
7. An operations person rolls out the new version to production

并非所有问题都必然要走到所有步骤中。 有些问题有更多的步骤(例如,第3步至4步之间的法典审查)。 许多问题也将在步骤中出现倒退(发展中国家需要更多信息,我们从第3步到第1或第2步;测试者发现问题,我们从4个到3个)。

在每一阶段,只有一人实际负责任何事情。 尽管如此,仍有一大批人与这一问题有关。 我们使用的跟踪系统很乐意向该问题的先前所有者(作为清单列出)提供容易的变化,但我很想再迈出一步,根据问题的地位,所有者自动回到正确的先前所有者手中。 在第6步,第1步的原始支持者最好与客户联系。 第7步,第5步的同案人最好是受让人。

在“其他”中,虽然我不想让多个受让人参与到一起,但我确实希望有一个“支持受让人”、“受让人”、“受让人”、“检验受让人”等。

我们能够用子公司这样做,我们可以通过在改变地位时人工选择先前的所有人来这样做,但这两种情况都不理想,我认为上述情况是多个受让人具有意义的。

在我的公司中,我们与Nikhil有着类似的工作流程。 我们以鼓动模式开展工作,每个团队都有发展者、测试者和技术作者。

一项发展任务的工作流程是:

发展-研究; 研发审查; 质量测试; PO 接受——和

质量保证任务的工作流程是

QA 撰写测试案例/自动测试-> QA审查-> Done

我们拥有一种工具,由联合执行所取代,使我们能够指派多人执行我们的工作。 关于质量保证任务,我可以很容易地看到,我的团队的其他测试者是否已经做了工作,我需要做下一个步骤。

Without this, I am finding it difficult to quickly identify tasks written by the other tester on my scrum team which are ready for me to review (versus the ones I wrote which they need to review).

自2007年以来,许多人要求有能力拥有多个受让人。 他们有不同的、有效的使用案例。 我感到失望的是,联合执行认证制度的发展小组单方面说,他们没有执行,要求他们重新考虑。

https://jira.atlassian.com/browse/JRA-12841

1. 虽然奶组工作(乳房方案规划等)是把两人都分配到这个问题上的时候了。

2. 任务通过不同的发展步骤(实例:发展、审查、测试)。 每个人都可以负责每一步骤。 尽管这项任务可能正在审查或测试之中,但审查者将难以找到开发者。 发挥不同的作用,帮助组织这项工作。

In our team we usually develop 1 or 2 persons together. Then the code is reviewed by around 2-5 persons in individually or in pairs Then it is tested by 1-2 persons initially, finally tested by the whole team.

目前,我们的制度使我们能够在某个时候指派一人。 这限制了我们追随谁在做什么,却不去看问题。 能够指派多人的灯塔对我们来说是好的。

如果John被指派任务,不能完成这项任务,那么怎么办?

难道你会失去它原先被分配到哪位的历史,以及花费/花费的时间?

In an e-Learning scenario, it makes sense to have an issue assigned to multiple users. Here is what I want to do: I have a storyboard which I want to assign to 3 people at the same time - the animators, the recording artists and the graphic designers. Once these people finish their tasks, they will pass it on to a common reviewer, who will review and close the issue. Graphically it would look something like this:

                   Storyboard
                 /     |     
           graphics animator recording
                      |     /
                    reviewer
                       |
                     done

The three job roles depend only on one storyboard. The compilation of the three have to go to a reviewer. I m racking my brains to get this working on redmine. Haven t found a solution yet.

Got this answer from an Atlassian partner https://www.isostech.com/solutions/ and then later from Atlassian

Objective: Want to set who does the works for each step on an issue

Summary: Use a plugin to copy values from custom fields into the assignee field whenever the issue transitions to a new step.

How: 1. Install the Suite Utilities plug-in: This plug-in adds a bunch of new functionalities to workflows.

3. 您将利用插图向受让人复制一个习俗领域的价值:

2. Create a custom field as single user picker for each role i.e., dev, tester, reviewer to be assigned at different steps in the issue

3. 在问题类型屏幕上添加这些领域

4. Modify the post-function on the workflow transition between each step Add a "Copy Value From Other Field" post function and set it to copy the value from the appropriate user custom field into the assignee field.