<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:49:08 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-73] Attempting to display the system dashboard generates a warning</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INFRA-73</link>
                <project id="10001" key="INFRA">Software Development Infrastructure</project>
                    <description>&lt;p&gt;If you go to the &lt;a href=&quot;https://pfs.ipmu.jp/jira/secure/Dashboard.jspa&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;system dashboard&lt;/a&gt; it complains about misconfiguration, and the details begin:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;We&apos;ve detected a potential problem with JIRA&apos;s Dashboard configuration. Hide Close&lt;br/&gt;
Dashboard Diagnostics: Mismatched URL Scheme&lt;br/&gt;
JIRA is reporting that it is using the URL scheme &apos;http&apos;, which does not match the scheme used to run these diagnostics, &apos;https&apos;. This is known to cause JIRA to construct URLs using an incorrect hostname, which will result in errors in the dashboard, among other issues.&lt;br/&gt;
The most common cause of this is the use of a reverse-proxy HTTP(S) server (often Apache or IIS) in front of the application server running JIRA. While this configuration is supported, some additional setup might be necessary in order to ensure that JIRA detects the correct scheme.&lt;br/&gt;
The following articles describe the issue and the steps you should take to ensure that your web server and app server are configured correctly:&lt;br/&gt;
Gadgets do not display correctly after upgrade to JIRA 4.0&lt;br/&gt;
Integrating JIRA with Apache&lt;br/&gt;
Integrating JIRA with Apache using SSL&lt;br/&gt;
If you believe this diagnosis is in error, or you have any other questions, please contact Atlassian Support.&lt;/p&gt;&lt;/blockquote&gt;</description>
                <environment></environment>
        <key id="10115">INFRA-73</key>
            <summary>Attempting to display the system dashboard generates a warning</summary>
                <type id="1" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10503&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/major.svg">Major</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="atsushi.shimono">shimono</assignee>
                                    <reporter username="rhl">rhl</reporter>
                        <labels>
                    </labels>
                <created>Fri, 18 Jul 2014 18:35:55 +0000</created>
                <updated>Wed, 16 Nov 2016 16:36:19 +0000</updated>
                            <resolved>Sat, 19 Jul 2014 15:01:12 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                <comments>
                            <comment id="10103" author="rhl" created="Sat, 19 Jul 2014 15:01:12 +0000"  >&lt;p&gt;Resolved when &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/INFRA-72&quot; title=&quot;Searching in Jira fails&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INFRA-72&quot;&gt;&lt;del&gt;IPMU-2&lt;/del&gt;&lt;/a&gt; was resolved.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="10116">INFRA-72</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|090000:</customfieldvalue>

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