[mantisbt-dev] "community" user in bug tracker

[Victor Boctor]

Hi all,

I just merged the SOAP API pull request which ended up marking the issue as resolved by me. I thought it may be a good idea to mark issues that are fixed by the community differently from ones that are fixed by the core dev team. Hence, I created a “community” user with access level DEVELOPER and assigned the issue to that user.

Thoughts?

-Victor

[Damien Regad]

Post by Victor Boctor
I just merged the SOAP API pull request which ended up marking the issue as
resolved by me. I thought it may be a good idea to mark issues that are fixed
by the community differently from ones that are fixed by the core dev team.
Hence, I created a “community” user with access level DEVELOPER and assigned
the issue to that user.
Thoughts?

It doesn't really hurt I suppose, but I'm not really sure what you are
hoping to achieve by this.

[Roland Becker]

Post by Damien Regad

Post by Victor Boctor
I just merged the SOAP API pull request which ended up marking the issue as
resolved by me. I thought it may be a good idea to mark issues that are fixed
by the community differently from ones that are fixed by the core dev team.
Hence, I created a “community” user with access level DEVELOPER and assigned
the issue to that user.
Thoughts?

It doesn't really hurt I suppose, but I'm not really sure what you are
hoping to achieve by this.

Consider that we sent emails to the community user and that we can't disable all
of them by configuration [1].
You configured ***@localhost for the user.
I am not sure if there will be a problem sending email to this user.
If so, we will generate entries in mantis_email_table that will never be cleared
(and the cron job will try to sent them again and again)

[1] https://mantisbt.org/bugs/view.php?id=12030 and related issues