Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
ghost opened this issue Jan 1, 2020 · 3 comments
Closed

Comments

@ghost
Copy link

ghost commented Jan 1, 2020

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
Copy link

steffen-wilke commented Feb 4, 2020

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
Copy link

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
Copy link
Member

dregad commented May 13, 2021

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.

@dregad dregad closed this as completed May 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants