<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sat Jan 11 15:14:56 UTC 2025

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>Mojang Studios Jira</title>
    <link>https://bugs.mojang.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en</language>    <build-info>
        <version>9.12.2</version>
        <build-number>9120002</build-number>
        <build-date>10-01-2024</build-date>
    </build-info>


<item>
            <title>[MCPE-17304] Pistons, droppers, dispensers, observers, &amp; redstone lamps become stuck in an on or off-state &amp; act like solid/opaque blocks until world-reload</title>
                <link>https://bugs.mojang.com/browse/MCPE-17304</link>
                <project id="10200" key="MCPE">Minecraft (Bedrock codebase)</project>
                    <description>&lt;p&gt;Sometimes, when you load up a world, a couple random pistons, dispensers, droppers, observers, and/or redstone lamps will be stuck in either their on or off state, and will not change state until broken, pushed, pulled, or upon reloading the world. The blocks also act as if they were just normal non-rs-component solid/opaque blocks. This means that pistons will be able to pass a redstone signal through them via dust &amp;amp; a repeater, and the blocks will not be affected by any redstone-component-specific bugs like &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-18114&quot; title=&quot;Solid/opaque redstone components act differently from normal solid/opaque blocks&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-18114&quot;&gt;&lt;del&gt;MCPE-18114&lt;/del&gt;&lt;/a&gt;. This bug is difficult to reproduce since it seems to be somewhat random as to when it occurs, but it tends to happen to the same particular blocks when testing.&lt;/p&gt;</description>
            <key id="150615">MCPE-17304</key>
            <summary>Pistons, droppers, dispensers, observers, &amp; redstone lamps become stuck in an on or off-state &amp; act like solid/opaque blocks until world-reload</summary>
                <type id="1" iconUrl="https://bugs.mojang.com/secure/viewavatar?size=xsmall&amp;avatarId=18903&amp;avatarType=issuetype">Bug</type>
                                    <status id="5" iconUrl="https://bugs.mojang.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                            <reporter username="NoUser">No User</reporter>
                        <labels>
                            <label>dispenser</label>
                            <label>dropper</label>
                            <label>observer</label>
                            <label>piston</label>
                            <label>redstone</label>
                            <label>redstone_lamp</label>
                            <label>world-loading</label>
                    </labels>
                <created>Thu, 29 Sep 2016 14:53:21 +0200</created>
                <updated>Fri, 14 Aug 2020 04:48:49 +0200</updated>
                            <resolved>Mon, 16 Apr 2018 17:46:49 +0200</resolved>
                                    <version>0.15.9</version>
                    <version>0.15.10</version>
                    <version>0.16.0</version>
                    <version>0.17.0.1</version>
                    <version>1.0.0</version>
                    <version>1.1.4.51</version>
                    <version>1.2.5.52</version>
                                    <fixVersion>1.2.13.54</fixVersion>
                                                        <votes>9</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="447307" author="mega_spud" created="Mon, 16 Apr 2018 17:46:49 +0200"  >&lt;p&gt;Resolving the ticket as fixed based on the comments above.&lt;/p&gt;</comment>
                            <comment id="447152" author="evrqst123" created="Sun, 15 Apr 2018 23:06:22 +0200"  >&lt;p&gt;I am no longer seeing the issue. I re-tested the same world in the latest version 1.2.13 and the redstone worked as it should even after re-loading the world many times.&lt;/p&gt;</comment>
                            <comment id="444515" author="mega_spud" created="Wed, 4 Apr 2018 09:38:52 +0200"  >&lt;p&gt;&lt;b&gt;Thank you for your report!&lt;/b&gt;&lt;br/&gt;
However, this issue has been temporarily closed as &lt;b&gt;&lt;font color=&quot;#FF5722&quot;&gt;Awaiting Response&lt;/font&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;Is this still an issue in the latest version?&lt;/p&gt;

&lt;p&gt;If so, could you please include a copy of the world that is affected?&lt;/p&gt;

&lt;p&gt;This ticket will automatically reopen when you reply.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Quick Links&lt;/b&gt;:&lt;br/&gt;
&#128211; &lt;a href=&quot;http://help.mojang.com/customer/portal/articles/801354-writing-helpful-bug-reports-for-minecraft&quot; title=&quot;How To Write Awesome Tickets! &#128175;&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Issue Guidelines&lt;/a&gt; &amp;#8211; &#128172; &lt;a href=&quot;https://www.reddit.com/r/MCPE/&quot; title=&quot;Help From the Minecraft Community &#128377;&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Community Support&lt;/a&gt; &amp;#8211; &#128231; &lt;a href=&quot;https://feedback.minecraft.net/&quot; title=&quot;Feedback and Suggestions &#9997;&#65039;&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Feedback&lt;/a&gt; &amp;#8211; &#128214; &lt;a href=&quot;http://minecraft.gamepedia.com/Minecraft_Wiki&quot; title=&quot;Official Minecraft Wiki &#127891;&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Game Wiki&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="434086" author="handlbar.rick@comcast.net" created="Fri, 9 Feb 2018 20:30:56 +0100"  >&lt;p&gt;I tested this in 1.2.10.2 on Windows 10 using the &quot;Stuck Piston.mcworld&quot; file. The piston is indeed stuck in the saved file, but I couldn&apos;t get it to get stuck again after saving and reloading about 10 times. However, I did notice that after you flip the toggle lever a couple of times, the top piston is no longer synchronized with the other two in terms of when it extends. This indicates a completely different problem with timing, which might be a different bug.&lt;/p&gt;

&lt;p&gt;Unfortunately, the original reporter&apos;s world which I had tested before is no longer available at the link he provided, so I couldn&apos;t test that.&lt;/p&gt;</comment>
                            <comment id="420801" author="handlbar.rick@comcast.net" created="Wed, 29 Nov 2017 09:55:54 +0100"  >&lt;p&gt;Confirm Justin Reschke&apos;s downloaded world exhibits the problem described for the torch and red concrete blocks.&lt;br/&gt;
Tested in Windows 10 1.2.5.52.&lt;/p&gt;

&lt;p&gt;In a first set of tests, I did a fresh import of the world save file each time. All 10 of these tests exhibited the problem of the redstone torch not turning off. I reimported the world a number of times during later testing and it continued to exhibit the problem. Then, suddenly, on one import everything worked. For me, the imported world seems to have the problem 90% or more of the time.&lt;/p&gt;

&lt;p&gt;In a subsequent set of tests, I started with a freshly imported  copy of the world. Then I saved and reloaded the world and tested the button. In a majority of these tests (&amp;gt; 80%), the reloaded world also exhibited the problem.&lt;/p&gt;

&lt;p&gt;I did a final test against another freshly imported copy, I broke the torch and replaced it. This allowed the activation signal to propagate up the tower. By watching the pistons&apos; behavior, I was able to determine that the problem with the red concrete blocks next to the pistons was still present, and if I fixed the problem for one of these it did not heal the other pistons.&lt;/p&gt;

&lt;p&gt;I notice that the torch and its attachment block (which is also the button&apos;s attachment block) lie on opposite sides of the Z = -224 chunk boundary plane. The same plane separates the repeaters and the red concrete blocks that power the failing pistons. The direction of activation flow across the boundary is opposite for these two pairs of components. However, the signal that propagates the activation from one level to another also crosses this chunk boundary, and it&apos;s impossible to test whether that path is also broken because any method you use to insert a probe signal might heal the problem the same way breaking and replacing the redstone torch does.&lt;/p&gt;

&lt;p&gt;The coordinate Z = -224 is also used as the boundary for the ticking area named SlimeFarm. However, removing the ticking area did not seem to make any difference, either immediately or after saving and reloading the world, so this is likely a coincidence.&lt;/p&gt;</comment>
                            <comment id="420754" author="evrqst123" created="Wed, 29 Nov 2017 01:16:57 +0100"  >&lt;p&gt;It seems when I load into my world it has about a 50% chance that the torch is stuck in that state. It seems to randomly change from a working state to the bugged state and vice versa just by reloading the world. I can also force it to work by breaking &amp;amp; replacing the affected blocks/components. But the next time I load the world there is that chance that it will not be working. It does not seem to be required to crash the game to make the redstone fail, but in case it is relevant, the crash I experience most often is when I play in fullscreen mode and then I switch applications, the game usually crashes when I switch back to Minecraft. So I just try to remember to play in windowed mode &lt;img class=&quot;emoticon&quot; src=&quot;https://bugs.mojang.com/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;

&lt;p&gt;It is probably best that I just include a copy of my world. The link to download it is &lt;a href=&quot;https://app.box.com/s/b7woiffrct9wm29a7z4n9ximl8nwq47a&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;here&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The coordinates for the affected area are in the screenshots below.&lt;/p&gt;

&lt;p&gt;The circuit is housed in an elevator I built for Elytra flight, it only goes up.&lt;br/&gt;
 &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;152046_thumb&quot; href=&quot;https://bugs.mojang.com/secure/attachment/152046/152046_tower+coordinates.png&quot; title=&quot;tower coordinates.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;152046&quot; file-preview-title=&quot;tower coordinates.png&quot;&gt;&lt;img src=&quot;https://bugs.mojang.com/secure/thumbnail/152046/_thumb_152046.png&quot; style=&quot;border: 0px solid black&quot; role=&quot;presentation&quot;/&gt;&lt;/a&gt;&lt;/span&gt; &lt;/p&gt;

&lt;p&gt;I have put some signs up on the affected blocks.&lt;br/&gt;
 &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;152047_thumb&quot; href=&quot;https://bugs.mojang.com/secure/attachment/152047/152047_blocktorch.png&quot; title=&quot;blocktorch.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;152047&quot; file-preview-title=&quot;blocktorch.png&quot;&gt;&lt;img src=&quot;https://bugs.mojang.com/secure/thumbnail/152047/_thumb_152047.png&quot; style=&quot;border: 0px solid black&quot; role=&quot;presentation&quot;/&gt;&lt;/a&gt;&lt;/span&gt; &lt;/p&gt;

&lt;p&gt;In the same circuit I have another block that sometimes seems to have an issue. However, it doesn&apos;t seem to happen as often as it does with the torch. The red concrete block that the cursor is over in this screenshot has the issue, although it might be more likely that it is the piston on the other side of it that may be at fault. In order to fix the issue I simply break and replace the block on each level of the elevator. This block may be difficult to test for bugs because I don&apos;t seem to be able to reproduce this specific issue very often.&lt;br/&gt;
 &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;152048_thumb&quot; href=&quot;https://bugs.mojang.com/secure/attachment/152048/152048_powered+block.png&quot; title=&quot;powered block.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;152048&quot; file-preview-title=&quot;powered block.png&quot;&gt;&lt;img src=&quot;https://bugs.mojang.com/secure/thumbnail/152048/_thumb_152048.png&quot; style=&quot;border: 0px solid black&quot; role=&quot;presentation&quot;/&gt;&lt;/a&gt;&lt;/span&gt; &lt;/p&gt;</comment>
                            <comment id="420525" author="zebulanstanphill@gmail.com" created="Tue, 28 Nov 2017 05:54:52 +0100"  >&lt;p&gt;&lt;a href=&quot;https://bugs.mojang.com/secure/ViewProfile.jspa?name=evrqst123&quot; class=&quot;user-hover&quot; rel=&quot;evrqst123&quot;&gt;evrqst123&lt;/a&gt;, could you provide a world download and/or some screenshots showing the surrounding circuitry? Is the issue with that particular redstone torch still occurring or did it start working again after a world reload? Does breaking and placing it fix the problem? Do you know an easy way to reproduce this behavior? Also, did you recently crash the game while playing on that world? Because that could be related to the redstone torch (and other redstone components) getting stuck in a certain state.&lt;/p&gt;</comment>
                            <comment id="420499" author="evrqst123" created="Tue, 28 Nov 2017 01:08:07 +0100"  >&lt;p&gt;I am having this same sort of problem with pistons on Windows 10 v1.2.5. It also seems to affect redstone torches too.&lt;/p&gt;

&lt;p&gt;Torch in its default state:&lt;br/&gt;
 &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;151911_thumb&quot; href=&quot;https://bugs.mojang.com/secure/attachment/151911/151911_default.png&quot; title=&quot;default.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;151911&quot; file-preview-title=&quot;default.png&quot;&gt;&lt;img src=&quot;https://bugs.mojang.com/secure/thumbnail/151911/_thumb_151911.png&quot; style=&quot;border: 0px solid black&quot; role=&quot;presentation&quot;/&gt;&lt;/a&gt;&lt;/span&gt; &lt;/p&gt;


&lt;p&gt;Button was pushed and torch signal should be inverted, but it is not:&lt;br/&gt;
 &lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;a id=&quot;151912_thumb&quot; href=&quot;https://bugs.mojang.com/secure/attachment/151912/151912_pushed.png&quot; title=&quot;pushed.png&quot; file-preview-type=&quot;image&quot; file-preview-id=&quot;151912&quot; file-preview-title=&quot;pushed.png&quot;&gt;&lt;img src=&quot;https://bugs.mojang.com/secure/thumbnail/151912/_thumb_151912.png&quot; style=&quot;border: 0px solid black&quot; role=&quot;presentation&quot;/&gt;&lt;/a&gt;&lt;/span&gt; &lt;/p&gt;</comment>
                            <comment id="416121" author="mistahtokyo" created="Wed, 1 Nov 2017 23:55:42 +0100"  >&lt;p&gt;Cannot reproduce as of 1.2.5.15&lt;/p&gt;</comment>
                            <comment id="395011" author="secret of world" created="Fri, 21 Jul 2017 07:15:46 +0200"  >&lt;p&gt;true,I put slime block on sticky piston&lt;/p&gt;</comment>
                            <comment id="391970" author="saintsalade" created="Fri, 30 Jun 2017 19:27:57 +0200"  >&lt;p&gt;The bug with pistons still happens in 1.1.2, with more than 20 at the same time&lt;/p&gt;</comment>
                            <comment id="370610" author="odus20032222336" created="Sat, 4 Mar 2017 10:43:36 +0100"  >&lt;p&gt;Observers also.&lt;/p&gt;</comment>
                            <comment id="354040" author="talaeus" created="Fri, 13 Jan 2017 15:40:34 +0100"  >&lt;p&gt;While it looks like the same bug, this is actually at least two bugs squashed into a single ticket.&lt;/p&gt;

&lt;p&gt;I have just made a fix that fixes: Pressure plate, tripwire, redstone lamp, detector rail, buttons and probably dispensers and droppers as well. What separates these from some others in this ticket is that these would &lt;em&gt;not&lt;/em&gt; get fixed by reloading the world. In fact, what was causing this issue was the actual saving of the world. Reloading wouldn&apos;t fix it since the saved state is broken.&lt;/p&gt;

&lt;p&gt;Pistons however is a completely different chapter.&lt;/p&gt;</comment>
                            <comment id="352581" author="mega_spud" created="Thu, 5 Jan 2017 16:02:01 +0100"  >&lt;p&gt;Attached a World save with a piston that becomes &apos;stuck&apos;.&lt;/p&gt;

&lt;p&gt;Open the world and toggle the lever, the top piston remains unresponsive, unless it is broken or replaced, or the obsidian is broken near to it.&lt;/p&gt;</comment>
                            <comment id="342297" author="zebulanstanphill@gmail.com" created="Mon, 14 Nov 2016 06:21:04 +0100"  >&lt;p&gt;Affects 0.17.0.1. Also confirmed to affect redstone lamps. I&apos;m guessing it probably affects note blocks, too, since they are also a redstone component block, but I haven&apos;t actually found a case of the bug happening with those yet as I haven&apos;t tested for them.&lt;/p&gt;</comment>
                            <comment id="339666" author="odus20032222336" created="Tue, 1 Nov 2016 18:46:47 +0100"  >&lt;p&gt;Reloading the world also fix the bug. Or, just simply break the corresponding redstone compoment and replace it back.&lt;/p&gt;</comment>
                            <comment id="339664" author="odus20032222336" created="Tue, 1 Nov 2016 18:37:52 +0100"  >&lt;p&gt;Also it only affects specific pistons and every time the bug happens, it will apply on the specific pistons ONLY. Kind of weird.&lt;/p&gt;</comment>
                            <comment id="333851" author="zebulanstanphill@gmail.com" created="Fri, 7 Oct 2016 16:38:12 +0200"  >&lt;p&gt;Thanks for closing my duplicate issue! &lt;img class=&quot;emoticon&quot; src=&quot;https://bugs.mojang.com/images/icons/emoticons/biggrin.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt; Please update the description/title to reflect the fact that this bug also affects droppers &amp;amp; dispensers as well!&lt;/p&gt;</comment>
                            <comment id="333775" author="nighter" created="Fri, 7 Oct 2016 11:00:20 +0200"  >&lt;p&gt;This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided). &lt;/p&gt;</comment>
                            <comment id="333587" author="zebulanstanphill@gmail.com" created="Thu, 6 Oct 2016 17:36:57 +0200"  >&lt;p&gt;I just tested, and this bug is actually the SAME thing as &lt;a href=&quot;https://bugs.mojang.com/browse/MCPE-17354&quot; title=&quot;Piston / Dispenser / Dropper Becomes Stuck in On or Off State &amp;amp; Acts Like Solid/Opaque Block&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MCPE-17354&quot;&gt;&lt;del&gt;MCPE-17354&lt;/del&gt;&lt;/a&gt;! :O (Also, affects 0.15.10.)&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10102">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="151120">MCPE-17354</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="156430">MCPE-18712</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="174727">MCPE-23094</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="184564">MCPE-28376</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="187081">MCPE-29169</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="194602">MCPE-31287</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10103">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="217084">MCPE-38630</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="248577">MCPE-48054</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="151878">MCPE-17476</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="153793">MCPE-18042</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="155922">MCPE-18570</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="160736">MCPE-19779</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="131900" name="Stuck Piston.mcworld" size="31524" author="Mega_Spud" created="Thu, 5 Jan 2017 16:02:01 +0100"/>
                            <attachment id="152047" name="blocktorch.png" size="881381" author="evrqst123" created="Wed, 29 Nov 2017 00:46:31 +0100"/>
                            <attachment id="151911" name="default.png" size="896695" author="evrqst123" created="Tue, 28 Nov 2017 01:05:55 +0100"/>
                            <attachment id="152048" name="powered block.png" size="749595" author="evrqst123" created="Wed, 29 Nov 2017 00:49:04 +0100"/>
                            <attachment id="151912" name="pushed.png" size="872665" author="evrqst123" created="Tue, 28 Nov 2017 01:07:48 +0100"/>
                            <attachment id="152046" name="tower coordinates.png" size="928358" author="evrqst123" created="Wed, 29 Nov 2017 00:42:34 +0100"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_11500" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>ADO</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>33729</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10701" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>CHK</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 5 Jan 2017 19:27:00 +0100</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10500" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Confirmation Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10303"><![CDATA[Confirmed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_11700" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10402" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Platform</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10760"><![CDATA[Tablet - Android - Samsung Galaxy Tab 3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0n62n:</customfieldvalue>

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