Question on cross-projects development in different locale
Hello,
A project team is located in three sites,China, UK, and Japan. The locale of these user machines are Chinese, English, and Japanese. When these users connect to a project area, information is displayed in the language of the process template applied for the project area rather than their own language. I understand that this is working as designed and there is an enhancement request. (Enhancement 73969: https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=73969). Therefore I am considering to create three Project area using each language process template (i.e. same process but different locale) as a workaround. Each site has own module to develop as below: Project (* this is not a project area. Just a logical level) | -- Project Area1 | Locale: Japanese | Develop Module1 | -- Project Area2 | Locale: English | Develop Module2 | -- Project Area3 Locale: Chinese Develop Module3 I am thinking the following scenario: 1) Story type work item will be created in "Project Area1" 2) The Story will be copied to "Project Area2" and "Project Area3" 3) Each site will be assigned a module to develop. 4) Each site will create sub workitems of the Story for developing the module 5) Associate the Work item to change set and deliver to the repository (Use Jazz SCM) 6) Import Module 2 and Module 3 to "Project Area1" and build those modules 7) Testing team in Japan will test and create defects in "Project Area1" 8) Copy/move the defect workitems to "Project Area2" and "Project Area3" 9) Each site will fix their module's defects in their project area 10) Load the modules which contains the fixes to "Project Area1" 11) Repeat 7), 8), 9), and 10) The above scenario involves copy/move work items and share modules between different locale project area. Would it be supported? Thanks, Toshi |
4 answers
Hello, Hi Toshi, For copy/move work items between different project areas, RTC supports it, you could open the worktem and click the item icon, and then select "Move/Copy to Project Area...". You could also add stream/component of another project area to share your modules. Kevin Jazz Process Authoring |
Hello, Hi Toshi, For copy/move work items between different project areas, RTC supports it, you could open the worktem and click the item icon, and then select "Move/Copy to Project Area...". You could also add stream/component of another project area to share your modules. Kevin Jazz Process Authoring Hi Kevin, Thank you very much for your response. The point of this question is those three project areas' locale are different. I would like to confirm that copy/move work items and share modules between different project areas which are in DIFFERENT LOCALE are supposed to work fine by design. Is this correct? Thanks, Toshi |
I would like to confirm that copy/move work items and share modules When we copy/move work item's across project areas, we try to map severities, priorities, types etc. by ID. So if you use e.g. the same process template but in different languages for the project areas, I wouldn't expect any mapping problems. All severities, priorities, types etc. should match their translated counterpart in the other project area. It is different for Categories (Filed Against). They don't have an internal identifier that is independent of the name. But I assume the category hierarchy would be different in the project areas anyway? -- Regards, Patrick Jazz Work Item Team |
I would like to confirm that copy/move work items and share modules When we copy/move work item's across project areas, we try to map severities, priorities, types etc. by ID. So if you use e.g. the same process template but in different languages for the project areas, I wouldn't expect any mapping problems. All severities, priorities, types etc. should match their translated counterpart in the other project area. It is different for Categories (Filed Against). They don't have an internal identifier that is independent of the name. But I assume the category hierarchy would be different in the project areas anyway? -- Regards, Patrick Jazz Work Item Team Hello Patrick, Thank you very much for your reply and I am sorry for the delay in responding. I was on leave. > But I assume the category hierarchy would be different in > the project areas anyway? Yes, the category hierarchy is different in the project areas. So, at step 7) in the scenario, WIs will be created in "Project Area1". When the WIs are copied/moved to "Project Area2" and "Project Area3" at step 8), users of "Project Area2" and "Project Area3" have to specify "File against" field manually. Is this correct? Also, could you please let me know whether there would be problems or not with importing and exporting modules between different locale project area while developing them? Thanks, Toshi |
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.