Copy work item does not copy attachments
4 answers
What version of RTC did you have this issue? I just tested with RTC 4.0.3 and there is no problem at all to access to the attachment in the copied workitem in another project area.
I guess that the problem could be in the source workitem in which the attachment is not appearing as file name only instead it may have local path to the file and that could lead to the problem you are seeing. If your source project area is in IE8(or higher) and see the attachment showing in full path to the local machine, you may want to try the below solution:
1. Open Internet Explorer options from Tools > Internet Options
2. Select Security tab
3. Click Custom Level ...
4. In the Miscellaneous section look for option called "Include local
directory path when uploading files to a server".
5. Click Disable
Then attach the file again and confirm it will be a file name only in workitem's link then copy to another project and see if that works now.
Hopefully this helps.
Don
Comments
Thanks for the quick reply Don. We will try what you proposed above. However it is strange that the user can see the attachment when he belongs to the source project area. And sees the "Unknown" and "NaN" when not a member. So the RTC server must be deciding to send the "Unknown" and "NaN" text based on membership and access control rules. I am not confident the problem is in the browser.
You could be right that the issue may not related to the one I mentioned. I remember I saw this issue some time ago but I tried in v4.0.3 now for the above use case, I don't see any problem. What version do you use now? It could be an issue in relative old version and was fixed now.
We are using 4.0.3 and see the same issue.
Hi Rachel,
The behavior is as expected from product point of view. I found the below note from the Infocenter:
https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.team.workitem.doc/topics/t_triaging_work_items.html&scope=null
Note: To access attachments in a work item that is copied to a different project area, users must have permissions to access the project area that contains the source work item.
Hence the user needs to have the access to the source project area in order to access to the copied workitem's attachment.
The workaround I can think is:
1) if the workitem is no longer used in source project area, use the Move instead of copy to move the workitem to another project area, in that case, the users in the target project area should be able to access to the attachment.
2) if the workitem is need in the source project area, try to duplicate the workitem first in the source project area and then move it to the target project area, this will make the two identical workitems in the two project areas.
Well i am glad that IBM agreed it is a required enhancement and plan to include it in next release - see:70127- Copy Of Attachments