---
** [tickets:#4987] Artifact links within tickets instance should check itself
first [ss695]**
**Status:** closed
**Milestone:** asf_release_1.2.0
**Labels:** support p3 42cc
**Created:** Fri Sep 21, 2012 08:51 PM UTC by Chris Tsai
**Last Updated:** Sun Jan 04, 2015 08:33 AM UTC
**Owner:** Igor Bondarenko
[forge:site-support:#695]
>My project has 2 ticket system instances, /bugs and /feature-requests. I
>added a comment to a ticket in /feature-requests, containing the Markdown link
>code `[#46]` in order to link to feature request #46 - that is, a ticket in
>the same instance. Click Preview to check, and I find out the link it created
>is to the other ticket instance: /bugs/46 rather than the correct
>/feature-requests/46. (I have to use `[feature-requests:#46]` to work around
>this.)
>Unqualified artifact links in the /bugs ticket instance correctly link to
>tickets under /bugs. But I have 2 other projects (pgtclng and pgintcl) with
>the same problem, in reverse. Unqualified artifact links from inside either
>/bugs or /feature-requests tickets both create links to tickets under
>/feature-requests.
>I see the same problem here. The link `[#4]` is linking to /doc-todo/4 rather
>than /site-support/4 as you can see here: [#4] (At least, that is what I see -
>not sure if you see the same thing.)
>Note that in all these cases, an artifact with the given number exists in both
>of the ticket instances.
In each example he gives, the one it defaults to is the first listed in the
nav. If an artifact is being linked to within a tickets instance, it should
check the instance it's already in first before checking others.
---
Sent from forge-allura.apache.org because [email protected] is subscribed
to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.
