Derek, your opinion is informed and has lots of history.<br><br>Technically, is it just a tweak to add "blocked"? Just a config item?<br><br>Socially/workflow-wise, do you object to adding blocked, or think it would add to much to people's confusion?<br>
<br>-Randy<br><br><div class="gmail_quote">On Thu, Jun 3, 2010 at 6:09 PM, Alex Bronstein <span dir="ltr"><<a href="mailto:alex@craftyspace.com">alex@craftyspace.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I'd be ok with either one of these options:<br>
<br>
1) Don't add "blocked". Treat "postponed" as a superset of "blocked". So, something can either be "postponed" because another issue needs to be resolved first, or it can be postponed for other reasons, like the person who feels responsible for the issue wishes to convey that they're putting it off their radar for a while, until they feel like picking it up again some day. Although these are very different concepts, I don't think it's so bad to bundle them into a single status as we do now. But, if "postponed" includes "this issue is very much alive, but is stuck until another issue is resolved", then we must change the "79 critical issues (D7)" link in the "Contributor links" block to include "postponed". Otherwise, we have the wrong count and lose awareness of issues that still must be solved.<br>
<br>
2) Add "blocked" and include those, but not "postponed" issues in the count of critical issues remaining.<br>
<br>
My preference is for the second, but I think the first is acceptable. What I think is a problem right now is that we have some critical issues marked as "postponed" thinking that's the correct status for blocked, but those issues not showing up in that link that people are increasingly paying attention to.<br>
<font color="#888888">
<br>
Alex.<br>
</font><br>
PS: Not sure if this conversation should move to an issue. Perhaps it should if it starts getting more responses, but at least for now, I see some value in continuing it on this email list.<div><div></div><div class="h5">
<br>
<br>
Derek Wright wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
On Jun 3, 2010, at 3:09 PM, E.J. Zufelt wrote:<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I think a blocked issue status would be helpful,<br>
<br>
</blockquote>
<br>
Perhaps, although I'm concerned about the overwhelming number of choices we already have and ask users to navigate and understand. There have been multiple bikeshed-of-doom threads about the whole question of issue status names and meanings, for example:<br>
<br>
"Reorganise project issue statuses"<br>
<a href="http://drupal.org/node/171350" target="_blank">http://drupal.org/node/171350</a><br>
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
especially if the ability to build block relationships was available. This would allow for the display of all blocking and blocked by issues to be listed for each issue.<br>
<br>
</blockquote>
<br>
Right. This would be slick, but would require some new plumbing:<br>
<br>
"relationships between issues integrated with the status field"<br>
<a href="http://drupal.org/node/44162" target="_blank">http://drupal.org/node/44162</a><br>
<a href="http://groups.drupal.org/node/555" target="_blank">http://groups.drupal.org/node/555</a><br>
<br>
Other related topics:<br>
<br>
"Provide a mechanism for issue meta discussions"<br>
<a href="http://drupal.org/node/569552" target="_blank">http://drupal.org/node/569552</a><br>
<br>
"Enable CCK and node_reference"<br>
<a href="http://drupal.org/node/651484" target="_blank">http://drupal.org/node/651484</a><br>
<br>
<br>
Enjoy,<br>
-Derek (dww)<br>
<br>
<br>
<br>
<br>
</blockquote>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Randy Fay<br>Drupal Module and Site Development<br><a href="mailto:randy@randyfay.com">randy@randyfay.com</a><br>+1 970.462.7450<br><br>