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
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
I think Jacob was asking why you would want to do this?
Of what possible use is making a comment on an issue at a specific time? If it's about an issue being left ignored for too long, then a comment isn't a good way to remind people about it, you should be using reporting, escalations or subscriptions to tell people actions are needed.
For future shipping only. This functionality exists in outlook and slack, for example. Sometimes we are working during non-business hours and we have a response to a ticket, but it's only good to send that response at the next business time. I just have a comment to send, but it's not the best time.
Or you could just make the comments when you feel the need to, and leave it for people to pick up when they're ready.
Announcements about releases, and shipping communications are not what Jira is for, you should be doing them in systems that are able to talk better to a customer.
Some of your customers would be delighted to get told "we did X" as soon as you know you have. Most won't read it until they're ready. Scheduling this sort of stuff (in an issue tracker) is (probably totally) pointless, there's no real use-case for it. Plenty of other good places to do it, of course.