When users submit Marketplace app install requests via Connected Apps (admin.atlassian.com > Site > Connected Apps > Requested apps tab), the only action available to admins is Reject. Rejecting has three mandatory side effects:

1. Blocks all future requests for that app

1. Sends a notification to the requester that their request was rejected

1. Makes the rejection comment visible to all logged-in users in the instance

There is no way to silently clear, dismiss, archive, or close an outdated request without triggering all three of these side effects. There is also no bulk action available.

Use Case

Customers accumulate a backlog of outdated Marketplace app requests over time. In many cases, the requests were resolved by installing an alternative app, making a formal rejection unnecessary. Admins need a way to clean up this backlog without:

• Sending confusing or unwanted rejection notifications to users about requests they submitted months or years ago

• Posting comments that are visible instance-wide

• Permanently blocking future requests for those apps (which may be needed later)

This is particularly important for enterprise customers managing large instances with many users.

Expected Behavior

• A "Dismiss" or "Close" action on Marketplace app requests that:

• • Removes the request from the active/open list

• • Does not notify the requester

• • Does not post any comment visible to other users

• • Does not block future requests for the same app

• A bulk action to dismiss/close multiple outdated requests at once

Current Workaround

None. Requests remain in an open state indefinitely. The only alternative is to reject them, which triggers all three undesirable side effects.

Affected Area

Atlassian Administration > Sites > Connected Apps > Requested apps tab
(admin.atlassian.com/s/{site-id}/user-connected-apps/tab/requested)