error when hit GET /get_plan using API v2

[indraaristya]

500 status code error was occurred when I tried to hit /get_plan endpoint.
Body response: Undefined property: stdClass::$dataset_id

{
    "error": "Undefined property: stdClass::$dataset_id"
}

[shaheelroshankhan]

I'm also hitting the same. Other APIs are working fine
APIError: TestRail API returned HTTP 500 ({'error': 'Undefined property: stdClass::$dataset_id'})

[bdfariello]

We're seeing the same in our TestRail Cloud instance

TestRail version: 7.8.0 Default (1136)
Built On: 1/25/2023
Database version: 20230105013501

We only started noticing it today

[Moriarty16]

The same error while querying "api/v2/get_plan": "error": "Undefined property: stdClass::$dataset_id"

[bdfariello]

Something else I noticed today - we have some api/v2/get_plan/{plan_id} requests working successfully, while others do not

It seems like there was an attribute change in the back-end Test Plan objects, and so Plans created BEFORE we got this update trigger this bug, while Plans created AFTER we got this update do NOT trigger the bug.

[sf0319]

Just wanted to pile to try and get more attention to this issue. I am seeing the exact same error for our instance as well since updating to TestRail version: 7.8.0 Default (1136).

[indraaristya]

Something else I noticed today - we have some api/v2/get_plan/{plan_id} requests working successfully, while others do not

It seems like there was an attribute change in the back-end Test Plan objects, and so Plans created BEFORE we got this update trigger this bug, while Plans created AFTER we got this update do NOT trigger the bug.

I've tried to update the test plan (only change the name) and save it then api/v2/get_plan/{plan_id} works perfectly again. Thanks!

[indraaristya]

[UPDATE]

You guys might need to update the test plan, try to change the name only or else and save it. The api/v2/get_plan/{plan_id} endpoint should be working fine after that. I've tried mine and it's works.

[sf0319]

@indraaristya I wouldn't say that this issue is Resolved (or ready to be closed) just because there is a workaround. I would appreciate it if this bug was re-opened so that Gurock could address it and make a proper fix.

[indraaristya]

@indraaristya I wouldn't say that this issue is Resolved (or ready to be closed) just because there is a workaround. I would appreciate it if this bug was re-opened so that Gurock could address it and make a proper fix.

Sure, done.

[Moriarty16]

4 days ago, request for plan A via this API fails, today the same request for plan A is successful.
However, request for another plan B still fails with the same error today.

[bdfariello]

Gurock has confirmed in a Tech Support case that I filed that they have internally reproduced the bug, but have not provided a timeline for its resolution.

…

On Mon, Feb 13, 2023, 3:54 AM MadHatter ***@***.***> wrote: 4 days ago, request for plan A via this API fails, today the same request for plan A is successful. However, request for another plan B still fails with the same error today. — Reply to this email directly, view it on GitHub <#39 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACDIDR7JJIWDOFS3SAWXCH3WXHZEHANCNFSM6AAAAAAUSDTYXU> . You are receiving this because you commented.Message ID: ***@***.***>

[SarLecobee]

Also started noticing this issue today.

[patrick-cichon-gcx]

We're also having the same issue since approximately a week