it'd be nice if the issue queue always let you leave the version alone, even if you're replying to an old issue pointing to a now-unpublished release. i.e. always insert the current value, whatever it is, into the list of valid choices for the version of an issue. the version string itself should be visisble, even if the release node is unpublished.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 97145_pi_version_4.patch | 2.29 KB | aclight |
| #4 | 97145_pr_versions_4.patch | 3.2 KB | aclight |
| #2 | 97145_pr_versions_2.patch | 2.46 KB | aclight |
| #2 | 97145_pi_version_2.patch | 2.22 KB | aclight |
Comments
Comment #1
aclight commentedYep, this is still a problem, as I discovered last night when commenting on a lot of old issues in the project queue. I'm updating the version to reflect that this is still an active issue.
Comment #2
aclight commentedHere's a patch for both the project release module and the project issue tracking module that takes care of this.
I needed to make a change in the project release module so that the versions are still sorted in the right order.
Tested locally and works well for both admin and regular users.
Comment #3
hunmonk commentedlet's not put $rid directly into the query string -- it makes baby jesus cry... ;)
this can easily be worked around by passing the db_query() params as an array.
Comment #4
aclight commentedThe baby jesus does not cry.
But this will ensure his tears are absent.
Comment #5
hunmonk commentedlooks good. tests out. committed to project release 5.x and HEAD, project issue 5.x-2.x and HEAD.
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.