Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,363,862
Community Members
 
Community Events
168
Community Groups

Best practices with issues reviews

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

Comment

Log in or Sign up to comment