Get URL for SCM folder that does not contain the Project Area name
Hello everyone,
I need to get the URL for a SCM folder in order to link it as a Related Artifact to a workitem.
The only URL I could obtain was the one shown in the browser when opening that SCM folder, e.g.:
The problem is that this URL contains the Project Area name, which can cause some problems for us in the future. For example, if the name is changed, then the link would become invalid.
I tried to search for some kind of “shortened” link that contains only ids, but I did not succeed. For workitems this is possible:-link with PA name: https://server:port/ccm/web/projects/Project_Area_Name#action=com.ibm.team.workitem.viewWorkItem&id=workitemId
-link without the PA name: https://server:port/ccm/resource/itemName/com.ibm.team.workitem.WorkItem/workitemId
Do you have any idea how could I obtain the link without the PA name in it?
Kind regards, Ana R. <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> |
One answer
Ralph Schoon (63.5k●3●36●46)
| answered Nov 23 '21, 7:32 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Several issues here.
I am not sure how far it would possible to implement what you want to do. I am not sure what is the business case that would require to do this or we have UI support for it. I know that there are possibilities to select the URIs for some of the objects, but there are some missing.
Comments 
Geoffrey Clemm
commented Nov 23 '21, 2:06 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
On (1), SCM folders are under version control. They need to be created/moved/renamed/deleted in change sets, which need to be delivered, like changes to files.
Geoff, thanks for your feedback. I could be wrong, however:
I think I had attended a meeting last week where it was pointed out that the files are traced, not the folders.
I have worked with the API and the folders are available as predecessor nodes in the path only, as far as I can recall.
Empty folders are not recreated when under source control I had to create fake files that where under SCM to get the folder created.
Geoffrey Clemm
commented Nov 24 '21, 5:16 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
You need to distinguish the root folder in a sandbox where a component is loaded from the folders inside a component. The root folder where a component is loaded is not under version control. All of the folders inside of a component are under version control. So it is true that not all of the folders in a sandbox are under version control, but all folders in a component are under version control. And in particular, if you have empty folders inside a component, and you load that component, all of those empty folders will be loaded in your sandbox (no need for fake files to get them loaded). Hi Geoff,
thanks for the clarification.
|
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.