Please add me to the list of people that feel this is a very important feature. The functionality, as documented here, would work perfectly.
Chief_Apricot:Hi Jessie - sorry, we are not likely to tackle this feature in 2011.
That's disappointing, especially since it was stated almost two years ago that it would be implemented mid 2010, at the latest.
Is the prioritization process documented anywhere? I understand that you can use these threads to get a sense of how important each feature request is, but how do you gauge how we would prioritize each of these features against each other? There are features that have been delivered over the last year that, personally, I would not have prioritized higher than this one.
Have you considered using some kind of stack-ranking system that your customers could use to communicate relative priority of feature requests? I recognize that the features may vary greatly in effort to implement, and that you have other constraints such as development resource expertise, which also influence priority. However, such a system could help define the workstream, provide visibility into the process, and alleviate some of the frustration that I'm sure customers on this thread are feeling.