I've often grumbled that issue queue mgmt zaps the life out of module maintainers. part of this is a people problem, but a lot is project_issue module. It is slow to read and respond to many issues. i think the solution lies in matching the UI of Gmail. Gmail follows the same pattern of showing a listing page, and then a detail page. the reason why Gmail is so comfortable is because it uses Ajax to avoid screen refreshes in almost all cases, and uses single letter keyboard shortcuts to select topics in list view, and to navigate in to next/prev in detail view.

So, this feature request is to copy Gmail :)

Yes, this is a large task. But if done right could be reused on other list/detail apps like admin/content/node or even /forum. So, here's a call out to project and Jquery devs. Whats the roadmap for this?

Comments

hunmonk’s picture

hunmonk commented

the roadmap is: we're in new york, and this is in, uh, china... ;)

i would love to work on this now -- this is the candy that everybody wants, but alas, there are many things that we need to handle before this.

let's resume this discussion, at the very earliest, after we have a running, stable D6 version.

aclight’s picture

aclight commented
Status: Active » Postponed

This may become slightly more possible once #76725: Refactor project issue module to use Views is completed, if there happens to be a slick plugin to views that can handle some of this functionality. Otherwise, we'd probably need some new contributors to project*. I can't speak for dww and hunmonk, but I have exactly 1 brain cell that is familiar with javascript, and it just appeared yesterday.

But +1 on the idea of duplicating gmail. :)

moshe weitzman’s picture

moshe weitzman commented

Some relevant jquery at http://projects.arkanis-development.de/table_navigation/index.html.

Gaelan’s picture

Gaelan commented
Version: 5.x-2.x-dev » 7.x-2.x-dev

Bumping to Drupal 7. Also, #76725: Refactor project issue module to use Views is in now.

dww’s picture

dww
we/he/they
commented

This sounds like a great idea, but I'd hate to fix it in the project_issue code base. Especially in the D7 port, we're trying to get rid of as much custom code as possible and just use generic solutions whenever we can. This seems like something that should be fixed as a views add-on, not part of project_issue. Maybe related to #949372: Port issue views to Search API so we can have a performant backend as well? This is a *great* use-case for something like this, but IMHO it'd be a big step in the wrong direction to just write this as custom jquery directly in project_issue. However, in the absence of a more appropriate queue to move this to, I'm okay leaving it here and postponed for now. Perhaps this wants to be a discussion at http://groups.drupal.org/views-developers to see if something like this has already been written, and if not, who's interested and what's the right level at which to solve it.

Cheers,
-Derek