Mainly it had to do with the abilities JIRA gives us (workflow adjustements for example) which were all rudimentary on different products (bugzilla is horrid) - but the main factor was basically the tight integration with other development tools provided by Atlassian (continuous integration, source code view, source code review, etc.) - with our old bug tracker we would've spend days, weeks, months for programming this - which is just not acceptable.narqelion wrote:I found it mind boggling that this was "the best solution" you could come up with.
Of course it is - it is always the case with a product you code for your own internal use, you only have one market you serve.The old tracker was far superior to the new one in terms of performance, usability and plain old useful functionality.
There still needs to be real commit messages sent and the redmine view updated to git - but without the correct commit messages there is of course no linking. It does not matter where it is displayed, if the commit messages are not noting the bug number (PHPBB3-XXXX) then no linking can happen.It would have made sense had you migrated to Redmine's Issue tracker to maintain consistency with the project management side and maintain the ability to link tracker tickets to repository revisions. Now all of that is lost.
If you mean adding revisions by hand to the ticket - this is possible if the dev team leader adds this to the issue field views.