Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

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?

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?

Problem:

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?

Resolution:

ANSWER
----------------------------------
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 value.

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.

  • Issues might not have the same Issue Type as they had before import
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.


  • The FrontendServer.log file will contain entries like "Unknown defectType "DEFECT" in table DEFECT found" were DEFECT is the value you have changed the Issue Type to instead of the default BUG


  • Defined workflow actions and states might differ
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.


  • Entries in the List of Values might differ
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 prompt:

Go to:

START | RUN

Type:
radar.exe -defectname


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.



Old KB# 23684

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 19:37
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.