<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:27:46 JST 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>PFS-JIRA</title>
    <link>https://pfspipe.ipmu.jp/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.3.4</version>
        <build-number>803005</build-number>
        <build-date>13-09-2019</build-date>
    </build-info>


<item>
            <title>[INSTRM-702] fix heaters keyword or actorkey</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-702</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;There is a discrepencies between heaters keyword and xcu actorkey.&lt;/p&gt;

&lt;p&gt;One of the two needs to be fixed.&lt;/p&gt;</description>
                <environment></environment>
        <key id="13660">INSTRM-702</key>
            <summary>fix heaters keyword or actorkey</summary>
                <type id="3" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10518&amp;avatarType=issuetype">Task</type>
                                            <priority id="10000" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/medium.svg">Normal</priority>
                        <status id="10002" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="The issue is resolved, reviewed, and merged">Done</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="cloomis">cloomis</assignee>
                                    <reporter username="arnaud.lefur">arnaud.lefur</reporter>
                        <labels>
                            <label>SM1</label>
                    </labels>
                <created>Thu, 11 Jul 2019 15:00:12 +0000</created>
                <updated>Wed, 17 Jul 2019 14:21:17 +0000</updated>
                            <resolved>Wed, 17 Jul 2019 13:21:50 +0000</resolved>
                                                                    <component>ics_xcuActor</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                <comments>
                            <comment id="15771" author="cloomis" created="Wed, 17 Jul 2019 13:21:50 +0000"  >&lt;p&gt;This turned out to only be a help/comment string issue.&lt;/p&gt;

&lt;p&gt;Made a git mistake: pushed master after the --no-ff merge but &lt;em&gt;before&lt;/em&gt; ever pushing the ticket branch, then checked out and pushed the ticket branch. That left a dangling branch and no merge commit on master. Not sure it matters for a ticket like this. If there is a way to fix it without a master force push I&apos;d do it.&lt;/p&gt;</comment>
                            <comment id="15773" author="hassan" created="Wed, 17 Jul 2019 14:18:04 +0000"  >&lt;p&gt;Fix was to swap CCD and ASIC names in the &lt;tt&gt;heaters&lt;/tt&gt; keyword.&lt;/p&gt;</comment>
                            <comment id="15774" author="cloomis" created="Wed, 17 Jul 2019 14:21:17 +0000"  >&lt;p&gt;Actually, to be specific, it was just the help strings and the unused long FITS card names which got changed. The field &lt;em&gt;names&lt;/em&gt; refer to circuits 1 and 2.&lt;/p&gt;

&lt;p&gt;The distinction matters, because the names affect the mapping to the arriver database columns, whereas the help/comment strings are no more than &quot;just strings&quot;.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10500" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|zx00v0:9</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10005" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="54">SM1-2019 K</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10002" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Story Points</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                        </customfields>
    </item>
</channel>
</rss>