New bug-tracker testing

I decided I wanted to move the bug tracker away from Bitbucket, and into a self-hosted system.
After trying several options, I've chosen to use MantisBT as the issue-tracker.

The main reason for the change is that I find Anonymous bugs to be detrimental because there is no reliable way to ask for more info. So I decided to use single-sign-on such that the forum account can be shared with the bug-tracker.

I've imported the Deviation repo and BitBucket bugs into Mantisbt, and I wrote a single-signon module for it. The module is not working perfectly yet (it seems to require a relogin instead of using your existing forum login), but it does use the same account info for login.

I also had to write the importers for the hg db and for the bitbucket bugs too, so I'm not sure they all imported smoothly.

I would appreciate feedback from anyone who is interested to try it before it goes live.

deviationtx.com/mantisbt/

Feel free to do whatever you like there, as I will wipe and rebuild the database before I switch over. Also don't file any tickets there that you actually want to keep for the same reason.

Besides the need to relogin, I have not yet hooked the deviation repo to it yet (so a commit to the repo will not update the bugtracker) but that is next on my list.

Please report any issues/comments in this thread

Thanks for the feedback.

I fixed the Category issue. I had disabled categories in an attempt to minimize the number of fields, but apparently was required, which broke things. I've now made categories optional, which makes it possible to add new issues.

As far as editing issues goes, my expectation is to have all users who are members of the deviationtx group on bitbucket have developer access, allowing them to edit tickets. For everyone else, you can only add notes and edit your own tickets. I have added you as a developer so you can test the ticket editing.

The regex matching patterns are a bit weird.
You can use:
#<bug id> To refer to a bug id
~<note id> To refer to a note
s:deviation:<commit_id>: To link to mantis's commit info
v:deviation:<commit_id>: To link to BitBucket's commit info
(note that you can use abbreviated commit-ids and it works properly)

There is not currently a way to refer to a pull-request from a ticket, but I can probably add that.

PhracturedBlue wrote: The regex matching patterns are a bit weird.
You can use:
#<bug id> To refer to a bug id
~<note id> To refer to a note
s:deviation:<commit_id>: To link to mantis's commit info
v:deviation:<commit_id>: To link to BitBucket's commit info
(note that you can use abbreviated commit-ids and it works properly)

I have now added:
p:deviation:<pull-request-id>:
Which will let you link a pull-request as well.

Thanks for the input. I'll fix the importer for the platform. I'll also look ito the a-accent thing (seen that before). I think your weird o+umlaut is a browser thing. I used the character-map to add a bunch of custom characters to a note and it worked fine.

I agree that Mantis is a bit different, (I personally don't think the issue list is pretty or super obvious to use) but despite all the bug trackers out there, my choices for a well supported, self-hosting, php-based (needed because Deviaton is on shared hosting) system supporting mercurial SCM and a plugin architecture (for joomla SSO) were actually quite limited. I played with a couple, and I think Mantis is good enough. It is easy to add tickets (which is probably the most important), and flexible enough to allow us to do everything we need. I want to verify commit updates work as intended from BitBucket (I have integration enabled now), then I'll re-import everything and do the switchover.

Thanks again for the help testing it out.

I've disabled the bitbucket bug tracker and re-imported all issues. Hopefully everything is working now.

it requires a trailing colon

Thanks. I've fixed it

Anybody watch Bug Tracker? I don't see any changes or responses about a month.

I would like to get fully operational Devo telemetry, specifically GPS telemetry.
www.deviationtx.com/mantisbt/view.php?id=610

Your bug was the 1st filed in about a month
All of the developers should be CCd when a bug comes in now. I certainly saw it. I will probably take a look at the difference between 3.0 and 4.0 telemetry and see if I can figure out why GPS stopped working.