The "Folow" button moved under the issue title - I think it is not a good place. I won't kow if I want to follow the issue untill I read it. So "Follow" should move to the meta block below the "Upadte…" button – it would have the benefit too that we keep action links together making a simpler user experience.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

yonailo’s picture

+1

eliza411’s picture

Status: Active » Needs review

I agree that it's much harder to find the follow button in its new location, especially since it's gray, but I haven't been following the design choices.

I'm setting this to "needs review" so it can be addressed and maybe linked to relevant discussion issues.

thamas’s picture

Screenshot with the recomended move.

issue-follow-button-1991726.png

dww’s picture

Assigned: Unassigned » tvn

I think tvn should comment, since she's been driving most of the final UI choices like this.

Thanks,
-Derek

webchick’s picture

Two big green buttons next to each other would be too easy to click the wrong one accidentally.

Counter-suggestion:

Follow button right after the block title.

webchick’s picture

Also, #2097925: Rename "Edit" to "Update" for consistency with the "Update this issue" button (at the bottom) is an example of a tester not seeing it where it's currently located. And FWIW, of the ~10 people who were reviewing the D7 site found jarring, too.

webchick’s picture

Priority: Normal » Major

Tentatively moving to major as a result. Not a release blocker, certainly, but also more important than "Unclear label 'Description'"

tvn’s picture

Project: [Archive] Drupal.org D7 upgrade QA » Project issue tracking
Version: » 7.x-2.x-dev
Assigned: tvn » Unassigned
Priority: Major » Normal
Status: Needs review » Active
Issue tags: +project, +drupal.org D7
FileSize
16.65 KB
16.81 KB

Decision about the current location and colour of the "Follow" button was made back in May, when Bojhan, yoroy, dww and I were reviewing and finalizing new issue page UI. The colour was changed, because we can't have 2 big green calls to action on one screen. We want to make new way of updating issues obvious since it changed significantly, so 'Update this issue' button is huge and green. Follow button has to be smaller and of a different colour. Grey was the only colour we were able to use for it from the current Bluecheese palette.

Location changed because Follow button didn't really fit inside the new Issue details block and we were trying to find a place for it outside of the block: either next to it or outside of sidebar completely. Advantage of the current location was that it's not too close to the main action button on the page. Considering that people have troubles finding the button now, we should move it back to the sidebar.

The mockup we worked on for the sidebar location:

tvn’s picture

Title: Issue page redesign: Move "Follow" button » Move "Follow" button back to the sidebar
yoroy’s picture

Issue tags: +Usability

If we agree that 'updating issue' should be more prominent than 'Follow' then this design seems fine to me. The arrangement in #8 makes the follow button much more discoverable than current position so that would be an improvement.

webchick’s picture

Looks good to me!

YesCT’s picture

updating makes people follow anyway, so I think this is ok.

jthorson’s picture

Assigned: Unassigned » jthorson
jthorson’s picture

Status: Active » Needs review
FileSize
631 bytes

This should be all that's needed, after #2001014-7: Port "Jump to" links to D7, which handles the css style changes that would also be needed.

Because it alters an existing update function, this change would require a full migration before it appears on git7site.

jthorson’s picture

FileSize
21.87 KB

Screenshot from dev site, with all patches applied.

yoroy’s picture

Status: Needs review » Reviewed & tested by the community

Rtbc it is?

drumm’s picture

Status: Reviewed & tested by the community » Fixed

Committed.

jthorson’s picture

Status: Fixed » Active

Looks like this didn't take on git7site ... re-activating to take another look.

jthorson’s picture

Status: Active » Fixed

My bad ... this wasn't committed before the last migration would have started. Will wait a few days first.

Status: Fixed » Closed (fixed)

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