Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

For a story, once QA Sub-task is completed, usually who (Dev or QA) should move the story to done?

Shiva Tripathi
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 14, 2023

-Story is ready for QA

-QA complete QA Sub-task and mark it done

-Story should be moved to done

2 answers

1 accepted

0 votes
Answer accepted
Calvin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 14, 2023

It depends, if your issue is just putting it to "Done" once the Sub-tasks are completed, you could actually automate this with Automation:

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation

But some don't as they like having a user accept/sign off/review before they mark the final story as Done.

This could be a Dev or I've even seen teams ask the designers. Typically I usually see the QA, Project Manager or Business Analyst do it though so that they're aware or happy the item can be closed off, especially if they have customers they ask to check or if they take the story past development (such as into production or customer review etc).

I normally see the dev do it in teams where the dev "owns" the story and is the main "go-to".

Shiva Tripathi
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 14, 2023

Thanks! @Calvin.Appreciate it.

0 votes
Sriram Kancharla August 14, 2023

Sub-tasks should be closed by the person who delivered/worked on it.

Usually subtasks doesnt require any review or approval.

Note that the efforts/time recorded on the task will be rolled-up to the parent.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events