It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,875
×10,905
×14

question asked: May 22 '17, 3:47 a.m.
question was seen: 2,032 times
last updated: Jun 07 '17, 4:01 a.m.

Related questions

strange link uri format in rtc oslc

0
Tali Rabetti (111●8●20) | asked May 22 '17, 3:47 a.m.

In my code I go over some work items information, and as part of it I follow the linked work items.

Usually, the linked item uri is in the format:
https://server:port/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/12345


In one case (link type is mentions/textuallyReferenced) the link has a different format:
https://server:port/jazz/web/projects/projectAreaName#action=com.ibm.team.workitem.viewWorkItem&id=12345

This link does not lead to data.
Any idea why this happens and what can I do about it?

One answer

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Donald Nong (14.5k●6●14) | answered May 29 '17, 11:35 p.m.

The second link is for Web UI only. It only works in a browser as it relies on JavaScript pulling in extra data.

Comments
Tali Rabetti commented Jun 01 '17, 2:34 a.m.

Thanks Donald!
Do you know why some of the links appear like this?
Maybe there is a way to avoid this when creating work items..
Is it consistent format?
As I am extracting data via oslc, I can't get the work item information when I encounter such link. I guess I can manually build the link that I need from the work item id at the end, if I assume that the format of this url is consistent.

Thanks!

1
Donald Nong commented Jun 07 '17, 3:39 a.m.

Yes the format is consistent. The web link may be entered by end users manually, in which case you can't really avoid it.

Tali Rabetti commented Jun 07 '17, 4:01 a.m.

Thanks, I will modify the link manually, then.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.