It's all about the answers!

Ask a question

Data mapping: Dealing with nonexistant users / contributors


Gerry Cullen (4651) | asked Mar 11 '11, 4:49 p.m.
We are in the process of migrating our 40k CQ records into RTC. There are a number of users referenced in these records who are no longer with the company. One such record looks something like this:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<bugzilla version="3.3" urlbase="">
<bug>
<dbid>33559630</dbid>
<bug_id>WTX00005198</bug_id>
<id>WTX00005198</id>
<Headline>gbc: Test heading</Headline>
<ECase_id>111159</ECase_id>
<State>Closed</State>
<Resolution>Informational</Resolution>
<DefectType>PMR</DefectType>
<Product>DATASTAGE TX</Product>
<Component>ADAPTER ORACLE 9I</Component>
<Crit>0</Crit>
<DefectSource>External</DefectSource>
<CompOwner.fullname>Gerry Cullen</CompOwner.fullname>
<Priority>3</Priority>
<Description>Description of this issue</Description>
<long_desc>
<who name="Admin">admin@mycompany.com</who>
<bug_when>2007-04-09 10:35 -0400</bug_when>
<thetext>

Text of the issue...

</thetext>
</long_desc>
</bug>
</bugzilla>


The line in this record I'm having trouble with is the one that starts with"<who name=...". The email address "admin@mycompany.com" is not in our RTC project and belongs to a person who is longer with the company. When I try to import this record when logged in as myself (gcullen@mycompany.com), I get the following error dialog:

Error Importing ClearQuest Records

Could not create work item from bug WTX00005198
User "gcullen@mycompany.com" does not have the required permission to perform this operation. The "JazzAdmins" role is required to perform this operation.


If I update the line to replace "admin@mycompany.com" with "gcullen@mycompany.com", it imports just fine.

How do I get around this problem? What I would *really* like to do is keep the CQ record as it is so that we know who was involved with the issue originally, even though they no longer work here. Is this a valid thing to do in RTC? Would the nonexistant users require user licenses?

For testing purposes, I thought I would map the email addresses that are no longer valid to addresses that are. I tried doing this in the mapping file in the following manner, but it didn't work:

<attribute sourceId="history.user_name" targetId="com.ibm.team.workitem.attribute.creator" />

<attribute sourceId="CompOwner.fullname" targetId="com.ibm.team.workitem.attribute.owner" />
<attribute sourceId="who.name" targetId="com.ibm.team.workitem.attribute.owner" />
<attributeType targetId="contributor">
<value sourceId="gcullen@mycompany.com" targetId="Gerry Cullen"/>
<value sourceId="admin@mycompany.com" targetId="Gerry Cullen"/>
<value sourceId="Admin" targetId="Gerry Cullen"/>
</attributeType>


Seems like the person in https://jazz.net/forums/viewtopic.php?t=12643 was doing something similar.

Answers / suggestions for both questions would be greatly appreciated.

3 answers



permanent link
Lorelei Ngooi (1.5k22) | answered Mar 13 '11, 7:02 p.m.
JAZZ DEVELOPER
When performing the import, the CQ Importer will create RTC contributors if they don't already exist. The user running the import must have a JazzAdmins repository role in order to create RTC contributors. Getting that error means that your account does not have that repository role.


If I update the line to replace "admin@mycompany.com" with "gcullen@mycompany.com", it imports just fine.


The reason why this works is because no RTC contributor is being created; it's using an existing RTC contributor.


How do I get around this problem? What I would *really* like to do is keep the CQ record as it is so that we know who was involved with the issue originally, even though they no longer work here. Is this a valid thing to do in RTC? Would the nonexistant users require user licenses?


Assign your user account the JazzAdmins repository role. What you are trying to do is valid. Non-existent users would not require user licenses.

You won't be able to do the email address mapping with the long_desc field, but you can do it with a simple user field such as the following:

<attribute sourceId="Owners" targetId="com.ibm.team.workitem.attribute.owner" />
<attributeType targetId="contributor">
<value sourceId="harrisk" targetId="bob" />
<value sourceId="fleenorj" targetId="bob" />
</attributeType>

permanent link
Gerry Cullen (4651) | answered Mar 16 '11, 8:00 a.m.
Now that my user account has JazzAdmins repository role, I'm able to successfully import the CQ records that reference nonexistent users.

Now I see that the mapping I did for certain users was not quite correct. I can go into the thick client and from the navigator choose the Process Template view. If I right click on it and select Administer -> Open Users..., I can search for and find the user that just got added. If I open the user record, I can view the values associated with the user, but most of the fields I'm interested in changing are in read-only mode. Is there a way I can edit the non-existent users once they are imported? What if I archive them? Can I reimport them with different values?

I also have a user-related question regarding functionality in the thick client versus the Web UI. In the Web UI, I can go to the upper right hand corner of the screen and select Administration -> Users, and I will see a complete list of all the active users. Is there a similar screen available in the thick client?

permanent link
Lorelei Ngooi (1.5k22) | answered Mar 16 '11, 10:39 a.m.
JAZZ DEVELOPER
I think the reason why you can't edit the imported users is because the jazz server is configured to use an external user registry. If it were configured to use tomcat, you should be able to modify the user attributes.

You won't be able to re-import users.

There's isn't a similar screen in the thick client to display all users.

I have contacted someone else who is more familiar with the user administration area of RTC.

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.