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

johnalbin’s picture

johnalbin
they/他
Primary language English
Location Taipei, Taiwan
commented
Version: 4.7.x-2.x-dev » 5.x-2.x-dev

This is a much better idea than unpublishing releases. We’ll have to see how itchy this issue gets for me. ;-)

cmundi’s picture

cmundi commented

Yes! This approach is *much* better than what I proposed yesterday as #438030.

This would be very useful.

Carlos

aclight’s picture

aclight commented

As 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.

aclight’s picture

aclight commented
Version: 5.x-2.x-dev » 6.x-1.x-dev
merlinofchaos’s picture

merlinofchaos commented

Yep. Totally on board with this.

senpai’s picture

senpai commented
Version: 6.x-1.x-dev » 7.x-2.x-dev
Assigned: dww » Unassigned
Priority: Critical » Normal
Status: Active » Postponed

Bumping 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.

senpai’s picture

senpai commented
Issue summary: View changes

This issue is postponed until the D7 Upgrade is launched.