<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:50:25 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>[INFRA-199] Abbreviations list: make searchable</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INFRA-199</link>
                <project id="10001" key="INFRA">Software Development Infrastructure</project>
                    <description>&lt;p&gt;The abbreviations tsv file&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/Subaru-PFS/doc/blob/master/misc/PFS_Abbreviations.tsv&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://github.com/Subaru-PFS/doc/blob/master/misc/PFS_Abbreviations.tsv&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;contains double quotes (&quot;) which prevent GitHub from rendering the document searchable, which is a useful feature. See &lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/isaacs/github/issues/848&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://github.com/isaacs/github/issues/848&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;for example.&lt;/p&gt;

&lt;p&gt;The simplest solution is to change the double-quote to single quotes (&apos;) where possible.&lt;/p&gt;</description>
                <environment></environment>
        <key id="12338">INFRA-199</key>
            <summary>Abbreviations list: make searchable</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="hassan">hassan</assignee>
                                    <reporter username="hassan">hassan</reporter>
                        <labels>
                    </labels>
                <created>Thu, 10 May 2018 14:35:13 +0000</created>
                <updated>Wed, 15 Aug 2018 18:42:22 +0000</updated>
                            <resolved>Tue, 14 Aug 2018 13:42:59 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                <comments>
                            <comment id="13390" author="atsushi.shimono" created="Thu, 10 May 2018 14:44:19 +0000"  >&lt;p&gt;if we want to follow BNF strictly, both single and double quote are illegal, but if github allows only single quote in a stupid way, we may be better to use single instead of double. but as you know, main target of this data is not to make searchable on github, so no one shall care whether it is single or double.&lt;/p&gt;</comment>
                            <comment id="13392" author="hassan" created="Thu, 10 May 2018 17:06:49 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=atsushi.shimono&quot; class=&quot;user-hover&quot; rel=&quot;atsushi.shimono&quot;&gt;shimono&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Yes, I understand from you that these data would be transformed into a (potentially searchable) form on the pfspipe website. But until that is done, if it is at least in a searchable form at some intermediate location that helps me a lot (hopefully others also). So making the small investment of making minor changes in the TSV file would be of significant benefit.&lt;/p&gt;</comment>
                            <comment id="13788" author="atsushi.shimono" created="Wed, 18 Jul 2018 16:24:19 +0000"  >&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=hassan&quot; class=&quot;user-hover&quot; rel=&quot;hassan&quot;&gt;hassan&lt;/a&gt; note you may be interested to this issue&lt;br/&gt;
&lt;a href=&quot;https://github.com/Subaru-PFS/pfs_www/issues/86&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://github.com/Subaru-PFS/pfs_www/issues/86&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="13790" author="hassan" created="Wed, 18 Jul 2018 16:28:57 +0000"  >&lt;p&gt;Yes, noticed that and am interested. But can I ask why that was raised as a GitHub issue and not a JIRA issue?&lt;/p&gt;</comment>
                            <comment id="13909" author="atsushi.shimono" created="Tue, 14 Aug 2018 09:00:45 +0000"  >&lt;p&gt;pfs_www is not open since we may include branch for public news release with specified public date, therefore we cannot handle any ticket for that repo on this OSS JIRA site.&lt;/p&gt;</comment>
                            <comment id="13911" author="hassan" created="Tue, 14 Aug 2018 13:42:59 +0000"  >&lt;p&gt;Specific request of correcting PFS_Appreviations.tsv file has been done. Issue fixed.&lt;/p&gt;</comment>
                            <comment id="13918" author="hassan" created="Wed, 15 Aug 2018 18:42:22 +0000"  >&lt;p&gt;@shimono, regarding GitHub issue 86, we can create a private project on JIRA to track such issues. See &lt;a href=&quot;https://community.atlassian.com/t5/Questions/How-can-I-make-a-private-project/qaq-p/26194&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://community.atlassian.com/t5/Questions/How-can-I-make-a-private-project/qaq-p/26194&lt;/a&gt; for example.&lt;/p&gt;

&lt;p&gt;Perhaps I should create a separate JIRA issue on this thread?&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="12214">INFRA-188</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|ii04jj:</customfieldvalue>

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