Last modified: 2013-08-08 07:38:04 UTC
For example, when I moved bug 50746 from ULS to MediaWiki, you will get a confirmation view with three values to choose: version, component and target milestone. I chose ResourceLoader as the component and clicked commit. Page only reloads with no message. I chose 1.22-git as the version and click commit. Now it succeeds but apparently it had reset my component to API while reloading the page.
Bugzilla does not allow defining a general default value for the "Move to other product" dialog (while you can define that for enter_bug.cgi). If the previous version value for product X also exists for product Y, Bugzilla will by default preselect that value. I'm not sure if setting a general default value for the "Moving from product X to Y" dialog makes sense (would be an upstream enhancement request). As the version "master" exists in product "MediaWiki extensions" but not in product "MediaWiki", that's expected behavior, hence closing as WORKSFORME here. However, if I had a time machine I'd not introduce the version "master" as it's meaningless over time. With the current setup, I might need to start mass-moving tickets with "master" version to "REL_1_xy branch" whenever we branch, so master tickets really only refer to current master. Hmm, hmm. Untidyness.
