Bug 1000344 - JSON data from server could not be parsed
Summary: JSON data from server could not be parsed
Keywords:
Status: NEW
Alias: None
Product: TCMS
Classification: Other
Component: Application
Version: 3.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Yang Ren
QA Contact: Nobody
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-23 09:04 UTC by Pavel Stehlik
Modified: 2022-03-14 03:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)
tcms-json (141.28 KB, image/jpeg)
2013-08-23 09:07 UTC, Pavel Stehlik
no flags Details
generate report (155.82 KB, image/png)
2013-10-01 12:04 UTC, jianchen
no flags Details

Description Pavel Stehlik 2013-08-23 09:04:04 UTC
Description of problem:
 Trying to search RUNs based on this criteria:
- Product: Red Hat Enterprise Virtualization Manager
- Product version: 3.3-rc

Getting message:
"DataTables warning (table id = 'testruns_table'): DataTables warning: JSON data from server could not be parsed. This is caused by a JSON formatting error."


Version-Release number of selected component (if applicable):
Nitrate 3.8.3, FF 20.0

How reproducible:
100%

Steps to Reproduce:
1. see above
2.
3.

Actual results:


Expected results:
Having results - similar to:
- Product: Red Hat Enterprise Virtualization Manager
- Product version: 3.3-beta1
^^ this suprisingly works

Additional info:

Comment 1 Pavel Stehlik 2013-08-23 09:07:08 UTC
Created attachment 789508 [details]
tcms-json

scrn-sht

Comment 3 jianchen 2013-10-01 12:02:01 UTC
Fail to reproduce the bug.

Generate report based on this criteria:
- Product: Red Hat Enterprise Virtualization Manager
- Product version: 3.3-rc

As attachment.

Comment 4 jianchen 2013-10-01 12:04:17 UTC
Created attachment 805886 [details]
generate report

Comment 7 fhuang 2014-04-14 10:42:41 UTC
Can't reproduce on 3.8.5-4.


Note You need to log in before you can comment on or make changes to this bug.