Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Best practices with issues reviews



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



Log in or Sign up to comment

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you