mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #990] FEATURE REQUEST: List Tenant Name on Reports Instead of Just Default Domain #520
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#520
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @PremierOneData on GitHub (Jun 23, 2022).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/990
Is your feature request related to a problem? Please describe.
Some screens/reports such as /tenant/standards/bpa-report list the default domain as the tenant identifier whereas other screens/reports such as /tenant/administration/tenants list the actual name of the tenant as well as the default domain.
Describe the solution you'd like
We would benefit from having both the tenant name and the default domain on reports that list multiple tenants. The name of the tenant is often configured to match other systems such as our PSA, so when we pull reports to CSV, having the actual tenant name is helpful to cross-reference other systems. The default domain alone is not always obvious to us who the client is.
@github-actions[bot] commented on GitHub (Jul 3, 2022):
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://cipp.app/GettingStarted/Contributions/ . Please notify the team if you are working on this yourself.
@KelvinTegelaar commented on GitHub (Jul 17, 2022):
Executed in dev