We have a self-hosted Atlassian infrastructure. Jira is hooked up to Fecru, and Fecru is hooked up to a Subversion server. Any commit messages that contains a Jira key like PROJKEY-123 show ups in the Jira issue's page under "Development: <number> commits". You can click the that link and it takes you to the Fecru page showing those commits.
I've become the sole developer on one of those projects, and I'd like to switch from subversion to git. However, I don't want to alter history, just start using git going forward. Would I be able to add a git repository to a project, and have Jira show commits from both subversion and git? Old issues would still link to the Subversion commits, while new ones to the git commits.
Hi,
I understand that you're currently using Fisheye/Crucible with Jira. However you are looking to start using Git, and want to be able to see those Git, pull requests, commits, branches that contain Jira issue keys as well.
Jira should have no problem being able to display this developer data from multiple sources simultaneously. My question is where are you planning to use Git from? Is this something you might use Bitbucket for? or perhaps Github?
Either of those should be fine, as Jira Server does have the DVCS plugin. More details in Linking a Bitbucket or GitHub repository with Jira. This allows Jira Server to connect to Bitbucket or Github so that Jira can see that data and then relate it back to your Jira issues. Which is technically a different method that allows Jira to connect to this development data than the method that Fisheye/Crucible (Fecru) uses. But since Jira does permit more than one source of such development data, I don't foresee any complication in regards to being able to see history here.
I hope this helps, please let me know if you have any additional concerns here.
Cheers,
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.