Sharing work items across project areas/servers

You can use the OSLC "Change Management" links to link between project areas on different servers (when the project admin has declared that those two project areas are "friends" of each other and support Change Management links). In general, you should be able to link two work items in different project areas on the same server if you have read access to the project areas on those servers.

When you say that "you can't" ... what is the error message that you get when you try to link them?

Cheers,
Geoff

I see that you can share work items across project areas on the same server. What configuration for a project area do you need to do to make this possible? I'm a member of two separate RTC projects currently and in one case I can create dependencies across work items in other projects on the server, but in the other case I can't. Additionally what options exist for linking work items to a project area on another server?

Hi Geoff-

By "can't link" I mean that in the web UI for one project area, I go to a Defect work item, under Links and select "Duplicate Of". In the dialog that pops up I see a dropdown for Project Area and I can select other Project Areas on my server, whereas for the other project area, only my project area is shown in the dropdown and I can't select any other.

As far as creating links between work items for project areas across servers, if I set up the project areas as you mention and then for example I created a Defect that depended on a Defect in another friend Project Area on another server would it be essentially the same as if I created the link with a Project Area on the same server, that is there would be no functional difference?

Thanks,
Jared

I have no explanation for the assymetric behavior you are seeing for two project areas on the same server. If you don't get an explanation on the forum, it would be good to submit a work item describing this situation, so development can look into it.

WRT the difference between linking between work items in the same repository vs. work items in different repositories, you have to use different kinds of links. In particular, there's a fairly rich set of built-in link types when they are in the same repository (some of which, such as parent/child, have important semantics that affect how planning works), but when they are in different servers, you have only a very limited number of link type choices, and those links have no planning semantics.

Cheers,
Geoff

Hi Geoff-

By "can't link" I mean that in the web UI for one project area, I go to a Defect work item, under Links and select "Duplicate Of". In the dialog that pops up I see a dropdown for Project Area and I can select other Project Areas on my server, whereas for the other project area, only my project area is shown in the dropdown and I can't select any other.

As far as creating links between work items for project areas across servers, if I set up the project areas as you mention and then for example I created a Defect that depended on a Defect in another friend Project Area on another server would it be essentially the same as if I created the link with a Project Area on the same server, that is there would be no functional difference?

Thanks,
Jared

I have no explanation for the assymetric behavior you are seeing for two project areas on the same server. If you don't get an explanation on the forum, it would be good to submit a work item describing this situation, so development can look into it.

Sorry I wasn't clear on this. What I meant to say is that I was seeing different behavior on projects on different servers. I'm guessing this is due to the fact that in one case the projects haven't been set up to be friends of each other as you mention above.

WRT the difference between linking between work items in the same repository vs. work items in different repositories, you have to use different kinds of links. In particular, there's a fairly rich set of built-in link types when they are in the same repository (some of which, such as parent/child, have important semantics that affect how planning works), but when they are in different servers, you have only a very limited number of link type choices, and those links have no planning semantics.

Got it... thanks for the prompt responses!

You can use the OSLC "Change Management" links to link between project areas on different servers (when the project admin has declared that those two project areas are "friends" of each other and support Change Management links). In general, you should be able to link two work items in different project areas on the same server if you have read access to the project areas on those servers.

When you say that "you can't" ... what is the error message that you get when you try to link them?

Cheers,
Geoff

I see that you can share work items across project areas on the same server. What configuration for a project area do you need to do to make this possible? I'm a member of two separate RTC projects currently and in one case I can create dependencies across work items in other projects on the server, but in the other case I can't. Additionally what options exist for linking work items to a project area on another server?

and just to be clear, its Friends between SERVERS.. not projects.
and sharing between projects (on the same server)
right?

Yes, I was "oversimplifying" (:-).
Two allow connecting work items in two different servers, you have to both:
- make the two servers friends of each other
- link the two project areas to each other

More detailed description can be found in:
https://jazz.net/help-dev/clm/index.jsp?topic=%2Fcom.ibm.jazz.repository.web.admin.doc%2Ftopics%2Ftenableoslc.html

Cheers,
Geoff

and just to be clear, its Friends between SERVERS.. not projects.
and sharing between projects (on the same server)
right?

 Thank you!