A fix for this issue is available in Confluence Server and Data Center 8.5.18. Upgrade now or check out the Release Notes to see what other issues are resolved.

"Me too" - we have a "date and time scheduled" field for a certain type of ticket, and I cannot show the time on the Confluence view of the ticket list.  It makes it pretty much useless to show it on Confluence at all.

The workaround of changing display of ALL date fields is ridiculous, this needs to be something configurable in the macro on a per-field basis.  

Hit this bug.......user complaint here

It actually show correct date/time one Issues list.......but Confluence actually displays its as date

Congrats Atlassian.........This bug have surpassed 10 years!....how they hell can you categorize this as "Major - Severity 2"......but still not solve it after 10 years!! .....and have it in a status "Short term Backlog" since September 2021!?!......or even comment on it.....This is just plain ridiculous.........hard to take you serious

I echo everyone else's' concerns, but seems that this has been open for 10 years, not sure anyone is monitoring it. If so would be great to hear about its potential deployment

Date/Time is urgently needed for reporting - kinda mandatory functionality.

I agree that this feature is so such a basic requirement.  Most companies want to use Jira to track issue. Implement intelligent workflows with accurate time stamping.  Confluence is then the best way to share status reports, as graphs etc.  This is impossible in any operational environment where we are depending on showing time as a metric of response times.

It decreases the value of having Jira and Conlfuence for ITSM as it limits the options in which they can be combined, becoming ineffektive to f.i. track and report on Tickets, create and manage KnownErrod DB´s, Operations Calendars etc.

This bug has an impact on my Management Dashboards as well. I do want to show the time of some issues, but I'm unable to do so.

I hope you can priorize as soon as possible :-/

The problem still persists in Confluence 7.19 with JIRA 8.22. 

If a BUG in the Short Term Backlog has already been there fo more than a year, I don't even want to know how long it takes for a BUG in the Long Term Backlog.
In addition, since version 7.19 there have been some other major bugs with the JIRA issue macro in confluence. It would be nice if the quality of the product would also increase with the rising prices. At the moment it's going in the wrong direction

This bug has impacted our Production operation where the timestamp is critical for the timeline reporting. Please fix this bug as soon as possible.

For such a simple bug fix, Jira takes years!

This is not an enhancement request. I might have to reconsider our strategy to use Jira if such simple bugs are not going to get fixed.

For a company that develops an issue tracking platform, they sure don't seems to be using it themselves.

For the record, the workaround I came up with for a user who encountered this issue was as follows:

1. Add a custom field of type "Scripted Field" (requires Script Runner) to represent the time component of a Date/Time field.
2. Set the script to have it extract the time component of the source field.  For example:

   (getCustomFieldValue(14932) as Date)?.format("hh:mm a") 

3. Add the "time" field to the view screen for any relevant issues.
4. Add the "time" field to the JIRA macro output in Confluence.

It's a little ugly, and I know Script Runner isn't free anymore, but it got the job done. The scripted field seems to stay in perfect sync without the need for additional events or listeners or post functions.

We have several fields in Jira that we pull into Confluence for reporting and documentation purposes.  It minimizes are ability to run any analysis (through Jira macro) based on time (hhmm).   This is very limiting for us and has been for years.   I hope we can see this fix soon!

This should seriously require further consideration as many reports are generated by my company out of Jira and we are always lacking this time to resolution or any time related fields. It is very disappointing that this has not been rectified years on. Not many people may bother to log it knowing there would never or ever be a fix but find other solutions which is not something we would like to happen. We do hope that a solution would be found to rectify this issue.

Team,

I have raised this concern through Atlassian community chat assuming I will get some reply but got the answer stating to  click "Vote" for this issue. Hence doing it now. Not sure whether product support team will develop this feature. Being around 6 years old issue I dont know whether it will complete.

But really it is needed one. In fact date value along with time is correctly displayin in the Jira then why not same cant be display in the confluence.  Anyhow expecting this feature as earliest.

We heavily use the Jira macros in Confluence to display dashboards and issue summaries for internal and external business teams (and part of our business is helping our customers do the same. Time management and schedule reporting is a major part of this, and excluding times from this view is definitely a problem.

HI Mark.Mackay168676824, there was only one vote on the suggestion you mention, as it seems that people have found and voted on this bug describing the same issue.
Due to the apparent lack of interest on that issue it was closed without review. The fact is it was a duplicate and could have been closed as such years ago.

Cheers,
Adam - Confluence PM

Limited demand????  We run into this daily and I have to explain it all the time to people this is a problem with Atlasssian and not our reports.  So we manually need to add the time, but the value of Confluence reports is time reports so people then wonder why we don't move the reports to another system and due to a simple time field.  I was literally showing a report that had these problems to executives yesterday and had to explain it was a Confluence limitation. 

Can someone reach out to me so I can explain how this impacts us before you write if off as "limited demand".  We had a similar problem with another feature for "priorities for projects" and I was happy this was finally implemented but the demand had to be close to a public outcry before Atlasssian took it seriously . https://jira.atlassian.com/browse/JRASERVER-3821   There should be a better way.

Just made the following comments on CONFSERVER-33960 and CONFCLOUD-33960, with respect to this issue, where i found this comment:

abarnes@atlassian.com added a comment - 18/Aug/2016 5:25 AM
Thank you for raising this issue. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. If you are able to describe your higher-level goals we may be able to provide better guidance. Thanks again.
Regards,
Confluence Product Management

My response?

Semi-politely, this response from Atlassian is absurd.

You're saying a field in Jira which allows you to select a DATETIME value, can't then be displayed in another Atlassian product in a way that shows the TIME part ... using a Macro that is supposed to allow embedding Jira information into Wiki pages?  

The only change you'd probably need to make is to modify a format string in the code to display the missing information. This is the really slack – and the issue has been open since at least 2012 (https://jira.atlassian.com/browse/CONFSERVER-26381).  Incredibly disappointed in Atlassian.

Just ran into this as well trying to build a report for management. Voted and watching.

Created in 2012 and this is STILL a problem? It looks like Confluence is just using the wrong format (Date Format vs Date Time Format).

Is there any progress on this to report?  Thanks!

We still really need it too! Our workaround is lame. We have to put the time in comments.

Dave Dibert
AVP, Global Technical Support
BroadSoft, Inc.

@slancashire we discussed this at summit and it is really needed by our organisation

I've created a support requst CSP-174768 at Atlassian Support.
Hopefully sombody now notice the problem.

We also use a Confluence page for Exec reporting and we need to keep manually updating a comment field with time since only the date shows. This is time consuming and error prone.

Seeing other users feedback in this forum is helpful, but from an end-user perspective, votes and priority don't seem to work for Atlassian features. I'm wondering what else can be done to escalate. Thanks for considering this.

Dave Dibert
Sr Director, Global Technical Support
BroadSoft, Inc.

We have 2000 user licenses JIRA 6.3.9 + Confluence 5.9.7 (server/on premise)
I was really annoyed that such a basic integration for 'Confluence <-> Jira is not working and see now that it's a known major ranked bug issue since years and still is "unassigned".
For us this is a severe problem becuase we cannot properly display process KPI to management!

Please resolve the issue and don't tell customers to play around with sytem settings for a workaround.

Thanks & best regards
Michael Kulas
CIO

Please add Veronika Kuzmina, one of our developers, to the watch list.