Request Rejection

jpenberthy asked for this feature about 4 years ago — 7 comments

jpenberthy commented about 4 years ago

I approve all requests, because I don't mind making it available. Though I would like someway to reject it, weather it is just for space or maybe I cannot get it. So you should be able to mark the item rejected for cause and list a reason, then it sends an email to them (and even a slack message, etc).

tidusjar commented about 4 years ago Admin

So we already have an option to "Deny" a request, so I guess you want some way to inform the user?

We can send them emails as long as there is an email on their account (being Plex or Local user), but doing some sort of Slack message per user is a bit too much (unless you mean a slack notification to a channel?)

| ksbansal commented about 4 years ago

I think what jpenberthy is trying to say is that he has his requests set to all auto approve, but once approved their is no way of rejecting that approved request afterwards. The only options after approval are remove and mark as available.

I have had the same issue. The requests are all set to auto approve but sometimes I would like to reject the approved request with a reason sent to the requester.

| leram84 commented about 4 years ago

I believe the term we're looking for here is "blacklist". This would be useful as well so that if another user went to add that item it would not let them and would say "blacklisted".... plus the notification to the op would be good too.

| ksbansal commented about 4 years ago

leram84 nicely put :)

| estavez commented almost 3 years ago

Baclklist is nice xtra thing also but not what jpenberty is talking about here.

Because you can already accept & deny requested contents when is is requested at first but the main thing here is that at lot of times the contents is not available and just lays here this it where the feature Request denied with a reason is useful, as it it today you can only deny a request with a reason at first, this is to do the same after it has been approved because the uses can see why it has been removed and then they could request it again. Shouldn't be to hard of a deal as the feature is already there, it just needs to be activated elsewhere in the code. +for notifications directly to the Plex user account they are logged in with on ombi.

| bromanguydude commented over 2 years ago

Yea a "Request not found" or "Request Unavailable" would be good.

Join the discussion!

with GitHub to comment