I am using SOAPpy (a python SOAP module) to add new versions to a jira project. I have a problem where the release date I specify for the new version is not the one that ends up being set for the new version. The day is one less than what I specify. For example, if I specify a release date of 2008-12-25, the new version will have a release date of 2008-12-24. Here is an example of the python code:

soap = SOAPpy.WSDL.Proxy(soapProxyURL)
auth = soap.login(JIRA_USER, JIRA_PASS)
versionInfo = {'name' : versionName,
                         'releaseDate' : SOAPpy.dateTimeType(2008, 12, 25, 0, 0, 0, 3, 360, -1)}
soap.addVersion(auth, projectKey, versionInfo)

More telling is when I debug the data that is actually being sent and returned from the server. Here is the SOAP package that is being sent (notice the release date is the 25th):
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd3="http://www.w3.org/2001/XMLSchema"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
>
<SOAP-ENV:Body>
<ns1:addVersion xmlns:ns1="http://jiradev.anim.com:8080/rpc/soap/jirasoapservice-v2" SOAP-ENC:root="1">
<v1 xsi:type="xsd:string">5xI725381q</v1>
<v2 xsi:type="xsd:string">INFRA</v2>
<v3>
<releaseDate xsi:type="xsd3:dateTime">2008-12-25T00:00:00Z</releaseDate>
<name xsi:type="xsd:string">2008.05</name>
</v3>
</ns1:addVersion>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Here is the data being sent in the response from the server (notice how the release date is not the 24th):
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/1999/XMLSchema" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"><soapenv:Body><ns1:addVersionResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://jiradev.anim.com:8080/rpc/soap/jirasoapservice-v2"><addVersionReturn href="#id0"/></ns1:addVersionResponse><multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:RemoteVersion" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="http://beans.soap.rpc.jira.atlassian.com"><archived xsi:type="ns3:boolean" xmlns:ns3="http://www.w3.org/2001/XMLSchema">false</archived><id xsi:type="ns4:string" xmlns:ns4="http://www.w3.org/2001/XMLSchema">10506</id><name xsi:type="ns5:string" xmlns:ns5="http://www.w3.org/2001/XMLSchema">2008.05</name><releaseDate xsi:type="ns6:dateTime" xmlns:ns6="http://www.w3.org/2001/XMLSchema">2008-12-24T08:00:00.000Z</releaseDate><released xsi:type="ns7:boolean" xmlns:ns7="http://www.w3.org/2001/XMLSchema">false</released><sequence xsi:type="ns8:long" xmlns:ns8="http://www.w3.org/2001/XMLSchema">8</sequence></multiRef></soapenv:Body></soapenv:Envelope>

I don't believe this has anything to do with the SOAPpy python module since it is eventually creating a SOAP package with the correct date and sending it across the network. Is this a bug in Jira or am I formatting the date incorrectly?