drupalorg_project_form_alter() selects a version for create issue links with a version parameter. This accepts a release node ID. A human-readable version number, like 6.x-3.x-dev, would be much more useful for #1001588: File an issue links on a.d.o need to go to projects and be easier all around.

Comments

dww’s picture

I still think this code would be better in project_issue. ;)

+1 to supporting both. Should be pretty easy to call is_int() and if that fails, try to find the right release via the version string and project ID (which we already have).

jhodgdon’s picture

Issue tags: +docs infrastructure

tagging. I might be able to look at this soon, although I have a few other issues in my queue at the moment.

jhodgdon’s picture

Issue tags: +Developer improvements

tagging again

jhodgdon’s picture

Issue tags: +api.drupal.org contrib

Adding new issue tag for issues pertaining to getting all contrib modules on api.drupal.org.

jhodgdon’s picture

Version: 6.x-3.x-dev » 7.x-3.x-dev
Issue summary: View changes
Status: Active » Fixed

This was taken care of sometime during the 7.x update of Project Issue and/or drupalorg.module. In a file an issue link, you can now do something like "version=7.x-dev" and the version will be filled in correctly. This is working on api.drupal.org.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.