It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,884
×4,712
×33

question asked: Feb 11 '16, 5:51 a.m.
question was seen: 2,986 times
last updated: Jul 02 '21, 11:10 a.m.

Related questions

Removing custom work item types from RTC project area

0
Alastair Raith (1●3●4) | asked Feb 11 '16, 5:51 a.m.
 We are using RTC 5.0.2 and we have some custom work item types that were developed in a project area, and there are now many work items that were created as part of the initial testing of that work item in that area.

The custom work item is now being actively used in a new project area and we want to remove the custom work item type in the original project area so that users do not have the option to create those work items in the original project area.

If we remove those work item types in the original project area, can we still view the work items that were created, or do we lose access to them?

My first thought was to move those work items to the new project area, but the custom work item types have been renamed in the new area, so it does not migrate them to the correct type in the new area. Would it simply be a matter of renaming the work item type in the original area to match that in the new area for it to move the records successfully?

One answer

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Ralph Schoon (63.6k●3●36●47) | answered Feb 11 '16, 6:24 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I would suggest to
  1. Remove the permission to create the work items you don't want any longer from all roles
  2. Change the type of the old work items to a type that you will keep
  3. Then remove the types you don't want any longer
  4. In the future use a test system to develop the process
  5. Use process sharing to have a better control over the process
Comments
Brad Morse commented Jul 02 '21, 10:37 a.m. | edited Jul 02 '21, 11:10 a.m.

 We are in the initial stages of setting up multiple project areas to support our customer projects. We have looked at sharing process from a master project area to other project areas to enable change one change all. Also, we have looked at not using process sharing and instead using a process template to update project areas with the changes. 


Which is the best and why?

Ralph Schoon commented Jul 02 '21, 11:10 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

What is this business to try to ask a question by providing an answer on a totally unrelated question? Please do what you did and ask your own question. Do not mess up other questions.

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.