You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi, can you provide me with the best practices for using the Due Date field. Specifically, if the Jira board is set up with work phases of "Development" "SQA Testing" "UAT Testing" "Done", should the Due Date be for the Development work only or include the activities associated with all phases through "UAT Testing". Note, the SQA Testing and UAT Testing Phases will be re-assigned to someone else to perform.
Thank you!
Nancy
That is a great suggestion of using custom fields. Thanks so much for your quick response and helpful information.
Apart from your question, you might also consider using a separate "Test" issue type with a different workflow (f.e. pass, fail, re-run) and link the tests to your original story or task. Those issues can have their own due date.
Just wondering: Are you using Jira Service Management for development? (since you posted your question in this group)
Hi Dave, Thank you for the great suggestion. I am not familiar with issue types having a different workflow. I will need to investigate that further.
Thank you,
Nancy
I think the overall due date for an issue should be the 'end' date, but if you're splitting it into smaller tasks that could have an individual due date