issue-tracking

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 6 years ago . Besides the painful-to-install non-Windows Bugzilla , what open-source issue tracking programs can be recommended that are just as good but available as a regular windows-style install? ( .exe or .msi ) You can try Redmine - a painless

I recently started to use GitHub Mylyn connector for Eclipse and I have it working, I create new tasks and I can see them in Eclipse and GitHub. The problem is when me or someone else create an Issue on GitHub I can't see it on Eclipse. I have done this and configured Mylyn on that way as you can see in the image: But as you can see under "Bugs and Enhancements" I have nothing and here I actually have one issues, so, why don't they appear? Is something to do with the fields Assigned to and Mentioning ? I have filled both with my GitHub username, then only one but with no results. I was also

I amended a commit a few times and did push --force each time (stupid mistake; I didn't realize until getting ready to send a PR that my editor had generated tons of noise by fixing tabs and trailing whitespace). The commits that I thought were no longer existent are still reachable on GitHub, and the issue reference causes a list of links to these non-existent commits to appear: How do I get rid of these commits on the GitHub remote so that these extra links will go away? In general, you cannot remove a commit from Github yourself. As pointed out in the answers to the other question linked as

First I thought it's strange that there's no link to a bug tracker on the OpenJDK project page , then I found bugs.openjdk.java.net , but it's only for accredited project members. How do people outside the ivory tower contribute issues? There's the mailing list and some people call sending issues and patches to a mailing list bug tracking... but the development and usage of bug tracker contradicts. I wanted also to report a bug and the only place I could find is the following one: http://bugreport.java.com/ I hope it is the correct place, Oracle engineer might end up creating an issue in the

I noted that in BitBucket when your commit log contains a number like #12 this number is linked to the bug number 12. I found this feature interesting, and I wonder if there is any keyword that would allow me to mark the issue as resolved from the commit log instead of going to the web interface each time. If BitBucket doesn't do it, could you point a system that does? Rob Van Dam Bitbucket already supports marking issues on commit using the Issues service . The issues service scans commit messages for commands which will automatically change the state of the relevant issue on the tracker.

I know you can close issues by putting closes #1 or fixes #1 in the commit message. What is the best way to close multiple issues in the same commit message? Also, it appears that using fixes rather than closes doesn't create a link from the commit message to the issue, but it does close the issue. What's up with that? Closes #1, closes #2, closes #3; rest of commit message. The closes clauses can be anywhere in the message and fixes is a valid synonym: This fixes a memory leak in foo() that closes #4, also fixes #5 which is a duplicate. The following used to work, but nowadays only references