We need to make it more obvious how to update issue summary, now that it's not possible to do via comment form as before.

Remaining tasks

Add 'Update this issue' link next to the comment form.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Bojhan’s picture

No, this is actually by design - click the huge Update this issue.

jthorson’s picture

Title: No way to change issue status and other options » Move 'update this issue' functionality to main comment form
Category: bug » feature
Status: Active » Needs review
Issue tags: +drupal.org D7

Positioning as a feature request, and tagging for discussion.

andypost’s picture

At least comment body needs more rows by default

jthorson’s picture

Title: Move 'update this issue' functionality to main comment form » Add 'update this issue' functionality to main comment form
tvn’s picture

Closed #2098091: There *must* be a way to easily update an issue from the comment form. as duplicate of this one.
Our options include:
1. Make 'issue details' block sticky
2. Repeat 'issue details' block at the bottom (which will look ugly when both blocks are visible on the screen e.g. when there are no comments)
3. Add 'Update this issue' link next to the comment form.

tvn’s picture

Project: [Archive] Drupal.org D7 upgrade QA » Drupal.org customizations
Issue summary: View changes

upd

jthorson’s picture

Project: Drupal.org customizations » [Archive] Drupal.org D7 upgrade QA

I think the motivation behind this issue was to put the 'full' edit issue form (complete with metadata and file upload) on the issue page itself instead of behind another mouse click ... not simply moving/duplicating the 'update this issue' button.

tvn’s picture

In that case it should've been closed as (works as designed) after the first comment. We still need to make it more obvious how to update issues now, so let's continue here instead of closing this issue and re-opening the other one.

tvn’s picture

Project: [Archive] Drupal.org D7 upgrade QA » Drupal.org customizations
Issue summary: View changes

img

tvn’s picture

Title: Add 'update this issue' functionality to main comment form » Add 'Update this issue' link next to main comment form
Project: Drupal.org customizations » Project issue tracking
Version: » 7.x-2.x-dev
Category: feature » task
Status: Needs review » Active
Issue tags: +project

During D7 team call today we settled on adding "Update this issue" link next to the comment form. Changing title accordingly.

tvn’s picture

Project: Project issue tracking » Drupal.org customizations
Issue summary: View changes

.

tvn’s picture

Project: Drupal.org customizations » Project issue tracking
FileSize
114.41 KB

Mockup:

Or we could even have 2 different links - Update this issue and Upload new file.
It might be not too obvious that one needs to update an issue in order to upload a file. On the other hand less links, less choices to make.

jthorson’s picture

Assigned: Unassigned » jthorson
jthorson’s picture

Okay ... this took a couple steps, since the 'Add this comment' is hard-coded directly within the comment-wrapper template.

The Bluecheese patch modifies this to output $variables['comment_form_title'] in the template, and defines this as the default 'Add new comment' text within bluecheese_preprocess_comment_wrapper().

The drupalorg patch then sets it's own $variables['comment_form_title'] value, adding the 'Update this issue' link within it's own preprocess_comment_wrapper() call.

jthorson’s picture

Project: Project issue tracking » Drupal.org customizations
Version: 7.x-2.x-dev » 7.x-3.x-dev
Assigned: jthorson » Unassigned
jthorson’s picture

FileSize
18.92 KB

Screenshot from dev site, with patches applied.

helmo’s picture

+1, looks better

drumm’s picture

Title: Add 'Update this issue' link next to main comment form » Remove 'Update this issue' link next to main comment form when issue updaters are used to the new green button
Priority: Normal » Minor
Status: Needs review » Postponed

I'm not too fond of making any PHP additions in bluecheese, but this is temporary. Committed & deploying.

drumm’s picture

Issue tags: -project, -drupal.org D7

Forgot to untag. We're not really in a hurry, so this isn't even Drupal.org 7.1.

In the meantime, we can think about:

  • Add a custom Google Analytics event to see what people actually use.
  • Change management pointing out new things. For example, I've seen sites like Podio show messages pointing to new things. Podio itself is quite annoying for new use because everything has these for new users, you end up spending minutes just dismissing things.
jthorson’s picture

Yeah ... the bluecheese template was a bit of a head-scratcher. But even more so is the fact that this can't be over-ridden any other way in core ... the text for this title is hard-wired into the .tpl file, whereas we make just about everything else alter-able via hooks.

jthorson’s picture

Issue summary: View changes

upd

mgifford’s picture

I think this issue needs to be updated.

Can we close this issue and create follow-up issues for the Google Analytics? Would be great to have stats on what folks are actually doing.

I like the idea about pointing to new UI changes in drupal.org. But again that should be a new issue.

drumm’s picture

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

  • Commit 29cd0f9 on 7.x-3.x, 7.x-3.x-dev authored by jthorson, committed by drumm:
    [#2097927] Add 'Update this issue' link next to main comment form