I'm trying to set an issues DateTime field at issue creation time based on priority. I've started by using Mizan's script in this question: https://answers.atlassian.com/questions/27052/customize-priority-based-on-custom-field
However I want the datetime to be set more granularly. 1 hour for Critical, 2 Hours for high etc. I've modified the script sucessfully to use my own priorties but I can't figure out how I can set the due date time to be set as well as the date. Is this even possible?
Short answer: No - Due Date is capable to store only date part - see https://jira.atlassian.com/browse/JRA-11770
Longer answer: You can of course create another datetime custom field and use it instead (along with) Due Date in your filters and computations. As various SLA plugins on Marketplace do.
EDIT - Short answer should be (thanks Jamie): Due Date is capable of storing date time (as it is Timestamp), but will be formatted as a date (that JRA-11770 about).
What Jozef said is true, but the actual storage for the duedate is a Timestamp, so date and time. However the UI does not display the time portion.
And in fact in the answer to Graham's other question, someone has provided code that sets the duedate (including hours), even though Graham asked about a custom field. So we're kind of come full circle.
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs