How to assign a person for a story?

Question

This is very difficult to assign one person to a story.

because finish a story maybe need team work.

Example:
Story : As a user,I want to login ,so that I can enter this system.

but this story need front-end engineer,back-end engineer,designer to finish.

So how to assign a person for a story?

Ste Wright · Answer

Hi @steven cheng

You could create custom fields to hold the other user's names - such as

* User Picker (single user): Have one field per role included on the Story
* User Picker (multiple users): One field which holds all users required

You can access custom fields as a Jira Admin, via: Jira Settings > Issues > Custom Fields

See more on creating custom fields on this page

---------------

However, these are the options I use most often for this specific scenario:

* Sub-Tasks: Create sub-tasks, slicing the work into the unique chunks each user looks after. Assign each sub-task to one of the users - and for reporting, add a component to each sub-task identifying the type of work it covers. See more on components on this page.
* Assignee: Just change the Assignee depending on who is working on the issue.* If you have a linear workflow, you could consider auto-assigning / unassigning the issue automatically depending on the workflow step (eg. New > In Design, assign to Designer).
* This can be done using workflow post-functions or Automation for Jira

---------------

^ I prefer the last option.

This is because I find that a Story can pass between a number of users throughout its lifecycle, and a lot of the work team members do is very co-dependent. It can also skip team members - not every Story needs every type of specialisation applied to it.

That can mean that even when breaking work into sub-tasks, one sub-task can be assigned to more than one user between creation and done.

We often just ask our teams to change the Assignee if they begin working on an issue - or if they hand-off the issue to another team member. If we're unsure who is working on an issue, we bring it up at stand-up.

If more than one user is working on the issue (eg. Pair Programming), the Assignee will be the team member most responsible for delivery at that point.

---------------

So I would consider how you work alongside what you need to visualise, when deciding the best approach.

Ste

Mehmet A _Bloompeak_ · Answer

Hi @steven cheng ,

You can create a custom field(with name 'developed by' or 'team members') of type multi-user picker and add all members who will work on the story.

Nic Brough -Adaptavist- · Answer

All issues have an assignee field (unless you deliberately disable it).  This is the person who is currently responsible for getting the issue dealt with.

So use that field to hold who the current responsible person is.

If you have others that might be useful to know about, draw them in as assignees on sub-tasks, or name them as watchers, or add them to custom fields to show that they have an interest.