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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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,465,875
Community Members
 
Community Events
176
Community Groups

Best Practices for Using Due Date

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 

3 comments

Fabian Lim Community Leader Jan 11, 2022

Hi @Nancy Arnold

I would use different customfields to ensure that they are unique for your testing purposes.  For us, we only use "Due Date" as the date when the issue should be completed by.  But you can repurpose it to whatever you want.  

The other issue is that it's a system field, so you should not modify it.

I hope this helps.

That is a great suggestion of using custom fields.  Thanks so much for your quick response and helpful information. 

Dave Mathijs Community Leader Jan 13, 2022

Hi @Nancy Arnold

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

Hi @Nancy Arnold 

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

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events