Launchpad itself

What is the point of blueprint feedback and how does it work?

Asked by Xavier (Open ERP)

I tried understanding the point of using "request feedback" on a blueprint, but it seems completely broken, or useless:

* It doesn't request feedback, it doesn't send any mail or anything (and doesn't display anything on a user's dashboard either, making it pointless and unnoticeable)
* It doesn't seem to be a feature for the spec's drafters/implementers as the people they "request feedback" from don't get any notification. Unless drafters start by *subscribing* them to the blueprint, they won't ever know they've been "requested feedback"
* Feedback can't actually be provided, the only thing the "provide feedback" link allows (as far as I can say) is to remove feedback "requests".

After this, my take on this terribly named feature:
* it's not about requesting feedback, it's about providing feedback to the blueprint authors/implementers. It should therefore be named "provide feedback" or -- even better "comment" with an UI in line with e.g. bug comments. The current UI is misleading at best
* likewise, the "provide feedback" (or whatever it was) link is misleading in its current form, as it doesn't let anyone provide anything. It should be renamed to "mark comment/feedback as " and some status, and it should at most gray out the comment/feedback, not delete it completely.

Now if I misunderstood that thing (and I hope I did), please enlighten me, because while my take looks pretty clear to me, it makes the current wording and UI of the feature utterly insane.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Xavier (Open ERP)
Solved:
Last query:
Last reply:
Revision history for this message
Curtis Hovey (sinzui) said : 		#1

The notifications for blueprint feedback are seriously broken. Feedback is used only publicly record who was asked to give feedback through some other means of communication.

There are no engineers working on the blueoprint application. Community users do contributes fixes and new features, but non have commited to fixing these bugs.

Revision history for this message
Xavier (Open ERP) (xmo-deactivatedaccount) said : 		#2

Wow, damn. Thanks a lot for the answer curtis. That's kinda sad.

Revision history for this message
naesk (naesk) said : 		#3

I have to agree the "Give Feedback" link is very misleading.

Having recently received a feedback request for a project, I was expecting to be able to literally do as the link suggests and actually give feedback directly to the blueprint. Instead all I see on a new page is;

"Select the requests which you wish to remove from your queue
Select the items that you have addressed in this blueprint, and click "Save changes" to clear those feedback requests from your queue."

This is totally counterintuitive to usability.