Make the "My issues" block (for the dashboard) more beautiful and functional

Okay, here's functional. Not beautiful yet. ;)

Before:

After:

You can play with it at your dashboard on:
http://solr.redesign.devdrupal.org/user/46549/dashboard

- Not sure we want the red "new" marker, that seems redundant with the "N new" comments link
- Not sure if text-align: right for the project name is good, or if we should keep it align left and bold or something. I wanted to visually separate from the issue title
- Not sure if the priority, category and status should be links, e.g. to the issue queue for that project, filtered by whatever you click

This version:
- Removes the "new" marker (which will dramatically simplify the query, too)
- Used bold instead of text-align: right for the project name.
- Puts the status first on the status line (as per original post), since it's the most important value in that row

Also, for comparison, it restores the status-based row coloring.

Fixing the tags

See also #936926: Update color scheme for status-based issue tables and issue link filter ;)

See also:
#947106: Provide dashboard configuration options for the 'My issues' block
#947108: Expose a block for the 'My projects' issue search for use on the dashboard

There's not currently a good way for you to test this, unfortunately. I'll probably just deploy it once I can review the queries with nnewton to make sure we're not going to introduce a regression relative to #921210: Fix performance of "My issues"

However, further usability reviews (of the screenshots in here) would be great...

@joshuajabbour: Yes, the block would get whatever colors and styles we come up with over at #936926: Update color scheme for status-based issue tables and issue link filter. The screenshot in #3 pre-dates any of the changes from #936926.

@all: Yes, I agree the filter should default to open issues, just like the page. That was just an oversight, and this is a good issue to fix it since we're changing the default view, anyway.

Re: making the dashboard titles link to their pages: that's a more tricky problem. Currently, those titles are how you drag the dashboard widgets around your dashboard. If folks are interested in pursuing this, please open a new issue at
http://drupal.org/node/add/project-issue/redesign?component=Dashboard&ta...

Fixed the view to add the default filter for open issues. This patch is now deployed on http://beta.drupal.org if folks want to play with it there. Here's a screenshot of how it looks on beta for me:

For nnewton's benefit, here's the resulting query:

SELECT
node.nid AS nid,
node_project_issues.title AS node_project_issues_title,
node_project_issues.nid AS node_project_issues_nid,
node_project_issues__project_projects.uri AS node_project_issues__project_projects_uri,
node.title AS node_title,
project_issues.priority AS project_issues_priority,
project_issues.category AS project_issues_category,
project_issues.sid AS project_issues_sid,
node.type AS node_type,
node_comment_statistics.comment_count AS node_comment_statistics_comment_count,
tracker2_user.changed AS tracker2_user_changed
FROM node node
INNER JOIN project_issues project_issues ON node.nid = project_issues.nid
INNER JOIN node node_project_issues ON project_issues.pid = node_project_issues.nid
INNER JOIN tracker2_user tracker2_user ON node.nid = tracker2_user.nid
INNER JOIN project_projects node_project_issues__project_projects ON node_project_issues.nid = node_project_issues__project_projects.nid
INNER JOIN node_comment_statistics node_comment_statistics ON node.nid = node_comment_statistics.nid
WHERE (tracker2_user.published = 1) AND (project_issues.sid in ('1', '13', '8', '14', '15', '2', '4', '16')) AND (tracker2_user.uid = 46549)
ORDER BY tracker2_user_changed DESC

Which results in this EXPLAIN:

+----+-------------+---------------------------------------+--------+---------------------------------------------------------------------------+---------+---------+--------------------------------------------------+------+--------------------------+
| id | select_type | table                                 | type   | possible_keys                                                             | key     | key_len | ref                                              | rows | Extra                    |
+----+-------------+---------------------------------------+--------+---------------------------------------------------------------------------+---------+---------+--------------------------------------------------+------+--------------------------+
|  1 | SIMPLE      | tracker2_user                         | ref    | PRIMARY,tracker                                                           | tracker | 5       | const,const                                      | 9278 | Using where; Using index | 
|  1 | SIMPLE      | project_issues                        | eq_ref | PRIMARY,project_issues_pid,project_issues_sid,project_issues_nid_assigned | PRIMARY | 4       | drupal.tracker2_user.nid                         |    1 | Using where              | 
|  1 | SIMPLE      | node_project_issues__project_projects | eq_ref | PRIMARY                                                                   | PRIMARY | 4       | drupal.project_issues.pid                        |    1 |                          | 
|  1 | SIMPLE      | node                                  | eq_ref | PRIMARY,nid                                                               | PRIMARY | 4       | drupal.tracker2_user.nid                         |    1 |                          | 
|  1 | SIMPLE      | node_project_issues                   | eq_ref | PRIMARY,nid                                                               | PRIMARY | 4       | drupal.node_project_issues__project_projects.nid |    1 | Using where              | 
|  1 | SIMPLE      | node_comment_statistics               | eq_ref | PRIMARY                                                                   | PRIMARY | 4       | drupal.tracker2_user.nid                         |    1 |                          | 
+----+-------------+---------------------------------------+--------+---------------------------------------------------------------------------+---------+---------+--------------------------------------------------+------+--------------------------+

That EXPLAIN looks pretty good to me...

So, any final objections here?

Thanks,
-Derek

@catch re: "Also am I missing something or is that query missing a limit?" -- that's just how views was feeding me the query when I previewed it on the beta site. Looks like a bug in views that it leaves off the limit stuff when displaying the query. ;) But yeah, there's really a LIMIT on there -- it's only rendering 10 rows.

It's obviously easy to leave off the category. I just thought if we're doing a meta-data row, it doesn't hurt to include it, and I certainly can see times where it's useful to know. but yeah, status and prio are more relevant, so we could leave it off i guess. in many ways, just seems like a matter of personal taste, and therefore, something to solve at #947106: Provide dashboard configuration options for the 'My issues' block...

For comparison, here's the query from the current block on d.o:

SELECT
node.nid AS nid,
node_project_issues.title AS node_project_issues_title,
node_project_issues.nid AS node_project_issues_nid, node_project_issues__project_projects.uri AS node_project_issues__project_projects_uri,
node.title AS node_title,
project_issues.sid AS project_issues_sid,
tracker2_user.changed AS tracker2_user_changed
FROM node node
INNER JOIN project_issues project_issues ON node.nid = project_issues.nid
INNER JOIN node node_project_issues ON project_issues.pid = node_project_issues.nid
INNER JOIN tracker2_user tracker2_user ON node.nid = tracker2_user.nid
INNER JOIN project_projects node_project_issues__project_projects ON node_project_issues.nid = node_project_issues__project_projects.nid
WHERE (tracker2_user.published = 1) AND (tracker2_user.uid = 46549)
ORDER BY tracker2_user_changed DESC

And the EXPLAIN:

+----+-------------+---------------------------------------+--------+--------------------------------------------------------+---------+---------+--------------------------------------------------+------+--------------------------+
| id | select_type | table                                 | type   | possible_keys                                          | key     | key_len | ref                                              | rows | Extra                    |
+----+-------------+---------------------------------------+--------+--------------------------------------------------------+---------+---------+--------------------------------------------------+------+--------------------------+
|  1 | SIMPLE      | tracker2_user                         | ref    | PRIMARY,tracker                                        | tracker | 5       | const,const                                      | 9306 | Using where; Using index | 
|  1 | SIMPLE      | project_issues                        | eq_ref | PRIMARY,project_issues_pid,project_issues_nid_assigned | PRIMARY | 4       | drupal.tracker2_user.nid                         |    1 |                          | 
|  1 | SIMPLE      | node_project_issues__project_projects | eq_ref | PRIMARY                                                | PRIMARY | 4       | drupal.project_issues.pid                        |    1 |                          | 
|  1 | SIMPLE      | node                                  | eq_ref | PRIMARY,nid                                            | PRIMARY | 4       | drupal.project_issues.nid                        |    1 | Using where              | 
|  1 | SIMPLE      | node_project_issues                   | eq_ref | PRIMARY,nid                                            | PRIMARY | 4       | drupal.node_project_issues__project_projects.nid |    1 | Using where              | 
+----+-------------+---------------------------------------+--------+--------------------------------------------------------+---------+---------+--------------------------------------------------+------+--------------------------+

Committed #17 to project_issue HEAD and the bluecheese patch in #3 to bzr. Also committed the attached patch to bluecheese with the basic idea drumm was saying in #6, but modified to actually work. ;) Everything is now deployed to the live site and the CSS cache is cleared. It's possible users will have to clear their browser caches for the full effect. Here's how it looks for me:

Next stop: #947106: Provide dashboard configuration options for the 'My issues' block ...

Adding the drupal.org redesign dashboard tag so we can easily track all the issues related to d.o dashboard widgets, regardless of what project they're in.

@joshuajabbour Re: #27: yes, good point. I committed a fix for that which will be rolled out to production sometime today. Thanks.

I got nnewton to approve the query that'd be introduced by the scope_creep in #29. So, now we just have to decide which of these we like better:

A) Put the update marker next to the issue title.
Pro: Consistent with the "Your posts" block
Con: Tends to introduce line wrapping since we have so little horizontal space to work with

B) Put the update marker next to the comment counts:
Pro: We always have space for it here, so we'll never introduce line wrapping b/c of this
Con: Less consistent with "Your posts" block (although these two widgets are pretty much wildly different already, so I don't see the harm)

C) Just style the "N new" links red like the updated marked
Pros: Updated vs. new is actually a bogus distinction. Anything in this list was either created by you or something you commented on. In neither case can the issue actually be "new". So really, the point of this marker is to draw attention to updated comments. So why not just do that directly? Also, keeps the query even simpler. ;)
Cons: Even less consistent with the "Your posts" block.

D) Just style the "N new" links bold.
Pros: Mostly same as (C)
Cons: Even less consistent with the "Your posts" block, and doesn't draw enough attention to my eyes.

Thoughts?

Thanks,
-Derek

@xjm: I thought of that, and tried to get that working, but it's actually a pain to accomplish that in Views, just given how all this stuff is being generated and given the tools views provides (field re-writing, tokens, fields that link automatically, etc).

I think C is best, but I can understand that people wouldn't necessarily know those are links you can click. So, I'm willing to do B, instead.

- Added joshuajabbour's CSS from #34 to bluecheese bzr (thanks, good catch!)
- Committed my patch #30.B to project_issue
- Merged both into production bzr
- Deployed live
- Cleared the views, css, and page caches