[GH-ISSUE #3779] [Feature Request]: Add "Requested" to the quarantine Preset Filter

kerem commented

2026-03-02 13:46:11 +03:00

Owner

Originally created by @TMGCL-TS on GitHub (Mar 10, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3779

Please confirm:

I have searched existing feature requests (open and closed) and found no duplicates.
**me or my organization is currently an active sponsor of the product at the $99,- level.

Problem Statement

When a user requests an email to be released from Quarantine, we currently have to put a filter on the column Release Status, rather than being able to apply a quick filter

Benefits for MSPs

Speed up time when doing quarantine release requests, as well as preventing issues with spelling when putting the manual filter in

Value or Importance

Nice to have, and was requested and 'closed' in a previous ticket
https://github.com/KelvinTegelaar/CIPP/issues/1066
however unsure if was applied to preset filters, or just the ability to filter,

PowerShell Commands (Optional)

No response

Originally created by @TMGCL-TS on GitHub (Mar 10, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3779 ### Please confirm: - [x] **I have searched existing feature requests** (open and closed) and found no duplicates. - [x] **me or my organization is currently an active sponsor of the product at the $99,- level. ### Problem Statement When a user requests an email to be released from Quarantine, we currently have to put a filter on the column Release Status, rather than being able to apply a quick filter ### Benefits for MSPs Speed up time when doing quarantine release requests, as well as preventing issues with spelling when putting the manual filter in ### Value or Importance Nice to have, and was requested and 'closed' in a previous ticket https://github.com/KelvinTegelaar/CIPP/issues/1066 however unsure if was applied to preset filters, or just the ability to filter, ### PowerShell Commands (Optional) _No response_

kerem

2026-03-02 13:46:11 +03:00

closed this issue
added the
enhancement

no-priority

no-activity
labels

kerem commented

2026-03-02 13:46:12 +03:00

Author

Owner

@TMGCL-TS commented on GitHub (Mar 10, 2025):

Happy to try implement myself as a learning experience, however I think it is a quick fix so not sure if its easier to implement on your end, or if ok to try my end

@TMGCL-TS commented on GitHub (Mar 10, 2025): Happy to try implement myself as a learning experience, however I think it is a quick fix so not sure if its easier to implement on your end, or if ok to try my end

kerem commented

2026-03-02 13:46:12 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 10, 2025):

Hello,

Thank you for your interest in improving CIPP!
To keep our development process focused and manageable, feature requests are limited to paying users. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support.

When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP.

While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "I’d like to work on this!" to assign the issue to yourself.

Did you get this notification in error? Reply with a screenshot of your sponsorship payment and we’ll reopen the issue.

Thank you for understanding,
The CIPP Team

@github-actions[bot] commented on GitHub (Mar 10, 2025): Hello, Thank you for your interest in improving CIPP! To keep our development process focused and manageable, **feature requests are limited to paying users**. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support. When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP. While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "**I’d like to work on this!**" to assign the issue to yourself. **Did you get this notification in error?** Reply with a screenshot of your sponsorship payment and we’ll reopen the issue. _Thank you for understanding,_ **The CIPP Team**

kerem commented

2026-03-02 13:46:12 +03:00

Author

Owner

@TMGCL-TS commented on GitHub (Mar 10, 2025):

Hello,

Thank you for your interest in improving CIPP! To keep our development process focused and manageable, feature requests are limited to paying users. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support.

When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP.

While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "I’d like to work on this!" to assign the issue to yourself.

Did you get this notification in error? Reply with a screenshot of your sponsorship payment and we’ll reopen the issue.

Thank you for understanding, The CIPP Team

Unfortunately, it is my organization that is sponsoring, so my login doesn't have anything directly tied to the sponsorship.
What information can I request from the higher ups to verify sponsorship on your end?

@TMGCL-TS commented on GitHub (Mar 10, 2025): > Hello, > > Thank you for your interest in improving CIPP! To keep our development process focused and manageable, **feature requests are limited to paying users**. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support. > > When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP. > > While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "**I’d like to work on this!**" to assign the issue to yourself. > > **Did you get this notification in error?** Reply with a screenshot of your sponsorship payment and we’ll reopen the issue. > > _Thank you for understanding,_ **The CIPP Team** Unfortunately, it is my organization that is sponsoring, so my login doesn't have anything directly tied to the sponsorship. What information can I request from the higher ups to verify sponsorship on your end?

kerem commented

2026-03-02 13:46:12 +03:00

Author

Owner

@kris6673 commented on GitHub (Mar 11, 2025):

Happy to try implement myself as a learning experience, however I think it is a quick fix so not sure if its easier to implement on your end, or if ok to try my end

You're welcome to try yourself always nice to get more contributors, or if you want I can add the preset filter for you? :)
You can see how they work here: github.com/kris6673/CIPP@961b8818f9/src/pages/identity/reports/mfa-report/index.js (L19-L47)

@kris6673 commented on GitHub (Mar 11, 2025): > Happy to try implement myself as a learning experience, however I think it is a quick fix so not sure if its easier to implement on your end, or if ok to try my end You're welcome to try yourself always nice to get more contributors, or if you want I can add the preset filter for you? :) You can see how they work here: https://github.com/kris6673/CIPP/blob/961b8818f9f8ed38846c1735b1de7380e66a90d8/src/pages/identity/reports/mfa-report/index.js#L19-L47

kerem commented

2026-03-02 13:46:12 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 21, 2025):

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.

@github-actions[bot] commented on GitHub (Mar 21, 2025): 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.

kerem commented

2026-03-02 13:46:12 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Mar 21, 2025):

Great job on your first pr! added in dev.

@KelvinTegelaar commented on GitHub (Mar 21, 2025): Great job on your first pr! added in dev.

Rows
Columns

[GH-ISSUE #3779] [Feature Request]: Add "Requested" to the quarantine Preset Filter #1680

Please confirm:

Problem Statement

Benefits for MSPs

Value or Importance

PowerShell Commands (Optional)