Posted by Anonymous on April 25, 2011 at 9:33am
Last updated by tvn on Mon, 2012-02-06 15:20
Last updated by tvn on Mon, 2012-02-06 15:20
Current Status - on hold
Re-designing an issue page so that it is easier to contribute and our discussions/collaborations are more effective.
Few positive things happened recently to issue pages, such as Issue following and Issue summaries, but we can do even better!
History :
- Exploring solutions - http://groups.drupal.org/node/136174
- Issue Queue User Journeys (Survey) - http://groups.drupal.org/node/139009
- Managing duplication in issue queue - http://groups.drupal.org/node/136179
- The first lot of wireframes - http://groups.drupal.org/node/137829
Related existing issues
- Redesign the Issue Queue (includes many issue links) - http://drupal.org/node/1080550
- Real issue subscriptions - http://drupal.org/node/1080494
- Project Issue Related - http://drupal.org/project/pi_related
- Back-link to the commit at the issue node - http://drupal.org/node/493074
Current thinking:
Here's the wireframe we're currently discussing as revision to the issue page template.
A description and discussion of each element on the page can be found here
| Attachment | Size |
|---|---|
| Version2.png | 126.78 KB |
| getsatisfaction.com_.png | 81.18 KB |
Comments
Not sure if this fits
The Git team is working on functionality to be deployed in the next month but which require the introduction of new interface elements. See http://drupal.org/node/1074960 and http://groups.drupal.org/node/141699
The addition will touch the Issue page so I want to get it connected somehow, but I'm not sure if these elements, which are visible to contributors only, belong here.
Project-specific gates
It would be great if the gates could be adjustable for each individual project, with a default list like we have with components now. I'm specifically thinking of a project like Drupal.org Project Applications, which would need a completely different gate list than most other projects, but I can also imagine it being useful for more normal projects to have custom gates. A project like WYSIWYG, for example, may find it useful to have a separate gate for checking changes against each supported WYSIWYG editor.
Yeah, I imagine there would be
Yeah, I imagine there would be check boxes on the admin side of this page to select which gates apply. Not sure we should want to promote the invention of new gates. Your example sounds more like a project-specific criterium for a generic 'performance' or 'functionality' gate?
Project application queue
I'm not sure which example you're referencing. I probably shouldn't use WYSIWYG as an example, as I'm not actively involved in that queue. My primary concern here is the project application queue, where there's continued discussion of functionality almost identical to what's being discussed here, most recently:
http://groups.drupal.org/node/152304
The big difference there is the gates. The default gates suggested here wouldn't really be usable in that queue. I think "promote the invention of new gates" is the wrong way to look at this. We're not really promoting new components now, though we do allow it. That functionality is only used in practice where it's actually useful. There's no incentive to change the defaults where they work, but the ability to change them where they don't work keeps the system usable for a variety of non-standard projects. I hope we can do the same for gates.
Related Issue
Someone from this group might want to comment here http://drupal.org/node/1224438#comment-4778388
Interesting discussion
Interesting discussion happening here about the endorsement of drupal.stackexchange.com as our official support channel. What I thought is that it could be used to test in the real world if some of the ideas wrt to this issue are valid, since SE is well developed Q&A engine.
Take a look at how they do it in getsatisfaction.com
...here is a screenshot and a link for those that like the real thing: http://getsatisfaction.com/mozilla_messaging/topics/addon_testpilot_for_...
PS: ...sorry for adding the screenie to the topic summary, but I see no other way to do it - don't mean to hijack or anything.
No excellent, that's what the
No excellent, that's what the wiki is for and that's indeed the only way to do it :)
Thanks! Issue pages are very much on the radar again: http://3281d.com/2011/10/26/report-from-project-7-sprint. There's links to UI research in there too:
http://www.flickr.com/photos/82268668@N00/sets/72157627969963444/with/62...
https://docs.google.com/document/d/1gGipnivb_uIa7Qez6ypU4hwpL9_9dxP_0KQw...
Go check it out, let us know what you think!
That's where I'm coming from Roy...
...I've already checked those mockups on flickr. That's why I thought I'd post a screenshot of one of my favorite ticket handling systems here. You see, I don't have a flickr account and I don't hung out at g.d.o that much. I prefer "lurking" in the issue queues where I try to help (I find the notifications of the "Your issues" page more convenient to keep track of + I am now addicted to the new "follow"/"unfollow" button thing).