I often find myself updating an issue summary and once I save the node I realize that I either forgot something or did something unintentionally. I then re-edit in order to add info or revert any unintentional changes and re-save. Of course -since I'm only human- there are times when even my second edit doesn't get things right, so I re-edit and re-save for a 3rd time or more.

In some other cases I keep coming back to the same issue several times in order to add information as I come across it. For example like in #2132095: Allow defining specific comment # in related issues meta. where I kept coming back to add related issues as I was spotting them in the issue queue.

In both the above use cases (+ some that might not cross my mind right now) what happens is that we have multiple successive nodechange comments added to the issue node. Now, if that happens many times we end up with really long issues while we could save the vertical space if we merged these nodechanges into a single one.

This idea was officially brought up by @xjm over at #1991500-32: Blocks in sidebar on issue pages forces the rest of the page to 2/3 width

Comments

tvn’s picture

tvn CreditAttribution: tvn commented
Issue tags: +D.o UX
mgifford’s picture

mgifford
he/him
Primary language English
CreditAttribution: mgifford commented

This is a nice idea. I sometimes find that happens for me too.

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
CreditAttribution: klonos commented

Another use case where the "noise" added by successive comments is more apparent is #1757550: [Meta] Convert core theme functions to Twig templates. I've been following that issue and it seems that the three people most involved there are @jenlampton, @Cottser and @joelpittet. They keep editing the issue in order to re-arrange the listed issues and most of the times they post 2, 3 or even more comments within only a few minutes (because for example they might have missed something). The intermediate edits are corrective 99,9% of the times and what matters is the latest edit which holds the actual intended end result. Having separate nodechange comments for each minor edit has caused this issue to exceed the threshold that splits the page into separate pages. This could have been avoided if we had something in place like what I propose here.

The reason why I'm not adding this use case in the issue summary is because I have another idea about it and I will file a separate feature request. You see, the actual root of the problem seems to be that we need an automated way to list issues sorted by various criteria. The successive comments in that issue are merely a side effect.

Anyways, thanx for acknowledging the usefulness of this.

joelpittet’s picture

joelpittet
Primary language English
Location Vancouver
CreditAttribution: joelpittet commented

Need more use-cases: #2006152: [meta] Don't call theme() directly anywhere outside drupal_render() :)

joelpittet’s picture

joelpittet
Primary language English
Location Vancouver
CreditAttribution: joelpittet commented

FYI we are looking at rocketship to manage the lists instead of on the meta itself.
https://drupal.org/project/rocketship

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
CreditAttribution: klonos commented

...no need for specific use cases. Within a minute you just posted two comments that could have been one :P

joelpittet’s picture

joelpittet
Primary language English
Location Vancouver
CreditAttribution: joelpittet commented

We could try and make this one a use-case? Challenge:P

tvn’s picture

tvn CreditAttribution: tvn commented
Project: [Archive] Drupal.org D7 upgrade QA » Drupal.org customizations
Version: » 7.x-3.x-dev