P: Assign People tags to pictures that were missed

This has been a known issue since at least Oct, 2018.  Referring to my previous post, what is the criteria for an issue getting visibility in front of decision makers?  This functionality was declined and now does not have a status. What was the discussion around going from Declined to No Status. Is the issue being analyzed?  How is Adobe planning to address this issue?

But as you can see, I mentioned a problem in my post "photos that contain clear faces remain unrecognized". And there a lot of photos that are left out.

Aren't you going to solve or at least commnet on this?

@georgiosa42941452 Sorry, I think that was me, and my extra bit of blurb explaining why didn't get included. This is the feature request thread for the feature that you are requesting - the ability to manually add people tags to faces that were missed. You can add your vote using the button in the top right corner. The number of votes on a feature request does influence future additions, so every vote counts. 

What is this? You merged my post in a general thread about face recognition and problem solved?

Nice customer support. You know that we pay for this product, right?

The problem is very simple: photos that contain clear faces remain unrecognized.

Moreover, there is no way to inform lightroom that a specific photo contains a face.

Unfortunately, the face recognition feature is unreliable.

If/When an answer changes, the thread will be updated and the status changed. 

The threads are merged to give a single source for Product Management to evaluate feature requests.

@dank87557784 

No issue.

@Rikk Flohr: Photography 

Any chance at an answer. And since you (or another Adobe employee) merged all these threads together, has the answer changed?

Tim

Apologies Tim, I should be specific...I'm asking this of Adobe, and specifically, Rikk Flohr, or another Adobe employee that is being notified of these updates.  I've Upvoted this issue and others, but don't know that it really makes a difference.  The person that started this three years ago KNOWS it doesn't make a difference.

Since I do not work for Adobe, I cannot answer any of those questions.

However, I have seen Adobe respond to customer pressure and interest. So, Adobe employees have stated multiple times the way to get visibility of an issue is to upvote it.

So, that is all we can do, unless you have connections others of us do not.

Tim

I'm not sure you're answering my question.  Why would this be marked as "Declined" if there wasn't internal discussion where the functionality was considered and rejected?  I'm asking specifically why the status was changed to "Declined"?  Given that this functionality is available in other similar Adobe products, this entry has been open for at least three years, and most people taking the time to post stated they would not use the application until the issue was addressed, I'm curious specifically what the issue was with incorporating this functionality into the product.

Also, for future reference, is there internal review criteria that we customers should be aware of?  As a user of the Adobe Support Community area, I would like to understand the Upvote thresholds for my entries to get any sort of visibility.  Is this entry close....like 110 votes gets another re-assessment...or is the criteria 1000, or 10,000, or 100,000 upvotes before this would be re-assessed?