Bug tracking integration

[lbauer]

I'm not sure why the update bugs section is greyed out. In Vault 4.1, 4.1.4 and 5.1.2, this area is enabled, even if no bug tracking is configured. We did some testing and found that if the database value for bugurl is NULL (as opposed to "blank", the BugID box is greyed out.

Did you make any changes to the Vault database?

Are you connecting to the correct Vault Server?

What exact version of Vault 4.1 are you using?

[kkchan]

We did some testing and found that if the database value for bugurl is NULL (as opposed to "blank", the BugID box is greyed out.

No, it is not NULL, please refer to screeshot

Did you make any changes to the Vault database?

Never, as it contains very important data. We dare to change it manually

Are you connecting to the correct Vault Server?

Sure, we only required to define in SINGLE web.config right? And we only have one instance of VaultService in our office. We do not have backup website for it, as we only backup the db intervally.

What exact version of Vault 4.1 are you using?

4.1.4 (18402)

[lbauer]

I ran the query exec dbo.splistrepositoryoptions on my own Vault Standard repository. The values were the same as yours except for the bugurl (expected) and defaultaccesslevel (not expected). My defaultaccesslevel value was U, which is "Access;" yours is N, which means "No Access."

Not sure if that might be causing a problem or how that setting is set in the repository options. It probably refers to Repository Access. This setting is in the Admin Web Client under Source Control Repositories->(Repository name)->Repository Access. Users can have No Access, Access or Full Admin. Perhaps you are running the API under a Vault account that has no repository access?

[kkchan]

Hi
Default repository access is No access, which is correct. But I have explicitly assignment for all users already. Most importantly, I am using admin to test on this.

Do you mind to remote in for checking?

[lbauer]

Contact me and we can do an online session. Email support at sourcegear.com, Attn: Linda. Please include a link to this forum post.

[lbauer]

We did a remote session with this user. The reason the Update Bugs field was grayed out was because he was checking in an unmodified file.

The default behavior for checking in an unmodified file is to Undo the checkout. So it makes sense that Vault would not allow you to associate it with a bug, because there would be no checkin.

helspot 225401