Remove 'Update this issue' link next to main comment form when issue updaters are used to the new green button

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

Positioning as a feature request, and tagging for discussion.

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.

upd

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.

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.

img

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

.

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.

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.

Screenshot from dev site, with patches applied.

+1, looks better

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

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.

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.

upd

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.

This was rolled into #2159813: Display parts of the issue edit form instead of the comment form on issue pages.