starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 08:16:01 +03:00

[GH-ISSUE #2864] License count does not aggregate when multiple license periods #1414

New issue

Closed

opened 2026-03-02 13:44:00 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 13:44:00 +03:00

Owner

Originally created by @itstart-mattb on GitHub (Aug 29, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2864

Description

I have a tenant who has two license periods for 18 licenses each. Seem image below:

The licenses are then only showing as 1 of the license periods and not summing together the two.

This then naturally flows on and shows up as an alert for over provisioned licenses

Environment data

Current front end 6.3.0 and backend same

Originally created by @itstart-mattb on GitHub (Aug 29, 2024). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2864 ### Description I have a tenant who has two license periods for 18 licenses each. Seem image below: ![image](https://github.com/user-attachments/assets/0e6d9085-361b-4bc0-8fdb-d98cdc5539b3) The licenses are then only showing as 1 of the license periods and not summing together the two. ![image](https://github.com/user-attachments/assets/6a17c3ac-32ee-4f14-ba30-fdfef634b4fb) This then naturally flows on and shows up as an alert for over provisioned licenses ### Environment data ```PowerShell Current front end 6.3.0 and backend same ```

kerem

2026-03-02 13:44:00 +03:00

closed this issue
added the
bug

unconfirmed-by-user
labels

kerem commented

2026-03-02 13:44:02 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 29, 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!".

@github-actions[bot] commented on GitHub (Aug 29, 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!".

kerem commented

2026-03-02 13:44:02 +03:00

Author

Owner

@itstart-mattb commented on GitHub (Aug 29, 2024):

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

@itstart-mattb commented on GitHub (Aug 29, 2024): I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.

kerem commented

2026-03-02 13:44:02 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Aug 29, 2024):

Not a bug, support issue. If you're a sponsor you can contact support.

@KelvinTegelaar commented on GitHub (Aug 29, 2024): Not a bug, support issue. If you're a sponsor you can contact support.

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#1414

No description provided.

Rows
Columns