search

mantisbt-plugins / source-integration

Source control integration plugin framework for MantisBT, including support for Github, Gitlab, Bitbucket, Gitea, Gitweb, Cgit, Subversion, Mercurial and more
http://noswap.com/projects/source-integration/
MIT License
181 stars 130 forks source link

No Update is happening. Status and resolution not set when issue is fixed #332

Closed ghost closed 3 years ago

ghost commented 4 years ago

I have installed the plug in to Mantis but I do not get it right. I add "resolved #146" in the commits on the CLI but the status is not updated to the resolved as we have as our next status.

Please see screen shots for configuration

When I test this it does not work as it should

What is wrong here. Please advise

Annotation 2020-01-01 121606 Annotation 2020-01-01 121550

steffen-wilke commented 4 years ago

I'm currently experiencing the same issue. The changeset is attached, the "Bug Fixed Message" is created, but the issue itself is not set to resolved.

Used VCS: SVN

Might be related to #229

jchampeau commented 4 years ago

I encountered the a similar issue. Changesets were being added to the bug but the bug was not being marked as fixed/resovled. I found 2 issues:

  1. The configuration option "Bug Fixed Assign To Committer" needed to be enabled. I was confused by wording as described in #229.

  2. The SVN username did not match to any username in MantisBT. Once I corrected this it started working for me.

While trying to figure out the second problem, I was looking at the function Source_Process_Changesets() in Source.API.php. There are checks on the user existing and having enough privileges to update the status/resolution fields. I added some logging to figure out which conditions were preventing the updating of the bug's status. There are also some checks on status thresholds. So if you have customized your statuses maybe that could be causing issues.

dregad commented 3 years ago

I'm not able to reproduce this - as mentioned by @jchampeau this is probably related to your configuration.

I don't see much value in keeping this open, considering that it's mostly the same topic as #229.