The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Best practices with issues reviews

Vinicius Freire da Silva
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!
December 23, 2021

Hello,

 

I'm having some trouble to actually define the best way to track the review (made by other user) of a related issue. I have already tried some ways, and others I also heard of:

  1. Development and review at the same task (logged work would be scrumbled between users on the same issue)
  2. Development as parent issue and review as subtask (some tasks were only development scope and could get to done to fit in the sprint, but the review as subtask would block the transition to done, taking all the task to taken as not completed)
  3. Development and review as independent issues (it's possible to relates them but it's not much clear and the issues wouldn't effectively block or sort of thing)

 

Would you have any suggestion about how to procced and/or point me which one Jira is best suited to handle?

 

Best regards, Vinicius

0 comments

Comments for this post are closed

Community moderators have prevented the ability to post new comments.

TAGS
AUG Leaders

Atlassian Community Events