Jira Work Item Panel

The Jira Work Item Panel is how BesTest meets your team where they already are. Open any work item - an epic, a story, a bug - and the BesTest panel sits in the main column of the issue. There is no separate tab to hunt for and no second tool to log into; the testing context lives on the issue itself.

The panel opens with release readiness: a pass rate across everything linked to the work item, with toggles to include test cases that come in via linked requirements and to roll up all descendant work items. Below it, the Traceability section lists the linked requirements with their coverage and status, the test cases with their recent runs, and the test executions with their test case and cycle keys as links. It is the same readiness signal as the Work Item Traceability report, without leaving the issue.

The panel is not read-only. Use Link to attach existing requirements, test cases or cycles (anything already linked shows as selected), or create new ones inline. When a story arrives with a list of acceptance criteria or scenarios, Create in bulk turns one name per line into that many requirements or test cases, with shared fields set once - all linked to the work item. A required custom field no longer blocks a quick create from here.

Turning it on is easy to miss if you do not know where to look, which is why teams ask about it: on a Jira work item, open the Apps ("...") menu in the toolbar under the summary and pick BesTest. The panel is pinned into the issue for everyone on your team. Because every test object is a BesTest record rather than a Jira issue, none of this bloats your backlog - the work item gains full traceability while your Jira instance stays clean and fast.