our current target audience is normally deploying their own
issue tracker instance within their internal corporate network and
in the short term we are focusing on providing plugins for the most
common issue trackers such as Jira to integrate and automate as
much process and workflow items as possible including code reviews,
pull requests and smart commit logic to transition issue tracker
items into the desired status using commit messages.
That said we are investigating the option to build, integrate
and roll out a simple issue tracker together with RhodeCode
Enterprise already for multiple months and we are always eager to
get further market feedback. Did you use any specific issue tracker
before? Would you prefer an issue tracker that is attached to each
repository or rather a product that has it's own interface but a
good integration with RhodeCode Enterprise? We are looking forward
to hear your opinions on this topic.
Are you currently evaluating a new integrated solution for
source code management, issue tracker and code review for your
team(s) or are you already using RhodeCode Enterprise and it would
be a great addition to your current RhodeCode environment.
As mentioned before we are really eager to provide a great
integrated issue tracker experience independent from the deployment
size and any feedback / ideas based on your current environment are
+1 to this request. We use a 3rd party issue tracking system (FogBugz) for tracking development of our main product. Outside of that we have lots of internal engineering focused projects that would benefit from a small and simple issue tracking component similar to that found in GitHub. If you do build one, I fully support you guys keeping it as simple as possible and telling customers to look at 3rd party solutions if they need more complex workflows. The ability to enable/disable per repository would help facilitate the described behavior.