What criteria is used when applying the status-planned tag? I've seen that status-planned is one of the restricted tags that can only be added or removed by a moderator (or employee). But, I can't find the specifics of how/when they decide to apply this tag for a particular bug or feature request.
Is there any particular rule or reason before this tag is applied/added?
The status-planned info. details page reads:
Wheels are in motion, the sand falls through the hour glass and we're looking down the barrel of something coming along sweet.
We're in a world now of a promised feature, tweak or enhancement to fruit.
A change in functionality has been considered and received positively, and work on it is either in progress, or will begin soon.
The answer on How does Meta Stack Exchange work? says:
Indicates that a feature request has been considered and received positively enough that its implementation has been placed in the development queue.
Both of the above points gives you only a generic/standard information.
There are few good feature requests and bugs reported on meta but they don't seem to get noticed enough even after having a fair amount of upvotes (assuming votes are considered as one of the factor).
I've also noticed that in a few cases the status-planned tag gets immediately applied (on the same day of posting) for some newly posted bugs/feature requests even though they have received very little votes. The only thing I can think of here is *how critical the bug/feature request is.
I guess "criticalness" also plays an important role in determining whether or not the tag should be applied. But, I believe there are few more factors out there.
It would be great if someone from the official side of the Stack Exchange team provided more details on the factors determining when the status-planned tag is used.