Email should be generated when bug number isn't on project

[Ted Gould]

One of my favorite features of Soyuz is how it looks at the changelogs to update the bugs statuses. The problem occurs when the bug is not on the same package as what is uploaded. While I agree with idea that this means the bug shouldn't be changed, the uploader should get an e-mail about this. There have been several bugs, which were fixed, but I didn't realize I hadn't updated the bug to be on the right source package.

[Julian Edwards (julian-edwards)]

Ted, can you give me a concrete example of this please? It would help to see the exact problem.

[Ted Gould (ted)]

On Fri, 2009-10-09 at 13:37 +0000, Julian Edwards wrote:
> Ted, can you give me a concrete example of this please? It would help
> to see the exact problem.

I can't find a bug that has done it quickly, but I think I can describe
it. I think I may have used the wrong terms in the original
description.

Many people file bugs on indicator-applet, that's basically how they see
the thing on the panel, so they file bugs on that package. It's not
entirely incorrect, but many times those bugs lie in indicator-messages
which is loaded by indicator-applet.

So, they file the bug against indicator-applet, and for what ever reason
I forget to move it to indicator-messages, or I just don't notice that
it's misfilled. I fix the bug. Put the bug number in the changelog,
and get the package sponsored.

The bug doesn't get marked "Fixed Released" because it's an upload of
indicator-messages and the bug in on indicator-applet. Just to be
clear, I think this is reasonable behavior. But, what I'd like is an
e-mail in this case so that I can go "Oh, I was an idiot, I'll go close
that bug."

Thanks!

  status new