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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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
Community Members
Community Events
Community Groups

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