<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>Inflectra Customer Forums: Custom Property Date Fields not using SpiraTest default Time Zone (Thread)</title><description> Version 5.0 SpiraTest seems to have a conflict with how it reports custom property date fields.  The XML output in the Custom_XX field shows the correct date value.  However, the CustomProperty (Alias) fields show the data value in what appears to be GMT.     First - why are the two date values different? And how do I correct the problem so all Date fields use the SpiraTest default time zone when generating reports??? </description><language>en-US</language><copyright>(C) Copyright 2006-2026 Inflectra Corporation.</copyright><managingEditor>support@inflectra.com</managingEditor><category domain="http://www.dmoz.org">/Computers/Software/Project_Management/</category><category domain="http://www.dmoz.org">/Computers/Software/Quality_Assurance/</category><generator>KronoDesk</generator><a10:contributor><a10:email>support@inflectra.com</a10:email></a10:contributor><a10:id>http://www.inflectra.com/kronodesk/forums/threads</a10:id><ttl>120</ttl><link>/Support/Forum/spiratest/issues-questions/1635.aspx</link><item><guid isPermaLink="false">threadId=1635</guid><author>Brian Stigler (bkstigler@usa.net)</author><title>Custom Property Date Fields not using SpiraTest default Time Zone</title><description> Version 5.0 SpiraTest seems to have a conflict with how it reports custom property date fields.  The XML output in the Custom_XX field shows the correct date value.  However, the CustomProperty (Alias) fields show the data value in what appears to be GMT.     First - why are the two date values different? And how do I correct the problem so all Date fields use the SpiraTest default time zone when generating reports??? </description><pubDate>Wed, 08 Mar 2017 17:07:10 -0500</pubDate><a10:updated>2017-03-14T13:48:35-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/1635.aspx</link></item><item><guid isPermaLink="false">messageId=2935</guid><author>Jim R (donotreply5@kronodesk.net)</author><title> Hi Brian  Yes you are correct we have a bug in v5.0 due to it overcorrecting the dates. We have fix</title><description> Hi Brian  Yes you are correct we have a bug in v5.0 due to it overcorrecting the dates. We have fixed it in v5.2 being released in April.  Regards  Jim </description><pubDate>Tue, 14 Mar 2017 13:48:33 -0400</pubDate><a10:updated>2017-03-14T13:48:33-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/1635.aspx#reply2935</link></item><item><guid isPermaLink="false">messageId=2936</guid><author>Jim R (donotreply5@kronodesk.net)</author><title> Hi Brian  Yes you are correct we have a bug in v5.0 due to it overcorrecting the dates. We have fix</title><description> Hi Brian  Yes you are correct we have a bug in v5.0 due to it overcorrecting the dates. We have fixed it in v5.2 being released in April.  Regards  Jim </description><pubDate>Tue, 14 Mar 2017 13:48:35 -0400</pubDate><a10:updated>2017-03-14T13:48:35-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/1635.aspx#reply2936</link></item></channel></rss>