Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Use bug trackers defined in the DB #79
NOTE: this is the bare minimum patch to get a custom bug tracker running. I've seen a few places where I've left visible artefacts from the Bugzilla and JIRA hard-coding but I'll remove them later.
I'll focus first on getting tests working into the local environment and enabling Travis-CI before I can continue any further.
@tkdchen it's been a while since I had the opportunity to work on this but it is ready for merge.
There are a few setbacks, see my comments above, but those are really not such a big deal and I will fix them in a separate PR.
The updated version is rebased to the latest develop branch and properly handles client side validation of bug IDs as you previously requested. I have also fixed a few minor bugs and made some improvements, see the commit log messages.
Waiting for review. You can also ping me on IRC.
This was referenced
Apr 29, 2017
As mentioned in #185, IssueTracker should be the new name of this integration with Bugzilla, JIRA or any other things that are able to manage issues. So, "bug tracker" should be replaced through the code and documentation properly.
I'll use a separate branch to merge issue tracker related code, and then merge it into master once the improvement is completed and good enough.
BTW, currently, master branch should contain code that belong to milestone 4.0.