[#JRA-10876] Ensure that issue and filter views use the context path of the request URL rather than the baseurl property

JIRA

JRA-10404

Ensure that issue and filter views use the context path of the request URL rather than the baseurl property

Created: 15/Aug/06 09:55 PM Updated: 26/Oct/06 07:17 PM

Component/s:

None

Affects Version/s:

3.7

Fix Version/s:

3.7

Time Tracking:

Original Estimate:

2 hours

Remaining Estimate:

0 minutes

Time Spent:

7 hours

Issue Links:

Reference

This issue relates to:

JRA-11303 Convert usages of $req.getContextPath() to $reqContext in velocity

Participants:	=Neal Applebaum, Anton Mazkovoi [Atlassian] and Scott Farquhar [Atlassian]
Since last comment:	1 year, 45 weeks, 4 days ago
Resolution Date:	26/Oct/06 07:17 PM
Labels:

Description

« Hide

At the moment all the links generated by issue views (and I believe filter views) use the base URL application property as a prefix. The problem is that sometimes JIRA is accessed from 2 or more different locations using different URLs. To ensure the links work in all cases, the context path from the request object needs to be used instead of the base URL property.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

=Neal Applebaum added a comment - 16/Aug/06 05:51 PM

Not sure if this is relavant, but I recall an issue where the baseurl is used when displaying a link in change history.

[ Permlink | « Hide ]

Scott Farquhar [Atlassian] added a comment - 15/Oct/06 07:32 AM

This should be done using the VelocityRequestContext described in JRA-11303.