On 09/11/2018 01:16 PM, Nathan Cutler wrote: > (This is a question for David Galloway, I guess, since this problem > arose within the last couple days as he has been battling the spammer.) > > Today I noticed that when I go to create a new issue in the Backport > tracker, it shows all the same fields (both standard and custom) as when > I create an issue in the Fix, Bug, Feature, etc. trackers. > > This is change from the previous state, in which the Backport tracker > had only a small subset of these fields. > > What's really strange about this is when I go to edit the Backport > tracker to turn off all those fields that aren't needed, I can see that > Redmine thinks they aren't there: > > http://tracker.ceph.com/trackers/9/edit > > Saving this state has no effect: when I try to create a new Backport > tracker issue, I still see all the extra fields. > > Also, I suspect this may be the root cause of another problem that > appeared within the same (last few days) time frame: our > "backport-create-issue" script, which uses the Redmine API, can no > longer create Backport tracker issues. > > David - whelp? > I think you're right in that the Backport fields and backport-create-issue problem are related. I think the Captcha I added to the New Issue page was to blame. I rolled the reCaptcha plugin back a few commits and the Backport creation page is rendering correctly now. Can you test your script again please? If the plugin /is/ to blame, I'd love it if someone with some rails experience could lend a hand in getting the Captcha to show up at the appropriate time and not mess with the page rendering!
