Project

General

Profile

Feature #1515

Feature #1511: Reporting v3

implement gap analysis views in all reports

Added by Greg Shah over 11 years ago. Updated about 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Start date:
09/10/2012
Due date:
% Done:

0%

Estimated time:
8.00 h
billable:
No
vendor_id:
GCD

Related issues

Related to Conversion Tools - Feature #1521: implement gap analysis rules or backing database/marker approach WIP

History

#1 Updated by Greg Shah over 11 years ago

  • Target version set to Milestone 2
  • Estimated time set to 8.00

#2 Updated by Greg Shah over 11 years ago

  • Target version changed from Milestone 2 to 25

#3 Updated by Greg Shah over 7 years ago

  • Target version changed from 25 to Reporting 3.0

#4 Updated by Greg Shah about 7 years ago

This involves updating the profile.rpt and schema.rpt to change the <report> element to include this attribute:

supportLvlExpr="execLib(&quot;read_support_level&quot;, this)" 

This enables the extra columns for support levels in the details reports. Most (if not all) of the reports can be handled using read_support_level function.

In addition, we will want to add a support level column to the top-level summary report. It should show the "worst" level of support that exists in the associated details view. For example, if everything is fully support then the details view would slow all green and the summary row for that report would show green. But if everything in the detail report is green except for 3 yellow and 1 red, then the summary report would show red (because that is the worst level of support in the details view).

#5 Updated by Greg Shah about 7 years ago

  • Related to Feature #1521: implement gap analysis rules or backing database/marker approach added

Also available in: Atom PDF