nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why a JIRA Story can't be rotated among team members?

V B_fo4l0f

Today, I challenged my Agile Coach stating A JIRA story can't be assigned to multiple people in a team. I also showed some evidence from this group that JIRA story can be owned by only one person in a team, however it can have multiple tasks.

But, while I say NO I don't have a justification as why a story itself can't be rotated between Developer, Tester and Reviewer.

Any help on the justification please?

Accepted answers

Rilwan Ahmed

Hi @V B ,

Welcome to the community !!

The assignee field in Jira is intended to show you who is the person currently responsible for getting the ticket done. That should only ever be a single person - at a given point of time.

Breaking up a story into sub-tasks for different assignees works well for some processes.

All comments

Rilwan Ahmed

Hi @V B ,

Welcome to the community !!

The assignee field in Jira is intended to show you who is the person currently responsible for getting the ticket done. That should only ever be a single person - at a given point of time.

Breaking up a story into sub-tasks for different assignees works well for some processes.

V B_fo4l0f

Thank you @Rilwan Ahmed . So, you suggest a Story can be rotated among Developer, tester and BA or PO if required?

Yes, I get the point it's only one person at any given time.

Rilwan Ahmed

Yes @V B , Only requirement is, all these users should have Assignable User permissions.

V B_fo4l0f

Yes they do have permission. With further research I learnt it's a best practice not to rotate story to multiple users but if needed can be done.

Thank you @Rilwan Ahmed

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software