seed icon indicating copy to clipboard operation
seed copied to clipboard

Improve Variable use on Reports

Open perryr16 opened this issue 2 years ago • 2 comments

Users couldn't get a combination of variables on the axis in a way that felt useful

perryr16 avatar May 12 '22 17:05 perryr16

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Jul 18 '22 02:07 github-actions[bot]

Add ability for user to select more fields in the Reports section

nllong avatar Aug 04 '22 16:08 nllong

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Oct 04 '22 02:10 github-actions[bot]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Dec 04 '22 02:12 github-actions[bot]

I think we can close this as reports have but completely redone.

haneslinger avatar Dec 21 '22 00:12 haneslinger

There is still work to be done on the Inventory Reports (not the Custom Reports in the Insight section).

So I think we should keep this open.

There are only 3 variables available for the Y Axis, which is definitely not enough. image

RDmitchell avatar Dec 21 '22 02:12 RDmitchell

It was my understanding this page would be depreciated in favor on the insight pages. Is there a reason we would keep it?

haneslinger avatar Dec 21 '22 17:12 haneslinger

It is a much simpler report than Insights, and I think we should keep it.

But I guess maybe that needs some discussion in January 2023 !!

So I would say we should keep it for now and talk about how it fits in with other reporting.

RDmitchell avatar Dec 22 '22 19:12 RDmitchell

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Feb 21 '23 02:02 github-actions[bot]

I am adding this to the Q2 project, because of my discussion with San Francisco, where they thought that the Reports were much better aligned with their needs for electrification and net zero compliance

RDmitchell avatar Feb 21 '23 18:02 RDmitchell

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Apr 23 '23 02:04 github-actions[bot]

I am closing this ticket, development on this page is being done via SCEP updates on other tickets

isalanglois avatar May 19 '23 17:05 isalanglois

@isalanglois -- can you list the SCEP tickets that are relevant to this? I would be interested to know what the changes are to the reports for that user, and whether those changes will also appear for the non-SCEP users.

Also, see the comment about San Francisco finding the existing reports useful -- have you consulted with them to see what their reporting needs are?

RDmitchell avatar May 19 '23 19:05 RDmitchell

@isalanglois -- Looking at the SCEP project, I don't see an issue there that refers to this problem.

I think we should reopen this issue and put it on the SCEP project if that project is interested in these reports. Otherwise put it in the Q4 project.

RDmitchell avatar May 24 '23 20:05 RDmitchell

@isalanglois -- I see that the Reports have been moved to Insights and are now called Default Reports.

But I think the original idea of this issue is that we need to think more about what variables are available to be plotted.

Right now the X-Axis has lots of variables but the Y-Axis only has 3, which doesn't make sense.

So I am reopening this issue and moving it to the Q4 project and maybe we can have a discussion about the best way to address this issue

RDmitchell avatar Jun 29 '23 04:06 RDmitchell

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Aug 29 '23 01:08 github-actions[bot]

This issue has been closed automatically. If this still affects you please re-open this issue with a comment or contact us so we can look into resolving it.

github-actions[bot] avatar Sep 06 '23 01:09 github-actions[bot]

I am closing this issue, because I have made a new issue #4369

I don't know what the new reporting features for SCEP are, but there is definitely a need, from developers and users, for more flexible general reporting functionality.

RDmitchell avatar Oct 26 '23 23:10 RDmitchell