Pulling traceability links from Zephyr Scale into eazyBI (Data Center)

Questions & Answers
1

Hi there,

I’m trying to join up my Zephyr Scale data to Jira user stories. We link epics to test cycles and test plans, and I’m looking to create a report which would display information per epic (e.g. description, status, assignee) alongside Zephyr Scale data such as number of linked test cycles, number of linked test plans. Is this possible?

Thanks!

2

Hi @bar368

Yes, you can combine Jira and Zephyr Scale data in one report.
Data on Jira issues are in the “Issue” dimension that works well together with issue properties and standard measures, like “Issue created”, “Story Points resolved”, etc. Issues with linked test cases are also available in the “TM4J Requirement” dimension that works well with TM4J specific measures and dimensions. You can start building a report from one of those dimensions (“Issues” or “TM4J Requirements”) and use calculated measures to refer to other dimesnion.

For example, you may use the “Issue” dimension on your report rows to represent epics and create calculated measures to represent metrics from Zephyr Scale (TM4J) data.

  1. Set Issue dimension on rows and select Epic hierarchy.

  2. On pages, you may set standard dimensions to filter issues (epics), like Priority, Assignee, Project, Status, etc.

  3. On report columns, select measure “Issues created” and filter rows by it:https://docs.eazybi.com/eazybijira/analyze-and-visualize/create-reports#Createreports-Orderandfilterrowsbymeasurevalues.
    Then remove the column; the filter will remain. Filter by measure “issues created” is needed to incorporate page filters to the report.

  4. On report columns, select issue properties you would like to see for your Epics, like “Issue status”, “Issue assignee”, and others.

  5. Define a new calculated measure in Measures to count test cycles are related to the issue (epic). The calculation would go through all test cycles and check whether any of those are related to TM4J Requirementsmatching the Issue key. The expression might look like this:

    NonZero(Count(
  Filter(
    --got through all Test Cycles
    Descendants([TM4J Test Cycle].CurrentMember,[TM4J Test Cycle].[Test Cycle]),
    --checkeck cycle relation to TM4J requirement matching epic key
    DefaultContext((
      [TM4J Requirement].[Requirement].GetMemberByKey(
         [Issue].CurrentHierarchyMember.key),
      [TM4J Test Cycle].CurrentHierarchyMember,
      [Measures].[TM4J Test Cases with Test Cycles]
    )) > 0
  )
))

  6. Define another calculated measure in Measures to count test plans related to the issue (epic). The expression might look like this:

    NonZero(Count(
  Filter(
    --got through all Test Plans
    Descendants([TM4J Test Plan].CurrentMember,[TM4J Test Plan].[Test Plan]),
    DefaultContext((
      [TM4J Requirement].[Requirement].GetMemberByKey(
         [Issue].CurrentHierarchyMember.key),
      [TM4J Test Plan].CurrentHierarchyMember,
      [Measures].[TM4J Test Cases with Test Cycles]
    )) > 0
  )
))

The report might look like in the picture below.

eazyBI Zephyr Scale and epic data
eazyBI Zephyr Scale and epic data2206×1028 208 KB

More details on calculated measures and used function for calculations are here:

Best,
Zane / support@eazyBI.com