Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I like having the new "issue summary" text to see who last edited an issue on drupal.org, however the way it's currently positioned is misleading.
Currently, it looks like it's actually the header for the initial issue text itself, making it look like the person who last updated it actually authored the issue in the first place (because it's between the original author's information and the text of the issue). I'd recommend moving this Issue Summary text elsewhere on the page so it's less confusing, possibly over by the "Jump To" information.
A screenshot is attached to show how the Issue Summary and the issue text appear to be related
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | Even more confusing... | 68.06 KB | Rob_Feature |
| Issue Summary is Confusing | 24.78 KB | Rob_Feature |
Comments
Comment #1
corbacho CreditAttribution: corbacho commentedOnly wanted to add an example: Posted by Deciphered, edited by webchick #691078: Field tokens
Don't know what to think. How important is to make clear who is responsible of last revision?
Comment #2
Rob_Feature CreditAttribution: Rob_Feature commentedWow, then there's this "updated" text on the issue you just linked to that makes it even more confusing..I don't even know what that is. I agree that this seems like a lot of info that no-one really needs in a really prominent (and confusing) position (see screenshot for further confusion, in case the linked issue above changes)
Comment #3
MichelleNot sure if this would be considered a duplicate but at least related: #1217286: Posting a comment changes too many issue node revision properties
Michelle
Comment #4
lisarex CreditAttribution: lisarex commentedFor what it's worth, I think having the Posted by and Revision by names next to each other could work, so it's clear there were at least 2 folks involved in the making of this issue.
I don't know how possible that is though.
Issue Summaries can get very long and they are the most important info on the page, so I think they do need to stay where they are now.
(also, refiling... This should be in the the 'customizations' project as the Redesign project is Obsolete)
Comment #5
joachim CreditAttribution: joachim commentedSubscribe.
I filed this which I'd say is a duplicate: #1220650: new issue summary layout is unclear.
Comment #6
klonos+1 to #4.
Comment #7
sreynen CreditAttribution: sreynen commentedAs an added data point, here's an example of someone completely misunderstanding who created an issue, I think because of this issue:
http://drupal.org/node/1114596#comment-4792248
#1217286: Posting a comment changes too many issue node revision properties definitely exacerbates the problem by changing the name when there's no edit to the actual issue, but even when there is an edit to the issue, the distinction between the original author and the revision author could be clearer.
Comment #8
dkingofpa CreditAttribution: dkingofpa commentedAnother data point:
http://drupal.org/node/1047842
A user had posted a comment *and* edited the summary. I couldn't delete the summary so I had to just change it to a very short summary of the ticket.
I've been confused by this new summary feature more than once. I understand that it helps solve the problem of really long and complex issue threads, but it seems to just add confusion to the majority of issue threads on d.o. (the non-complex issues)
Comment #9
dwwI believe this is all addressing the same problem as #1221190: The Issue summary should augment the original post, not replace it. I've been trying to understand the fallout since summaries went live (I've been offline for about a month), and the whole discussion is very scattered, so I'm going to try to consolidate issues where appropriate...
Thanks,
-Derek