<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:37:02 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-1577] Verify the mechanism to store pfsDesing/pfsConfig information to opDB</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-1577</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;In the last run, we could not verify ingesting pfsDesign/pfsConfig information to opDB. The current opDB schema for&#160;pfsDesign/pfsConfig and the routine to populate have been implemented as a part of &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/INSTRM-1348&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;INSTRM-1348&lt;/a&gt; . Please verify this for the next engineering run.&lt;/p&gt;</description>
                <environment></environment>
        <key id="22733">INSTRM-1577</key>
            <summary>Verify the mechanism to store pfsDesing/pfsConfig information to opDB</summary>
                <type id="10001" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10515&amp;avatarType=issuetype">Story</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="kiyoto.yabe">Kiyoto Yabe</assignee>
                                    <reporter username="kiyoto.yabe">Kiyoto Yabe</reporter>
                        <labels>
                            <label>EngRun</label>
                            <label>opDB</label>
                    </labels>
                <created>Thu, 14 Apr 2022 02:26:36 +0000</created>
                <updated>Sat, 9 Jul 2022 02:49:42 +0000</updated>
                            <resolved>Sat, 9 Jul 2022 02:47:46 +0000</resolved>
                                                                    <component>ics_iicActor</component>
                    <component>pfs_utils</component>
                    <component>spt_operational_database</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="31110" author="hassan" created="Fri, 8 Jul 2022 14:54:10 +0000"  >&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=kiyoto.yabe&quot; class=&quot;user-hover&quot; rel=&quot;kiyoto.yabe&quot;&gt;Kiyoto Yabe&lt;/a&gt;: has the mechanism been verified? Can we close this ticket?&lt;/p&gt;</comment>
                            <comment id="31116" author="kiyoto.yabe" created="Sat, 9 Jul 2022 00:11:04 +0000"  >&lt;p&gt;I think we verified the mechanism at least for pfsDesign-related tables in June run. There are still blank columns and we have not verified the pfsConfig (and intermediate pfsDesign tables if needed) yet, but a part of them have already been filed and others should be filed in future as separate tickets.&lt;/p&gt;</comment>
                            <comment id="31118" author="hassan" created="Sat, 9 Jul 2022 02:47:46 +0000"  >&lt;p&gt;Based on Yabe-san&apos;s previous comment, implementation necessary for June run has been achieved and additional tickets filed. So closing this one.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="22806">INSTRM-1618</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="17016">INSTRM-1348</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <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|zzstqm:zzy</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10005" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="145">PreEngRun06June</customfieldvalue>

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