Why have my Issue Types, Workflow Actions and States, or Entries in the List of possible Values for Issue Types have changed after upgrading from Issue Manager 3.x to 4.x?
This is a consequence of not configuring the 3.x Issue Manager correctly before importing.
It is vitally important, before importing a 3.x database into
4.x, that any Issue Type which has been set to a custom value is
reset to the default values of BUG, ENHANCEMENT and DOC-ISSUE using
the Administrative Console (Windows client).
Further information on how to do this is contained below. After
the import the values may be changed back to their original
If you fail to make these changes before importing you may
experience the following behaviour with your newly imported
database in Issue manager 4.x.
e.g. if you had renamed an Issue Type to DEFECT instead of the default value of BUG it may no longer appear as Defect.
For example, when you change a State (Assign, Reject, etc) it may not go to the person or group you expect it to be assigned to.
e.g. they may not appear or be combined in a different Issue Type]
You should correct this by making the changes on the backed
up 3.x database and re-importing.
How to change defect type back to original value
Changing the defect name is implemented as the menu item DEFECT NAME CHANGE under the SETUP main menu list in the Administrative console.
You will need to ensure that the user logged in has WORKFLOW
CUSTOMIZATION security permission in their Radar account to use
this menu choice.
The menu selection above is not normally seen on the Setup menu,
to enable it enter "-defectname" as an argument when
starting the Administrative console at the command line or command
START | RUN
SilkRadar will launch and you can go to SETUP | DEFECT NAME
CHANGE to change the Defect Name. Click on GET LOCK before editing
the fields then RELEASE LOCK when done.