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.On the D6 site users tended to comment on issues and would very rarely edit the issue node itself. I guess that's why the big green "Update this issue" button has been added, to encourage keeping the issue nodes up to date.
But while users used to choose between comment & edit, they now have to choose between 3 actions - "Add new comment", "Update this issue", and "Edit". I suggest that's 50% more confusing than on the D6 site. I was confused, anyway.
It's unclear what the difference is between Update and Edit. Of course, when you click both it turns out that there is no difference.
I suggest at least renaming "Edit" to "Update" so there's consistency. Or vice-versa.
And it should be very clear whether users should normally comment on or edit the issue.
AND meanwhile, the "Update this issue" looks a lot like the old "Follow this issue" Flag button, but on this particular (DrupalCon Prague) user test, I can't see any Follow buttons at all. [update: it's in the top left! aha! but it's light gray and tiny so I didn't see it]
| Comment | File | Size | Author |
|---|---|---|---|
| Screenshot from 2013-09-25 22:26:20.png | 59.21 KB | pjcdawkins |
Comments
Comment #0.0
pjcdawkins CreditAttribution: pjcdawkins commentedUpdated issue summary.
Comment #1
jthorson CreditAttribution: jthorson commentedFollow button tracked in #1991726: Move "Follow" button back to the sidebar.
Adding functionality currently behind 'Update this Issue' to the issue page itself in #2097927: Remove 'Update this issue' link next to main comment form when issue updaters are used to the new green button.
Keeping this for the 'rename Edit to Update' suggestion ... let me know if I've missed anything!
Comment #2
tvn CreditAttribution: tvn commented.
Comment #3
tvn CreditAttribution: tvn commentedComment #3.0
tvn CreditAttribution: tvn commentedUpdated issue summary.
Comment #4
dwwAdding this to the meta issue about the D7 issue update workflow problems.
Comment #5
dwwWhoops, cut + paste error. ;)
Comment #6
mgiffordI agree that this is confusing. Particularly since there are 2 "Update this issue" buttons & also an edit link.
Comment #7
danylevskyiI think we should leave the tab labels unchanged. It's more confusing to have 10 content types with 'edit' tab and and 1 with 'update' tab.
I propose 2 options:
Comment #8
tvn CreditAttribution: tvn commentedThis is more of a UX issue. Untagging from 7.1, Developer tools team should look at this.
Comment #9
Bojhan CreditAttribution: Bojhan commentedThis sounds like something that we should just a/b test I am not sure about the impact of Edit vs. Update. The reason we chose update because we thought edit was too verbose and implied a complex activity. We should just a/b test the following variants 1) "change all to edit", 2) change the sidebar button to "edit" and 3) change the "edit" secondary nav to "update".
Comment #10
drummI'd be okay with going ahead and changing the local task to "Update". That was chosen for a reason, and "Edit" just exists because it is a default local task.
Comment #11
Bojhan CreditAttribution: Bojhan commentedI think this is a very small issue and I will leave it up to drumm to decide.
Comment #12
drummLet's go with "Update".
(I remembered that this isn't just edit, it is commenting too.)
Comment #13
drummComment #14
drummThe “Update this issue” button has been removed.