...as per title.

Now, if we could somehow figure out a way to automatically also change the priority to "critical" and then revert it back to what it used to be before change, then that would be awesome.

Comments

Gábor Hojtsy’s picture

Reality is when there is no change notification, the issue is Active and when there is one but needs review, its in Needs review, so then you would say there would be two new statuses, "Needs change notification" and "Needs change notification review"?. The point of using the tags (and title change) is to ensure we can go into different statuses for another round on the issue. Another (ugly) option would be to make every issue a meta issue and do the change notification as a sub-issue. Drupal.org is not really scalable for that.

xjm’s picture

Status: Active » Postponed

This is actually a totally legitimate use of the tag system. The need to change the title, status, category, and priority is what's ugly about change notifications, not the tag. The use of the tag fits entirely with all our other "Needs" tags. (There should also be a feature request to move these "Needs" tag tasks to a separate field of their own; I will add it to this issue when I find or file it.)

However, we are currently considering changing the process for change notifications entirely so that change notifications will be required prior to commit, for everything other than critical bugs. So this issue should be postponed on that discussion.

Also, I think there's a duplicate of this issue in the core queue somewhere.

Mixologic’s picture

Project: Drupal.org infrastructure » Project
Version: » 7.x-2.x-dev
Component: Other » Issues

Moving to appropriate queue.