<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 02:53:59 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[SERVER-405] dates before epoch sorting</title>
                <link>https://jira.mongodb.org/browse/SERVER-405</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description></description>
                <environment></environment>
        <key id="10837">SERVER-405</key>
            <summary>dates before epoch sorting</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</type>
                                            <priority id="2" iconUrl="https://jira.mongodb.org/images/icons/priorities/critical.svg">Critical - P2</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="9">Done</resolution>
                                        <assignee username="dwight@mongodb.com">Dwight Merriman</assignee>
                                    <reporter username="eliot">Eliot Horowitz</reporter>
                        <labels>
                    </labels>
                <created>Tue, 3 Nov 2009 21:04:53 +0000</created>
                <updated>Tue, 12 Jul 2016 00:27:06 +0000</updated>
                            <resolved>Mon, 8 Aug 2011 22:25:56 +0000</resolved>
                                                    <fixVersion>1.9.1</fixVersion>
                                    <component>Index Maintenance</component>
                                        <votes>49</votes>
                                    <watches>36</watches>
                                                                                                                <comments>
                            <comment id="50726" author="auto" created="Thu, 25 Aug 2011 16:33:40 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;login&apos;: u&apos;stbrody&apos;, u&apos;name&apos;: u&apos;Spencer T Brody&apos;, u&apos;email&apos;: u&apos;spencer@10gen.com&apos;}
&lt;p&gt;Message: Add more tests for sorting pre-epoch dates.  &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-405&quot; title=&quot;dates before epoch sorting&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-405&quot;&gt;&lt;del&gt;SERVER-405&lt;/del&gt;&lt;/a&gt; &amp;amp; QA-40.&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/812e49a673293f34a09f091cb5e9124cc5685c6d&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/812e49a673293f34a09f091cb5e9124cc5685c6d&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="47337" author="auto" created="Tue, 9 Aug 2011 13:23:03 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;login&apos;: u&apos;TonyGen&apos;, u&apos;name&apos;: u&apos;Tony Hannan&apos;, u&apos;email&apos;: u&apos;tony@10gen.com&apos;}
&lt;p&gt;Message: new jstests/date3.js for &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-405&quot; title=&quot;dates before epoch sorting&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-405&quot;&gt;&lt;del&gt;SERVER-405&lt;/del&gt;&lt;/a&gt; &amp;amp; &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-960&quot; title=&quot;Dates before epoch not retrieved correctly&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-960&quot;&gt;&lt;del&gt;SERVER-960&lt;/del&gt;&lt;/a&gt;&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/ad2f56a651b0b25f7a63ca4f533bdbc48b8c6ef0&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/ad2f56a651b0b25f7a63ca4f533bdbc48b8c6ef0&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="47188" author="eliot" created="Mon, 8 Aug 2011 21:43:59 +0000"  >&lt;p&gt;Yes - no changes for old indexes.&lt;/p&gt;</comment>
                            <comment id="47186" author="tonyh" created="Mon, 8 Aug 2011 21:42:47 +0000"  >&lt;p&gt;They also don&apos;t filter correctly. Is that OK too? See my $lt, $gt example above.&lt;/p&gt;</comment>
                            <comment id="47175" author="eliot" created="Mon, 8 Aug 2011 21:03:07 +0000"  >&lt;p&gt;@tony - Yes - old indexes will still not sort correctly.&lt;/p&gt;</comment>
                            <comment id="47163" author="tonyh" created="Mon, 8 Aug 2011 20:31:03 +0000"  >&lt;p&gt;Eliot or Dwight, can you answer above two comments? In a nutshell, is it OK that old indexes don&apos;t return right results or sort correctly?&lt;/p&gt;</comment>
                            <comment id="47162" author="tonyh" created="Mon, 8 Aug 2011 20:29:11 +0000"  >&lt;p&gt;Old index answers range queries differently if $lt comparison used. To recreate:&lt;/p&gt;

&lt;p&gt;In old version (1.8.2):&lt;br/&gt;
&amp;gt; db.foo.save(&lt;/p&gt;
{x:1, d: new Date(1000)}
&lt;p&gt;)&lt;br/&gt;
&amp;gt; db.foo.save(&lt;/p&gt;
{x:2, d: new Date(-1000)}
&lt;p&gt;)&lt;br/&gt;
&amp;gt; db.foo.ensureIndex(&lt;/p&gt;
{d: 1}
&lt;p&gt;)&lt;/p&gt;

&lt;p&gt;In new version (1.9.2-pre) on same db files:&lt;br/&gt;
&amp;gt; db.foo.find({},{_id:0})&lt;/p&gt;
{ &quot;x&quot; : 1, &quot;d&quot; : ISODate(&quot;1970-01-01T00:00:01Z&quot;) }
{ &quot;x&quot; : 1, &quot;d&quot; : ISODate(&quot;1969-12-31T23:59:59Z&quot;) }
&lt;p&gt;&amp;gt; db.foo.find({d:{$lt:new Date(0)}},{_id:0})&lt;br/&gt;
&amp;gt; db.foo.find({d:{$gt:new Date(0)}},{_id:0})&lt;/p&gt;
{ &quot;x&quot; : 1, &quot;d&quot; : ISODate(&quot;1970-01-01T00:00:01Z&quot;) }

&lt;p&gt;Notice $lt incorrectly returns empty set.&lt;br/&gt;
This may also be by design if we are ignoring old indexes.&lt;/p&gt;</comment>
                            <comment id="47110" author="tonyh" created="Mon, 8 Aug 2011 18:13:17 +0000"  >&lt;p&gt;An index created on a date field before upgrading to version 1.9.1 still sorts incorrectly after upgrading. Is this by design? I gather yes from Eliot&apos;s comment above &quot;Rather than forcing every index to be re-created, we can correct the behavior for new indexes and leave old ones as they were&quot;. After dropping and recreating the index, it sorts correctly.&lt;/p&gt;</comment>
                            <comment id="40798" author="auto" created="Wed, 6 Jul 2011 03:55:34 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;login&apos;: u&apos;dwight&apos;, u&apos;name&apos;: u&apos;dwight&apos;, u&apos;email&apos;: u&apos;dwight@10gen.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-405&quot; title=&quot;dates before epoch sorting&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-405&quot;&gt;&lt;del&gt;SERVER-405&lt;/del&gt;&lt;/a&gt; signed dates a test&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/c0130065860db820488cdfaa55b43805a017e7ed&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/c0130065860db820488cdfaa55b43805a017e7ed&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="40232" author="dwight_10gen" created="Fri, 1 Jul 2011 19:18:17 +0000"  >&lt;p&gt;this should work now but i&apos;m not resolving until i add a test&lt;/p&gt;</comment>
                            <comment id="28191" author="leif" created="Thu, 7 Apr 2011 15:21:05 +0000"  >&lt;p&gt;It sounds like much of the delays on resolving this issue revolve around concerns with corruption of data in the indexes.  I have not gone into the source so sorry if this a silly question.  Would it be possible to add a format version number to the beginning of all indexes and collections?  The first format version would be identified by the lack of the version identifier.  MongoDB would load in these versions ids on startup so it knew how to handle the data.&lt;/p&gt;

&lt;p&gt;This way applications which need to continue using the current broken format could continue to do so, but new collections or indexes would use version 2 (with the fix).  If you rebuilt your index or collections then their versions would be incremented to the newest version.&lt;/p&gt;

&lt;p&gt;The drawback is that there would be two versions of some data structures and the related logic.  These upgrades could probably be removed after a full major version increase.  If would let you upgrade from 1.6.5 to 1.8.x without rebuilding indexes and data, but you would need to go all the way up to 2.0.x for example. &lt;/p&gt;

&lt;p&gt;I spent much of a day trying to figure out why certain of our queries were not working and it turned out to be this issue.  We make heavy use of dates with some of it well before 1970 so we are also looking forward to a fix for this.&lt;/p&gt;

&lt;p&gt;Cheers,&lt;br/&gt;
Leif&lt;/p&gt;</comment>
                            <comment id="26527" author="vicentemundim" created="Tue, 22 Mar 2011 22:25:42 +0000"  >&lt;p&gt;I&apos;ve followed your advice and manage to make it work. Basically, I&apos;ve changed Date_t declaration in bson/util/misc.h to:&lt;/p&gt;

&lt;p&gt;    struct Date_t {&lt;br/&gt;
        long long millis;&lt;br/&gt;
        Date_t(): millis(0) {}&lt;br/&gt;
        Date_t(unsigned long long m): millis(static_cast&amp;lt;long long&amp;gt;(m)) {}&lt;br/&gt;
        operator long long&amp;amp;() &lt;/p&gt;
{ return millis; }&lt;br/&gt;
        operator const long long&amp;amp;() const { return millis; }
&lt;p&gt;        string toString() const &lt;/p&gt;
{
            char buf[64];
            time_t_to_String(millis/1000, buf);
            return buf;
        }
&lt;p&gt;    };&lt;/p&gt;

&lt;p&gt;I&apos;ve maintained the &apos;unsigned long long&apos; constructor, which typecasts it to &apos;long long&apos;. I&apos;ve also changed the return of operators to &apos;long long&apos; and the millis variable.&lt;/p&gt;

&lt;p&gt;I&apos;ve found two related TODOs, one in scripting/engine.cpp:&lt;/p&gt;

&lt;p&gt;     case Date:&lt;br/&gt;
            // TODO: make signed&lt;br/&gt;
            builder.appendDate( fieldName , Date_t((unsigned long long)getNumber( scopeName )) );&lt;br/&gt;
            break;&lt;/p&gt;

&lt;p&gt;And another one in scripting/sm_db.cpp:&lt;/p&gt;

&lt;p&gt;        if ( JS_InstanceOf( c-&amp;gt;_context , o, &amp;amp;js_DateClass , 0 ) ) &lt;/p&gt;
{
            jsdouble d = js_DateGetMsecSinceEpoch( c-&amp;gt;_context , o );
            //TODO: make signed
            b.appendDate( name , Date_t((unsigned long long)d) );
            return true;
        }

&lt;p&gt;I didn&apos;t changed those files as the constructor of Date_t will already typecast the values in both of them.&lt;/p&gt;

&lt;p&gt;Since I&apos;m not a C++ expert, and I&apos;m not familiar with MongoDB code, I don&apos;t know if there are other places where a change is needed.&lt;/p&gt;

&lt;p&gt;Any suggestions or advices here?&lt;/p&gt;</comment>
                            <comment id="26457" author="eliot" created="Tue, 22 Mar 2011 02:13:47 +0000"  >&lt;p&gt;The key is bson/util/misc.h&lt;/p&gt;


&lt;p&gt;        // TODO: make signed (and look for related TODO&apos;s)&lt;br/&gt;
        unsigned long long millis;&lt;/p&gt;


&lt;p&gt;But there are a few changes and needs a lot of testing.&lt;br/&gt;
If you miss a spot for example, you&apos;ll get data corruption.&lt;/p&gt;</comment>
                            <comment id="26446" author="vicentemundim" created="Tue, 22 Mar 2011 00:09:39 +0000"  >&lt;p&gt;Thanks for the clarification Eliot. My application is not yet in production, so I could easily reIndex it. Maybe that&apos;s the case of other people here. Is there any way to create a patch for 1.8, since it is trivial to fix?&lt;/p&gt;

&lt;p&gt;I could make it if I knew where to start.&lt;/p&gt;</comment>
                            <comment id="26434" author="eliot" created="Mon, 21 Mar 2011 23:13:23 +0000"  >&lt;p&gt;Its trivial to fix going forward, the problem is that if done nievely, every exiting index would have to be reIndexes or things would be corrupt.&lt;br/&gt;
In 1.8 we took steps such that we can do this without forcing a full reIndex.&lt;br/&gt;
So in 2.0 we&apos;ll be able to fix.&lt;/p&gt;</comment>
                            <comment id="26423" author="smonsees" created="Mon, 21 Mar 2011 21:58:45 +0000"  >&lt;p&gt;This is a big deal for me as well.&lt;/p&gt;
</comment>
                            <comment id="26420" author="vicentemundim" created="Mon, 21 Mar 2011 21:10:54 +0000"  >&lt;p&gt;Eliot,&lt;/p&gt;

&lt;p&gt;Could you explain the complexity of implementing this? I&apos;m a little confused here. How datetimes are store in mongodb, and why sort works this way?&lt;/p&gt;

&lt;p&gt;I have an application which contains videos that were exhibited at dates before epoch. When I use sort(&lt;/p&gt;
{exhibited_at: -1}
&lt;p&gt;) it brings me videos from 1969, 1965, etc first, then videos from 2011. I&apos;m considering the option of storing longs instead of datetimes, but this seems like a hack...&lt;/p&gt;

&lt;p&gt;I have to agree with Durran, this is a pretty large bug, and from the change history, it is being pushed again and again to next releases. Can we be confident that this will be released in 2.0?&lt;/p&gt;</comment>
                            <comment id="22333" author="eliot" created="Thu, 13 Jan 2011 20:14:20 +0000"  >&lt;p&gt;There was a change made in 1.8 that had to be released before we could safely do this.&lt;br/&gt;
This will be in 2.0, and in an early 1.9&lt;/p&gt;</comment>
                            <comment id="22328" author="nehresma" created="Thu, 13 Jan 2011 19:38:00 +0000"  >&lt;p&gt;Unfortunately the target date for this keeps getting bumped back.  Can someone give us any idea what &quot;2011 - phase 1&quot; means, and when this is scheduled to happen?  We&apos;ve been developing our project under the assumption that this was going to make it into 1.8, but we&apos;re going to need to do something else for dates at this point.&lt;/p&gt;</comment>
                            <comment id="18475" author="eliot" created="Thu, 23 Sep 2010 21:04:31 +0000"  >&lt;p&gt;Rather than forcing every index to be re-created, we can correct the behavior for new indexes and leave old ones as they were.&lt;/p&gt;</comment>
                            <comment id="14841" author="jch" created="Thu, 17 Jun 2010 14:05:16 +0000"  >&lt;p&gt;mongoimport also seems to have problems parsing dates pre-epoch:&lt;/p&gt;

&lt;p&gt;exception:Invalid use of reserved field name&lt;br/&gt;
{&quot;dob&quot;:&lt;/p&gt;
{&quot;$date&quot;:-1884384000000}
&lt;p&gt;, ... }&lt;/p&gt;
</comment>
                            <comment id="14258" author="eliot" created="Fri, 14 May 2010 10:44:23 +0000"  >&lt;p&gt;end Q3/early Q4&lt;/p&gt;</comment>
                            <comment id="13939" author="durran" created="Thu, 29 Apr 2010 17:19:13 +0000"  >&lt;p&gt;If this is geared to 1.7.x - is that around Q4 2010?&lt;/p&gt;</comment>
                            <comment id="13713" author="eliot" created="Sat, 17 Apr 2010 18:45:49 +0000"  >&lt;p&gt;That would work though doing that migration is even more costly than what we would have to do.&lt;br/&gt;
There may be other creative solutions, i&apos;ll think about it for a while.&lt;br/&gt;
The trick is selectively upgrading indexes - can do a scan, but that at startup would have to scan all indexes, which is expensive.&lt;br/&gt;
Though perhaps I have an idea...&lt;br/&gt;
Should be easy to find bad index keys actually...&lt;/p&gt;
</comment>
                            <comment id="13712" author="durran" created="Sat, 17 Apr 2010 15:04:53 +0000"  >&lt;p&gt;Well I am considering handling this in the meantime at the ODM level, and passing the longs to the db to store... When querying I&apos;d have to do this conversion as well... Do you think this a viable workaround for the moment - I&apos;ll need to supply a migration script for all that use Mongoid if I do this - just want to get an opionion first... Right now it&apos;s affecting us in a large way (not sure how we missed this before) in that we can&apos;t query for people who are over age 40.&lt;/p&gt;</comment>
                            <comment id="13705" author="eliot" created="Fri, 16 Apr 2010 16:16:30 +0000"  >&lt;p&gt;the server is using an unsigned number rather than signed for dates, so anything before the epoch rolls over far into the future.&lt;br/&gt;
so this will cause all sorts of problems with dates before 1970&lt;/p&gt;

&lt;p&gt;the annoying part of this case is that if there is an existing index with an old date, and we make this change without forcing an index-rebuild, it could lead to corruption.&lt;/p&gt;

&lt;p&gt;so we&apos;ve been holding off until we&apos;re ready to force a file format change&lt;/p&gt;</comment>
                            <comment id="13703" author="durran" created="Fri, 16 Apr 2010 16:05:55 +0000"  >&lt;p&gt;Can we get a better description on this issue since the other I submitted was closed as a duplicate? This is a pretty large bug in my opinion (we cant query times accurately at all) but this one can&apos;t get votes if the public doesn&apos;t don&apos;t know what it is.&lt;/p&gt;

&lt;p&gt;Thanks!&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                            <outwardlinks description="depends on">
                                        <issuelink>
            <issuekey id="13170">SERVER-1845</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is depended on by">
                                        <issuelink>
            <issuekey id="11694">SERVER-960</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="10892">SERVER-429</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>27.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Fri, 16 Apr 2010 16:05:55 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        12 years, 25 weeks, 6 days ago
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18254" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Dependencies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[<s><a href='https://jira.mongodb.org/browse/SERVER-1845'>SERVER-1845</a></s>]]></customfieldvalue>


                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10057" key="com.atlassian.jira.toolkit:lastusercommented">
                        <customfieldname>Last comment by Customer</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>true</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10056" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last commenter</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>ramon.fernandez@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            12 years, 25 weeks, 6 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10000" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Old_Backport</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10000"><![CDATA[No]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>auto</customfieldvalue>
            <customfieldvalue>durran</customfieldvalue>
            <customfieldvalue>dwight@mongodb.com</customfieldvalue>
            <customfieldvalue>eliot</customfieldvalue>
            <customfieldvalue>jch</customfieldvalue>
            <customfieldvalue>leif</customfieldvalue>
            <customfieldvalue>nehresma</customfieldvalue>
            <customfieldvalue>smonsees</customfieldvalue>
            <customfieldvalue>tonyh</customfieldvalue>
            <customfieldvalue>vicentemundim</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrpuun:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hrilzr:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>22215</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_23361" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Requested By</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10053" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>Time In Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_22870" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Triagers</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_14350" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>serverRank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrvmhb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>