* Wish List guidance and rules

[Gary_G]

Vyger;

When logged into one's account, is there a way for a user to review the Wishlist items on which they have already voted and how they prioritized that item?

There are times when that would help me make sure that I voted on an item and possible alert me to revise my priority if my circumstances changed.

[ColeValleyGirl]

Viewing the Wish List, look at the options for filter 'Where'.

[Gary_G]

Helen;

Thank you. I'm still learning my way 'round the board and missed that.

[Gary_G]

This is a very long thread for anyone to read and digest, when considering creating a wishlist suggestion. It really needs to be consolidate and put up as some form of single-entry invariant posting on creating a wishlist item.

[tatewise]

I agree with Gary. There needs to be a straightforward set of guidance notes in a thread that does not allow replies.

[ColeValleyGirl]

That was always the intention, once the ideas had been thoroughly discussed. We got a bit of input on process, a digression about notifications, and not a lot of comment on the actual contents of a well-formed Wish List request.

On that basis, can we assume the process and contents are agreed?

[Gary_G]

Helen;
I'd suggest that part of the invariant post be a skeleton structure, like Adrian's, containing brief notes within the structure sections relating to their intended purpose and content.

[As an aside: If you or others are familiar with military industry documents or want to look at what some industries have done; these are often called Data Item Descriptions and used to define the look and feel of a contract deliverable document. That's not to say we should ever need to be so prescriptive, but they usually result in a 1-2 page final document and may offer some good ideas. The one you'd be looking for is the MIL-STD 498 - "Software Design Description", which keeps things at a high enough level to avoid unnecessary design constraints.]