Transition Date/Time Field (JIRA Misc Custom Fields) is not showing time

I successfully setup transition date/time field, I thought.

but it's not showing time, only date.

How can I fix this? 


I can see time on view screen(detail view of issue), but it's not showing on issue list or exported excel file. 

1 answer

This widget could not be displayed.

The display of transition date/time fields respects your general JIRA settings for the display of dates (e.g. "created" field). You can change it in JIRA's advanced settings.

As for the Excel export, it's an old JIRA bug...

Thanks for your reply,

in my JIRA's advanced settings, I think it has no problem. dd/MMM/yy %d/%b/%y %d/%b/%y %I:%M %p dd/MMM/yy h:mm a


Could you please recommend change required for the settings? 


edit/view screen (created date also with time)

image2016-10-4 10:23:20.png

issue list

image2016-10-4 10:23:7.png

I'm not sure what the problem is. As you can see, all date/time values, including for system fields, are shown as just the date in the issue navigator. That's a standard JIRA feature.

If you really need date and time, and you can live without sorting on that field (you can always display both versions), you can create a Calculated Text Field with the format you want.

Or you can raise a feature request on for the Transition Date/time fields to support custom formatting for issue view and issue lists - I believe it could be implemented fairly easily (just like for the Calculated Date/time fields).

OK. I just expected that Transition Date/time is showing time on the issue list as well. 

I will raise a feature request. thanks for you help.

It's said to be pretty much useless raising a Feature Request with Atlassian if there's already a commercial plugin that does the same thing. People selling expensive plugins are an important part of the Atlassian ecosystem.

Except the feature request was raised with Innovalog wink

I do understand your point @David Skreiner. My company is also using certain paid plugins for JIRA and Confluence. If the plugin provide functions we need, we're going to pay, of course.

In this case we have great free plugin and if we have enough time to wait until feature is provided, then why not? if we cannot wait any longer, we're going to buy other plugin. 

Also I think any suggestion can be considered, and then maybe developer can drop it. I am not forcing anything. 

I think this is also important for the ecosystem as well. 

thanks for your suggestion smile 

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

255 views 5 0
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you