> Well, a thought did just pop up, which is that we need to check that
> the user can actually change the various properties of a task *before*
> we create that task, otherwise we end up in the interesting position
> of having a Bug with no BugTasks, which is going to cause OOPSes.
An exception is probably (almost certainly) raised and the transaction
aborted.
> Well, a thought did just pop up, which is that we need to check that
> the user can actually change the various properties of a task *before*
> we create that task, otherwise we end up in the interesting position
> of having a Bug with no BugTasks, which is going to cause OOPSes.
An exception is probably (almost certainly) raised and the transaction
aborted.