Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Asset links should be bidirectional #58

Open
jacobsevart opened this issue Jul 16, 2013 · 4 comments
Open

Asset links should be bidirectional #58

jacobsevart opened this issue Jul 16, 2013 · 4 comments

Comments

@jacobsevart
Copy link

Unless I am missing something, and this should already be happening? Right now if I specify an asset as "running on" another asset, the URL for the machine is listed on the software page, but not vice versa.

@jacobsevart
Copy link
Author

I am able to add bidirectional links by searching for the asset. It only fails to work both ways when I do it by URL.

@btb
Copy link
Member

btb commented Jul 23, 2013

What URL are you entering? An asset link URI needs to be of the form at://example.com/asset/1

@jacobsevart
Copy link
Author

Ah. I was using HTTP urls for the asset's pages in RT. like
http://ticketing.my_organization.com/AssetTracker/Asset/Display.html?id=114

How do I get an asset URI in that form?

On Tue, Jul 23, 2013 at 3:36 AM, Bradley Bell [email protected]:

What URL are you entering? An asset link URI needs to be of the form at://
example.com/asset/1


Reply to this email directly or view it on GitHubhttps://github.com//issues/58#issuecomment-21400226
.

@btb
Copy link
Member

btb commented Jul 23, 2013

for your example, it ought to be at://ticketing.my_organization.com/asset/114
although technically the hostname part would be whatever "Organization" is set to in your RT_SiteConfig.pm

It would be nice if there was an extension that automatically translated http URLs for tickets and assets to their respective internal URIs

@btb btb closed this as completed Jul 23, 2013
@btb btb reopened this Jul 23, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants