Incorrect issue type for Jira workitems in Testiny

Support
, ,
1

Hey Testiny

I’m writing some scripts to handle populating test runs based on the linked Jira requirements, but I’ve found that some workitems in Testiny seem to have the incorrect work item type e.g. bug instead of task. In this case, they are custom Issue types.

The related requirements in Jira have had the Issue type changed since they were linked as requirements in Testiny, so I’m guessing there’s a lag in syncing them somewhere in the backend.

EDIT: Some more digging has turned up Workitem values missing from API call - #2 by hanna_mueller, but after invoking that and waiting a bit it seems the requirements in question still haven’t updated. I can see them listed in the response, so I’m fairly sure I’m getting the right IDs in the request.

2

Hi Ben,

Thanks for reporting the issue - the work item type id is not correctly updated; other values like the status, summary, key etc are synced. This will be fixed with the next release.

In general, the information that is stored directly in Jira (e.g. the status, workitemType, etc) needs to be sycned (as described in the post you’ve linked e.g. with /workitem-integration/workitems?integration_id=34&project_id=1&sync=true&ids=218).
If you need more information than is stored in Testiny, you can also use the Jira API itself to fetch the Jira work items.

Best regards,
Hanna

3

The issue type should now be updated since Testiny v1.30.

Best regards,
Alex