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.Related Issues
#1665580: Add version field back to project_issue views has just been ported.
Problem/Motivation
It'd be great to be able to restrict the allowable choices for the "Version" field in the issue queue other than simply unpublishing the release nodes for the versions you don't want to see. unpublishing makes the version completely invisible in the queue, old issues/comments against that version now look like they have no version at all, etc, etc.
but, we don't want people to submit *new* issues against these versions (e.g. the "x.y.z" version of core, see http://drupal.org/node/94702), even if we want to still want to see them.
Next Steps
This issue is postponed until the D7 Upgrade is launched.
Comments
Comment #1
JohnAlbinThis is a much better idea than unpublishing releases. We’ll have to see how itchy this issue gets for me. ;-)
Comment #2
cmundi CreditAttribution: cmundi commentedYes! This approach is *much* better than what I proposed yesterday as #438030.
This would be very useful.
Carlos
Comment #3
aclight CreditAttribution: aclight commentedAs a note, completing #75565: make a hook to get version options for a given project would make it pretty easy for a small custom module to restrict the version fields for a project, though providing a UI to do so might be more challenging.
Comment #4
aclight CreditAttribution: aclight commentedComment #5
merlinofchaos CreditAttribution: merlinofchaos commentedYep. Totally on board with this.
Comment #6
Senpai CreditAttribution: Senpai commentedBumping the version from 6.x to 7.x since #1665580: Add version field back to project_issue views has just been ported, and downgrading it until the D7 Upgrade is launched.
Comment #6.0
Senpai CreditAttribution: Senpai commentedThis issue is postponed until the D7 Upgrade is launched.