Skip to content

Bug: collaboration_report() cannot run if a required metric does not exist  #177

@martinctc

Description

@martinctc

There are several metrics which will fail on the Ways of Working Assessment query if run on the collaboration_report() because they do not exist. This is due to an internal code within collaboration_report() which explicitly requires some metrics to be input into keymetrics_scan().

This is the error observed:

Columns `Low_quality_meeting_hours`, `Time_in_self_organized_meetings`, `Generated_workload_email_hours`, and `Total_emails_sent_during_meeting` don't exist.

A solution would be to make this dynamic from keymetrics_scan() - if a metric does not exist, simply omit the metric (and return a warning) instead of defaulting to error.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions