-
Bug
-
Resolution: Fixed
-
High
-
10.87, 10.88
-
None
-
3
-
Severity 2 - Major
-
Rangers VH4
-
No
Issue Summary
Type mismatch occurs when importing Epics with value stream mapping.
Steps to Reproduce
- Create an Epic value stream for a program.
- Configure the process steps for that Epic value stream and map the Epic states.
- Try to import an Epic for that program.
Expected Results
Epic/s is detected and imported successfully.
Actual Results
0 epics found and an exception is captured in the logs:
ASP_function: OOFunctionsSql.dbexecReturnIDLogError correlationid: V35mCcMYFYPF/p2XtVqQOgsq4JoBcJ0mVW7RRm24+KA= customer_db: customername error_description: Type mismatch error_number: 13 error_source: Microsoft VBScript runtime error log_type: exception logfrom_location: Website-ASP sql: SET NOCOUNT On Insert Into tblImportEpic(...
Workaround
Currently, there is no known workaround for this behaviour. A workaround will be added here when available
- is related to
-
JIRAALIGN-2886 [JIRAALIGN-2886] Import : FeatureHeaderRow error due to missing Header & ColumnNames in XML
- Closed
- mentioned in
-
Page Loading...
- resolves
-
ALIGNSP-8009 Loading...
-
ALIGNSP-8108 Loading...