The nice JS we have to automatically update the Version and Component fields for issues whenever you toggle the Project works fine when adding a new comment. However, when you first submit the issue, or go back and edit it, the JS doesn't work. Of course, we want to discourage editing issues to change stuff, anyway, but certainly for creating them, it'd be nice if this worked.

I confirmed this both on a clean d.o testing install profile site, and on d.o itself.

Comments

hunmonk’s picture

hunmonk commented
Status: Active » Postponed

this is due to the stupid renaming we have to do on the followup form to avoid namespace collisions with comment module's pid form field. IMO, this should be fixed properly along with the other namespacing issues in project/project issue.

postponing until those larger issues get fixed, which will make this fix simple (or unnecessary).

dww’s picture

dww
we/he/they
commented

sounds reasonable, thanks for clarifying the underlying problem.

dman’s picture

dman commented

Does clicking 'preview' help this a little?
It's an extra step, but it's a habit I'm used to when dealing with dependant selects etc.
Not a solution, but a work-around.

dww’s picture

dww
we/he/they
commented

Sadly, no. It doesn't seem to update the component and version options on a preview when creating a new issue. :( That might be an unintended side-effect of #199138: Remove multipage form for issue nodes.

dww’s picture

dww
we/he/they
commented
Status: Postponed » Fixed

This is now fixed via #326419: validating Version and Assigned against potentially the wrong project. There's no longer a project selector when you create/edit an issue so this JS problem doesn't matter. ;)

Status: Fixed » Closed (fixed)

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