Details
-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
5.1, 5.2.8
-
None
-
5.01
-
Description
When you are viewing the XML view of a list of issues, the XML tree has a field call link, with the URL to the issue. This link is relative to the URL used in the request.
Example:
The URL http://192.168.35.133:8181 return:
<rss version="0.92"> <channel> <title>Your Company JIRA</title> <link> http://192.168.35.133:8181/secure/IssueNavigator.jspa?reset=true&jqlQuery= </link> <description>An XML representation of a search request</description> <language>en-us</language> <issue start="0" end="301" total="301"/> <build-info> <version>6.0-beta1</version> <build-number>6080</build-number> <build-date>15-04-2013</build-date> </build-info> <item> <title> [SDFDSFSD-301] Bishoprics windscreens emulsification teasel's Whitfield's celibacy subsistence's residuals clearing </title> <link>http://192.168.35.133:8181/browse/SDFDSFSD-301</link> <project id="10000" key="SDFDSFSD">sdfdsfsd</project> <description> <p>Whiffed Balanchine's Spaniard's systematized glamorously cordon acknowledgment Josephus's Chile's reunify reproachful biweekly rakish Fredrick's improvisation's tailgate's tenor Bulganin's Reaganomics's Fijian's caseload scraper truculence's transitting</p> </description> <environment/> <key id="10300">SDFDSFSD-301</key> <summary> Bishoprics windscreens emulsification teasel's Whitfield's celibacy subsistence's residuals clearing </summary> ...
Same JIRA server now using the hostname instead: http://littertray:8181
<rss version="0.92"> <channel> <title>Your Company JIRA</title> <link> http://littertray:8181/secure/IssueNavigator.jspa?reset=true&jqlQuery= </link> <description>An XML representation of a search request</description> <language>en-us</language> <issue start="0" end="301" total="301"/> <build-info> <version>6.0-beta1</version> <build-number>6080</build-number> <build-date>15-04-2013</build-date> </build-info> <item> <title> [SDFDSFSD-301] Bishoprics windscreens emulsification teasel's Whitfield's celibacy subsistence's residuals clearing </title> <link>http://littertray:8181/browse/SDFDSFSD-301</link> <project id="10000" key="SDFDSFSD">sdfdsfsd</project> <description> <p>Whiffed Balanchine's Spaniard's systematized glamorously cordon acknowledgment Josephus's Chile's reunify reproachful biweekly rakish Fredrick's improvisation's tailgate's tenor Bulganin's Reaganomics's Fijian's caseload scraper truculence's transitting</p> </description> <environment/> <key id="10300">SDFDSFSD-301</key> <summary> Bishoprics windscreens emulsification teasel's Whitfield's celibacy subsistence's residuals clearing </summary> ...
The problem with this is that when this XML is a feed to another application (i.e.: a Confluence JIRA Issues macro), the links for the issues will make reference to the address used instead of the server base URL. In this case, it is a common setup to have Confluence and JIRA running in the same private network and they may not be able to contact each other in their public URL, but using a private IP or hostname will lead to broken links for end users.
I think all links served by JIRA should use the server base URL instead of the URL used in the request.
Attachments
Issue Links
- relates to
-
-
- Closed
-
-
JRASERVER-33298 Figure out what we're going to do with Configured (Base) URL vs Detected URL
- Closed