way to make list of tasks(tickets) that are planned to a user ?

[Bala]

Im a QA lead, We use to assign the ticket to devloper and no field for QA who test it.

My problem is, i have assigned(not assigned in jira) list of ticket to a QA team member in an priority order.

I would like to do this in JIRA (similar to kanban board) where it will have column as name of each team member and i need to list the tickets in an order i want them to take one by one.

Please suggest the best way.

[John Funk · Accepted solution]

Hi @Bala 

There are probably a couple of ways to accomplish this. One is to create a custom field for QA Tester or QA Analyst as a single user picker field. Then you can populate that field at any time. 

Then I would create a board using a filter where that custom field is not empty. Then on that board, you can drag the cards into the correct order you want them tested when they are ready. 

[Bala]

Thanks.
If i do so, will show up here in swimlanes ?

[John Funk]

You can base the Swimlanes on JQL and do that, sure. 

[Bala]

I created a custom field as QA analyst but i don't see that in Swimlanes. Am i missing anything @John Funk 

This is my JQL

project in (IOSVII, COM, ADVII) AND status in ("Ready for QA","QA Started") AND type in (Epic, task) and "QA Analyst[User Picker (single user)]" in (557058:2f797bb3-c8f9-4ef6-85a9-23da3dd584188) ORDER BY Rank

Definitely i want my custom field in Swimlane. Otherwise this kanban board will not be so useful to me. 
Please help further.

[John Funk]

Have you tried that as a regular filter? And do issues get displayed? 

[Bala]

Issues are showing up in Board but it still looking for status based. If the board will be work based on my new custom field then it will be great. I will just assign QA to the ticket then it will list here accordingly.

.

[John Funk]

Columns are always status based and should be. You can do swimlanes to group issues, but those are horizontal lanes and not columns. 

[Bala]

I used the swimlane as query and achieved it.

As shown in the figure, created query for each tester and configured 2 column "Ready for QA" and "Qa started". So, i have assigned tickets to each QA.

Thank you so much for the help and guidelines @John Funk @Diogo Teles 

[John Funk]

Great! Looks good. 

[Diogo Teles]

Hi @Bala ,

Let me summarise the question so you can tell me if I understood it correctly. 

1. You have Jira issues (ticket) to a developer but also want the same ticket to be associated with the QA tester, a different person.
2. Do you want a board that shows your QA testers what they have to test in a way that only shows each tester their work?
3. On that board, the cards must be organised so that the card on top is always the next job for that QA tester.

Is this correct? If not, could you help me correct my interpretation?

Thank you!

[Bala]

Yes @Diogo Teles Correct.

[Diogo Teles]

Brilliant, thanks for confirming @Bala 

There are different ways to tackle this. This is how I would approach the situation. I assume your issues exist in a Jira Software project, and you use the Kanban project type. 

Here are the steps

1. Assign work to the testers by creating a subtask to the main ticket. For example, if the ticket is a Task to deliver feature A, create a sub-task on it called QA Feature A. Set the assignee of the sub-task to be the QA tester
2. Set a due date to the sub-task, and if required, set a priority (you may need to add those fields to the sub-task screen, and you need the schedule issues permission in that project)
3. Create a new board in the project with a descriptive name (e.g. QA Board)
4. Configure the board filter query only to capture subtasks of the project assigned to your QA group members (e.g. AND membersOf("QA") ). You can refine this query further to make the board's scope more accurate; for example, add summary ~ "QA", which will only capture subtasks with QA in the summary. 
5. In your board filter query ORDER BY the way you want tickets to appear on the board for each user, for example, ORDER BY priority, duedate
6. Share the board with the team and train them on how to use it

Your testers can go to this board and click the "Only my issues" subfilter. This will show them only their issues (you can also force this in the board filter query by adding the currentUser condition, but I would not do that)

Once they click that subfilter button, they will show a board with columns for the subtask workflow (e.g. to do, in progress done) where the top card of the to-do list will always be the next job to do, based on the criteria you defined (priority and due date).

If you want the order of work to be different, all you have to do is adjust priority.

[Bala]

Thanks for the help .
Creating subtask is an additional work to QA. We already dealing too much.

What i was thinking is, Creating a board with column name with "Tester's name" and list it.

The problem is, each column requires unique "Status" but i want to use the status called "Ready for QA" in each column.

Is there way to achieve something like this @Diogo Teles  @John Funk 

Above approach will help me to handle the QA's who are working on multiple projects.

[Diogo Teles]

Hi @Bala ,

As you correctly said, columns need to be matched to statuses. 

Have you considered using a filter instead of a board? You may achieve a similar or even better result.

Now that you already have a custom field, you can add it to your issues and select for each issue the QA tester.

With that done it is a simple matter of creating a filter to show you work for each tester.

For example, assuming here the custom field is user picker type and called "QA tester", the issuetype is Story, the project key is PRJ, and you have a Group called "QA Testers"

project = PRJ AND issuetype = Story AND "QA Tester" is not EMPTY AND "QA Tester" IN membersOf("QA Testers") ORDER BY "QA Tester", Priority, duedate

Essentially, this query retrieves all the stories in the "PRJ" project where the "QA Tester" field is populated and the assigned tester is a member of the "QA Testers" group. The results are sorted first by the assigned tester, then by priority, and finally by the due date.

This query helps to create a filter that shows the work of each tester involved in testing the stories within the specified project.

Save the filter, select the columns that you want to see, and if you want email updates you can even subscribe to it.

Once again, there are many ways to do this. One of them is not having assignees mapped to board columns though, that is not currently possible in Jira.

[Bala]

Filter was my last option.

My expectation is, if its board it will give priority order. Thanks for you help and advice.

Ill use filter for now.