[GH-ISSUE #2607] Quota and Quota Used % are blank when exported to PDF #1311

Closed
opened 2026-03-02 13:43:12 +03:00 by kerem · 8 comments
Owner

Originally created by @jrandRTCC on GitHub (Jun 26, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2607

Description

1.) Go to Email & Exchange - Reports- Mailbox Statistics
2.) Export Visible Columns as PDF
3.) Quota and Quota Used show in CIPP, but not in the report

CIPP Bug

CIPP Bug2

Environment data

Non-sponsored instance
Front end version number: 5.9.3
Back end version number: 5.9.3
Tried Tenant Cache Clear: true
Tried Token Cache Clear: false
Originally created by @jrandRTCC on GitHub (Jun 26, 2024). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2607 ### Description 1.) Go to Email & Exchange - Reports- Mailbox Statistics 2.) Export Visible Columns as PDF 3.) Quota and Quota Used show in CIPP, but not in the report ![CIPP Bug](https://github.com/KelvinTegelaar/CIPP/assets/66025354/50da8aed-a823-414f-966d-a7b8973328bf) ![CIPP Bug2](https://github.com/KelvinTegelaar/CIPP/assets/66025354/a72c1b1d-d321-47e7-9f98-85046a5fd1d3) ### Environment data ```PowerShell Non-sponsored instance Front end version number: 5.9.3 Back end version number: 5.9.3 Tried Tenant Cache Clear: true Tried Token Cache Clear: false ```
Author
Owner

@github-actions[bot] commented on GitHub (Jun 26, 2024):

Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug."

Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

<!-- gh-comment-id:2191897155 --> @github-actions[bot] commented on GitHub (Jun 26, 2024): Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/ If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug." Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
Author
Owner

@jrandRTCC commented on GitHub (Jun 26, 2024):

I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.

<!-- gh-comment-id:2191898313 --> @jrandRTCC commented on GitHub (Jun 26, 2024): I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
Author
Owner

@github-actions[bot] commented on GitHub (Jul 6, 2024):

This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.

<!-- gh-comment-id:2211578013 --> @github-actions[bot] commented on GitHub (Jul 6, 2024): This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.
Author
Owner

@kris6673 commented on GitHub (Jul 9, 2024):

Fairly sure this is cause we calculate it in the frontend and not backend.
Moving it to the backend should be a fairly easy fix I think?
I'll give it a go when I have the time

<!-- gh-comment-id:2217448297 --> @kris6673 commented on GitHub (Jul 9, 2024): Fairly sure this is cause we calculate it in the frontend and not backend. Moving it to the backend should be a fairly easy fix I think? I'll give it a go when I have the time
Author
Owner

@kris6673 commented on GitHub (Jul 9, 2024):

I would like to work on this please!

<!-- gh-comment-id:2217454169 --> @kris6673 commented on GitHub (Jul 9, 2024): I would like to work on this please!
Author
Owner

@github-actions[bot] commented on GitHub (Jul 9, 2024):

Great! I assigned you (@kris6673) to the issue. Have fun working on it!

<!-- gh-comment-id:2217454483 --> @github-actions[bot] commented on GitHub (Jul 9, 2024): Great! I assigned you (@kris6673) to the issue. Have fun working on it!
Author
Owner

@KelvinTegelaar commented on GitHub (Jul 9, 2024):

We dont want to do this in backend, as we're trying to decrease the amount of APIs and this is a direct graph call. I'll see how we can add it to frontend instead. :)

<!-- gh-comment-id:2217461723 --> @KelvinTegelaar commented on GitHub (Jul 9, 2024): We dont want to do this in backend, as we're trying to decrease the amount of APIs and this is a direct graph call. I'll see how we can add it to frontend instead. :)
Author
Owner

@kris6673 commented on GitHub (Jul 9, 2024):

Fixed in v6.0.0 by @KelvinTegelaar

<!-- gh-comment-id:2218662074 --> @kris6673 commented on GitHub (Jul 9, 2024): Fixed in v6.0.0 by @KelvinTegelaar
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#1311
No description provided.