Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Can no longer view another user's change sets in web client after upgrading to RTC 5.0.1

Questions
Tags
Users
Badges
Richard Michelson
(21●1●8●15) edited
Oct 20 '14, 5:26 p.m.
After upgrading to 5.0.1 from 5.0, users receive the following error when attempting to view a change set (owned by a different user) attached to a Work Item in the web client.  "No permission to access the workspace". It does work in eclipse and it does work as an admin user.

0 votes

2 answers
4,223 views
0 votes

2 answers

Permanent link
Lily Wang
(4.9k●7●14) Oct 17 '14, 2:58 a.m.
 Hi Richard,

I have the same issue in RTC 5.0.1. I tested in RTC 4.0.6 which doesn't have the issue.
I compared the two URLs of the change set links and found the format was changed in v5.0.1. 
In RTC 5.0.1, the change set link is:
https://rtc-server:9453/ccm/resource/itemOid/com.ibm.team.scm.ChangeSet/_hrY5EE9OEeSmGtnUXxMVxQ?projectAreaId=_bk3asAJ2EeSiePAi_miXwQ&workspace=_fmA78AJ2EeSAo-lLo6R9pg

if the workspace visibility is Private you will get "No permission to access the workspace". However you can open the the changeset using the URL without "&workspace=".

This maybe a product defect. 

1 vote

Permanent link
Melissa Kivisto
(287●11●21) Dec 24 '14, 3:59 p.m.
I just wanted to add this may also appear if the workspace has since been deleted, in which case you will see "The workspace does not exist".

The above was fixed in RTC 5.0.2.

0 votes

Your answer

Register or log in 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.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Oct 16 '14, 9:47 a.m.

Question was seen: 4,223 times

Last updated: Dec 24 '14, 3:59 p.m.

Related questions
Confirmation Cancel Confirm