If you use the devel module to generate project releases, it does not randomly pick project to associate the releases with. There is no way to correct this after the fact, so it basically makes the devel module useless in testing the project / release association. For issues the same issue with the devel module exists, however if one chooses to edit a generated issue the first message that comes up is that an invalid project is selected and it must be changed. So the feature request is to include the same kind of message for a project release node if it is not assigned to a project.

Comments

aclight’s picture

aclight commented
Title: Project Releases that aren't assigned to a project can't be assigned. » Generated project_release nodes should be attached to projects
Category: feature » bug

I think a better approach would be to have releases generated by the devel module be assigned to a project. I don't think it makes sense to add in the ability to provide a user interface to change the project a release is associated with, since I don't see how that would ever be useful (assuming that generated releases had a project assigned in the first place).

BTW, I would think it'd be a pretty easy database query to manually associate releases you've generated with projects, just for testing purposes.

kanato’s picture

kanato commented

Yes, that would make sense. Should I report this as a bug / feature request for the devel module?

aclight’s picture

aclight commented
Category: bug » feature

Nope, I think this is something that would need to be implemented in project itself.

Originally I thought this was a bug, but actually I don't think we have code in the project_release module at all to automatically generate releases (I was thinking of project_issue), so I'm setting this back to be a feature request.