Can a plugin prevent a case from being committed, for example to prevent invalid data or satisfaction of some requirements (such as a non-empty bugevent)?
|
4
1
|
|
|||
|
|
|
1
|
No, plugins cannot abort a bug commit. This is because it amounts to requiring a field (which we're not into). Our philosophy would be to accept the edit, but assign the case back to the user asking them for a valid value for the field in question. If you would like to see this change, please vote up this question to get it in our top 100 feature requests by votes. Once there, we will file it as an official request. |
|||
|
|
|
-1
|
You guys make me angry. I just paid over $700 to spend a sleepless night upgrading FogBugz 5 to version 8, expecting that surely, by now, you would have implemented CAPTCHAs for public case submission. I find out that you didn't. Crap. All this work upgrading my FogBugz installation for nothing. But wait, there's this shiny new plugin architecture. There's a ReCaptcha example in it. Maybe I can use that. So I spend a couple hours modifying the ReCaptcha example to work with case submissions. I try to compile, and... whoop! Turns out that the return type of BugCommitBefore is actually void, not boolean. I cannot stop a public case submission. What good are plugins if you can't modify behavior? Your stubborn philosophies, and your refusal to implement the most basic features requested by your customers after years, make me sick. I want my money back! |
|||
|
