<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 03:44:29 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-17453] warn that db.eval() / eval command is deprecated</title>
                <link>https://jira.mongodb.org/browse/SERVER-17453</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;div class=&quot;panel&quot; style=&quot;background-color: #EEEEEE;border-color: #ccc;border-width: 1px;&quot;&gt;&lt;div class=&quot;panelHeader&quot; style=&quot;border-bottom-width: 1px;border-bottom-color: #ccc;background-color: #6CB33F;&quot;&gt;&lt;b&gt;Issue Status as of Apr 29, 2015&lt;/b&gt;&lt;/div&gt;&lt;div class=&quot;panelContent&quot; style=&quot;background-color: #EEEEEE;&quot;&gt;
&lt;p&gt;&lt;b&gt;ISSUE SUMMARY&lt;/b&gt;&lt;br/&gt;
The &lt;tt&gt;eval&lt;/tt&gt; operation that permits clients to execute is deprecated in 3.0 and is currently planned for removal in an upcoming release. This change adds additional warning messages regarding the deprecation to the &lt;tt&gt;mongo&lt;/tt&gt; shell and the &lt;tt&gt;eval&lt;/tt&gt; command.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;USER IMPACT&lt;/b&gt;&lt;br/&gt;
This change just adds additional logging, but users depending on &lt;tt&gt;eval&lt;/tt&gt; should start planning for its eventual removal.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;FIX VERSION&lt;/b&gt;&lt;br/&gt;
The change is included in the 3.0.3 production release.&lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;h6&gt;&lt;a name=&quot;Originaldescription&quot;&gt;&lt;/a&gt;Original description&lt;/h6&gt;

&lt;p&gt;Add a warning msg to server and mongo repl log when invoking the eval command, aka $eval or db.eval().&lt;/p&gt;</description>
                <environment></environment>
        <key id="187304">SERVER-17453</key>
            <summary>warn that db.eval() / eval command is deprecated</summary>
                <type id="3" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14718&amp;avatarType=issuetype">Task</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</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="samantha.ritter@mongodb.com">Samantha Ritter</assignee>
                                    <reporter username="dan@mongodb.com">Daniel Pasette</reporter>
                        <labels>
                    </labels>
                <created>Tue, 3 Mar 2015 22:51:52 +0000</created>
                <updated>Thu, 14 Jan 2016 06:21:31 +0000</updated>
                            <resolved>Mon, 30 Mar 2015 18:48:15 +0000</resolved>
                                                    <fixVersion>3.0.3</fixVersion>
                    <fixVersion>3.1.1</fixVersion>
                                    <component>JavaScript</component>
                                        <votes>2</votes>
                                    <watches>25</watches>
                                                                                                                <comments>
                            <comment id="1134597" author="rsercano" created="Thu, 14 Jan 2016 06:21:31 +0000"  >&lt;p&gt;@Ramon Fernandez I know you still have the eval functionality but it&apos;s madness to use it since you are about to remove this command, thank you for clarifying.&lt;/p&gt;

&lt;p&gt;@Ian Beaver thank you I&apos;m going to watch it.&lt;/p&gt;</comment>
                            <comment id="1134418" author="ibeaver" created="Wed, 13 Jan 2016 23:12:19 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=rsercano&quot; class=&quot;user-hover&quot; rel=&quot;rsercano&quot;&gt;rsercano&lt;/a&gt;, see &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-20510&quot; title=&quot;Add stored procedure functionality&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-20510&quot;&gt;&lt;del&gt;SERVER-20510&lt;/del&gt;&lt;/a&gt; for the discussion on an &lt;em&gt;eval&lt;/em&gt; replacement.&lt;/p&gt;</comment>
                            <comment id="1134389" author="ramon.fernandez" created="Wed, 13 Jan 2016 22:42:42 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=rsercano&quot; class=&quot;user-hover&quot; rel=&quot;rsercano&quot;&gt;rsercano&lt;/a&gt;, we&apos;re discussing replacements that can improve on the limitations of &lt;tt&gt;eval&lt;/tt&gt;, but there are no further details I can provide. Note that &lt;tt&gt;eval&lt;/tt&gt; is part of our latest stable release, MongoDB 3.2.&lt;/p&gt;

&lt;p&gt;Regards,&lt;br/&gt;
Ram&#243;n.&lt;/p&gt;</comment>
                            <comment id="1123324" author="rsercano" created="Tue, 29 Dec 2015 14:29:09 +0000"  >&lt;p&gt;Hello,&lt;/p&gt;

&lt;p&gt;Are you planning to serve a similar functionality ?&lt;br/&gt;
I&apos;m developing a mongodb client which works with meteor-js (internally node-js mongodb driver) and eval was a perfect helper for me.&lt;/p&gt;

&lt;p&gt;Regards,&lt;br/&gt;
Sercan&lt;/p&gt;</comment>
                            <comment id="951041" author="ramon.fernandez" created="Thu, 25 Jun 2015 19:11:01 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=h.lassiege%40gmail.com&quot; class=&quot;user-hover&quot; rel=&quot;h.lassiege@gmail.com&quot;&gt;h.lassiege@gmail.com&lt;/a&gt;, looks like the latest update to Mongeez predates MongoDB 3.0, so there will be other changes that Mongeez may need to undertake to 3.0 before having any issues with &lt;tt&gt;eval&lt;/tt&gt;. Note that &lt;tt&gt;eval&lt;/tt&gt; will continue to work with MongoDB 2.6.&lt;/p&gt;

&lt;p&gt;Regards,&lt;br/&gt;
Ram&#243;n.&lt;/p&gt;</comment>
                            <comment id="948313" author="ibeaver" created="Tue, 23 Jun 2015 16:56:55 +0000"  >&lt;p&gt;Are you planning any alternatives to eval?  Mongo needs to have an equivalent to stored procedures or it will be unusable for many of our use cases.  M/R and the aggregation pipelines are not alternatives as they are not designed for individual document operations but group and aggregation operations.  Stored procedures exist because there are many cases where changes need to be made that are dependent on existing data and it is not efficient to do that outside of the DB.&lt;/p&gt;

&lt;p&gt;A very common use case is you need to modify every document in a collection based on some attribute of each document.  For example: each document has a rank score or other numerical attr of some kind, and you want to normalize that score based on the max value in the collection.  To use client side code, as you recommend, means pulling down every single document or specific fields of each in the collection, reading the score and dividing by the max, and writing the result back.  We have many collections with tens to hundreds of millions of documents and do many similar operation with them.  To do this client side is a non-starter with the IO and bandwidth needed to ship data back and forth between the client and servers.  Running some basic tests with only ~100k documents this simple normalization operation is 10x-20x slower running client side, not to mention all the additional bandwidth used.  This is in AWS with r3.8xlarge DB and client instances and SSD volumes.  We re-wrote lots of our applications to use $eval because of this performance issue.&lt;/p&gt;

&lt;p&gt;If Mongo wants to position itself as a scaleable database for analytics, it has to provide some mechanism for executing arbitrary functions on the data within the server, and ideally one that works with shards.  It doesn&apos;t need to be JS and it doesn&apos;t have to be embedded in the storage engine, but even a streaming model like Hadoop where each node executes a script on its partition of the data just using stdin/stdout would be fine.  Pulling all of the data out of the database over the network to write it back again with some minor changes is not a usable strategy.  One of the major wins of horizontal scaling is to be able to do the processing where the data lives and have that processing power scale with the data storage.&lt;/p&gt;</comment>
                            <comment id="946640" author="hlassiege" created="Mon, 22 Jun 2015 07:35:21 +0000"  >&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;Regarding this issue, I guess that tools like Mongeez will not work anymore when eval will be removed, is it correct ?&lt;br/&gt;
(&lt;a href=&quot;https://github.com/secondmarket/mongeez&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/secondmarket/mongeez&lt;/a&gt;)&lt;/p&gt;

&lt;p&gt;Do you know any alternative ?&lt;/p&gt;
</comment>
                            <comment id="893108" author="xgen-internal-githook" created="Mon, 20 Apr 2015 18:43:37 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;samantharitter&apos;, u&apos;name&apos;: u&apos;Samantha Ritter&apos;, u&apos;email&apos;: u&apos;samantha.ritter@10gen.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-17453&quot; title=&quot;warn that db.eval() / eval command is deprecated&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-17453&quot;&gt;&lt;del&gt;SERVER-17453&lt;/del&gt;&lt;/a&gt; eval command is deprecated&lt;/p&gt;

&lt;p&gt;(cherry picked from commit 465bb26c0fb0f4731f4dbb5e09e0a791177bbc64)&lt;br/&gt;
Branch: v3.0&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/ad6f455452db9dd395a0ba71ec38d34848770f3d&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/ad6f455452db9dd395a0ba71ec38d34848770f3d&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="867911" author="xgen-internal-githook" created="Mon, 30 Mar 2015 18:45:51 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;samantharitter&apos;, u&apos;name&apos;: u&apos;Samantha Ritter&apos;, u&apos;email&apos;: u&apos;samantha.ritter@10gen.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-17453&quot; title=&quot;warn that db.eval() / eval command is deprecated&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-17453&quot;&gt;&lt;del&gt;SERVER-17453&lt;/del&gt;&lt;/a&gt; eval command is deprecated&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/465bb26c0fb0f4731f4dbb5e09e0a791177bbc64&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/465bb26c0fb0f4731f4dbb5e09e0a791177bbc64&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="865416" author="davebarbarian24" created="Thu, 26 Mar 2015 20:24:10 +0000"  >&lt;p&gt;&amp;gt; If it turns out that the difference in performance is the extra latency (since both your code and eval passed in code run JS) - in which case you could achieve better performance running your node closer to the server.&lt;br/&gt;
The tests I&apos;ve been running have been on an SSD with Node and Mongo on my machine. I can&apos;t see where there I could reduce the latency any further in that. It could be overhead of the complexity of the app, but I&apos;m not sure. I attempted to use the C++ connector but gave up in frustration trying to solve boost linking problems.&lt;/p&gt;

&lt;p&gt;&amp;gt; The schema choice you link to is not one that will be able to give you an efficient way to fetch all children of a node (i.e. it requires multiple queries at the tradeoff of less maintenance on changes in hierarchy).&lt;br/&gt;
Yeah, I said that. Changes in hierarchy are done much more frequently than removal of nodes in our system. Doesn&apos;t mean it never gets done just much less frequently. I&apos;d rather have a performance hit 10% of the time than 90% of the time.&lt;/p&gt;

&lt;p&gt;Is there any plan to introduce an API that can match this performance?&lt;/p&gt;</comment>
                            <comment id="859460" author="asya" created="Fri, 20 Mar 2015 18:26:48 +0000"  >&lt;p&gt;If it turns out that the difference in performance is the extra latency (since both your code and eval passed in code run JS) - in which case you could achieve better performance running your node closer to the server.   The schema choice you link to is not one that will be able to give you an efficient way to fetch all children of a node (i.e. it requires multiple queries at the tradeoff of less maintenance on changes in hierarchy).&lt;/p&gt;</comment>
                            <comment id="859199" author="davebarbarian24" created="Fri, 20 Mar 2015 14:58:10 +0000"  >&lt;p&gt;Not recommended? This page begs to differ: &lt;a href=&quot;http://docs.mongodb.org/manual/tutorial/model-tree-structures-with-parent-references/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://docs.mongodb.org/manual/tutorial/model-tree-structures-with-parent-references/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;When we first started building our app 2 years ago, we took a serious look at &lt;b&gt;all&lt;/b&gt; of the different approaches (outlined on docs.mongodb.org) and decided to go with parent references, as it gave us the best performance for what our users do most often, move branches around. If we picked ancestors, child references or nested sets(&lt;b&gt;all&lt;/b&gt; of the other options outlined on docs.mongodb.org) we&apos;d have &lt;b&gt;exactly&lt;/b&gt; the same performance issues, but more often! There is a drawback to each one of the hierarchy schema designs, we picked the one that, for our use case, performed the best for everyday tasks.&lt;/p&gt;

&lt;p&gt;I&apos;m not opposed to removing eval, I&apos;m opposed to not replacing it with something that gives equal performance, forgetting my use-case, as there are a thousand others. If I have some scheduled data reduction that takes on average 12 hours to complete on a client, but 2 with eval, why remove such a useful feature without giving us an equally performant (or better) option?&lt;/p&gt;</comment>
                            <comment id="858920" author="asya" created="Fri, 20 Mar 2015 03:59:00 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=davebarbarian24&quot; class=&quot;user-hover&quot; rel=&quot;davebarbarian24&quot;&gt;davebarbarian24&lt;/a&gt; &lt;/p&gt;

&lt;p&gt;That&apos;s not a recommended way to solve this use case - docs.mongodb.org have several examples of schema design for representing hierarchy/trees that allow you to get this sort of information in a single query.  I would recommend a different schema to improve performance.&lt;/p&gt;</comment>
                            <comment id="858071" author="davebarbarian24" created="Thu, 19 Mar 2015 17:42:48 +0000"  >&lt;p&gt;I&apos;m currently using eval for performance reasons. My database has a tree structure with parent references. I often need to find out all the children of a particular branch of the tree (using a recursive call). Doing these queries with the Node.js connector and concatenating their IDs together takes on average 6x times longer than my stored Javascript function that does the same thing. Without this my app doesn&apos;t scale very well.&lt;/p&gt;</comment>
                            <comment id="856611" author="rgpublic" created="Wed, 18 Mar 2015 12:34:35 +0000"  >&lt;p&gt;Sigh. Another beloved Mongo feature goes away... Though I fully understand the reasoning behind it. I&apos;d like to add here that at least &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-458&quot; title=&quot;JavaScript $function in update&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-458&quot;&gt;&lt;del&gt;SERVER-458&lt;/del&gt;&lt;/a&gt; should be implemented &lt;b&gt;before&lt;/b&gt; eval is removed. When you want to do complex updating on lots of rows simple client code just isn&apos;t fast enough. And a client process (think of web server process) can much easier be interrupted - leaving you with half of the rows changed and half of the rows not. We&apos;re using eval right now to avoid this. Also, it&apos;s sometimes great to be able to use javascript for some changes, not your usual client language (PHP etc)...&lt;/p&gt;</comment>
                            <comment id="843469" author="matt.parlane@gmail.com" created="Thu, 5 Mar 2015 05:11:59 +0000"  >&lt;p&gt;Personally, nothing &amp;#8211; I&apos;m not using eval at all, but I would like the option in the future.&lt;/p&gt;

&lt;p&gt;The way I see it, server-side logic, in the form of stored procedures, is a big deal in the enterprise world, which you&apos;ve made no secret that you&apos;re going after. I think you guys should look seriously at solving the problems and making eval a first-class citizen rather than just removing it.&lt;/p&gt;

&lt;p&gt;You&apos;ve got a tight, high-performance integration with (arguably) the fastest implementation of (arguably) the most popular programming language in the world, that sounds like something you should embrace and promote, not shun.&lt;/p&gt;</comment>
                            <comment id="843013" author="dan@10gen.com" created="Wed, 4 Mar 2015 18:59:47 +0000"  >&lt;p&gt;Hi Matt,&lt;br/&gt;
There are a number of issues with the eval command.&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Compatibility: eval was developed before the introduction of sharding. The eval command does not work on sharded clusters at all.&lt;/li&gt;
	&lt;li&gt;Performance: Takes a global lock by default.  If eval is with the &lt;tt&gt;noLock&lt;/tt&gt; option, it implies that the javascript could just as easily be run from a client program.&lt;/li&gt;
	&lt;li&gt;Security: You must have access to all actions on all resources in order to run eval.  Security best practices depend on being able to segment privileges to actions, and eval gives too broad a range of powers.&lt;/li&gt;
	&lt;li&gt;Maintenance: The server must move to a model where javascript is executed &quot;out of process&quot; for a number of reasons; maintaining support for eval makes this very difficult.&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;I should point out that this does not mean a drop of support for all server side javascript. &lt;tt&gt;$where&lt;/tt&gt; and map/reduce are still supported.&lt;/p&gt;

&lt;p&gt;Can you tell me what you&apos;re using eval to accomplish?&lt;/p&gt;</comment>
                            <comment id="842335" author="matt.parlane@gmail.com" created="Wed, 4 Mar 2015 01:12:11 +0000"  >&lt;p&gt;Anyone care to provide some rationale behind the deprecation?&lt;/p&gt;</comment>
                            <comment id="842312" author="schwerin" created="Wed, 4 Mar 2015 00:24:27 +0000"  >&lt;p&gt;This ticket covers the db.eval() shell helper and the eval/$eval command.  The latter form the basis for the implementation of the former.&lt;/p&gt;</comment>
                            <comment id="842251" author="matt.parlane@gmail.com" created="Tue, 3 Mar 2015 23:50:25 +0000"  >&lt;p&gt;Is the $eval command also deprecated?&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                            <outwardlinks description="depends on">
                                        <issuelink>
            <issuekey id="111103">SERVER-12742</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is depended on by">
                                                        </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="187188">DOCS-4899</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                                        </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="200712">DRIVERS-225</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>20.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18555" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname># of Sprints</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_12451" key="com.atlassian.jira.plugin.system.customfieldtypes:multiversion">
                        <customfieldname>Backport Completed</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="15290">3.0.3</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10011" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Backwards Compatibility</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10011"><![CDATA[Minor Change]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Tue, 3 Mar 2015 23:50:25 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        8 years, 4 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-12742'>SERVER-12742</a></s>, <s><a href='https://jira.mongodb.org/browse/WRITING-1307'>WRITING-1307</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>rsercano</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            8 years, 4 weeks, 6 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>schwerin@mongodb.com</customfieldvalue>
            <customfieldvalue>asya.kamsky@mongodb.com</customfieldvalue>
            <customfieldvalue>dan@mongodb.com</customfieldvalue>
            <customfieldvalue>davebarbarian24</customfieldvalue>
            <customfieldvalue>xgen-internal-githook</customfieldvalue>
            <customfieldvalue>hlassiege</customfieldvalue>
            <customfieldvalue>ibeaver</customfieldvalue>
            <customfieldvalue>matt.parlane@gmail.com</customfieldvalue>
            <customfieldvalue>ramon.fernandez@mongodb.com</customfieldvalue>
            <customfieldvalue>rgpublic</customfieldvalue>
            <customfieldvalue>samantha.ritter@mongodb.com</customfieldvalue>
            <customfieldvalue>rsercano</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrlbgv:</customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>165021</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_10557" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="452">Platform 1 04/03/15</customfieldvalue>

                        </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_11861" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>User Summary</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="11858"><![CDATA[Completed]]></customfieldvalue>

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

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