Recently we made some alterations to our project tree structure in VersionOne renaming a number of elements in the tree to better suit our work practices. The result of this was that subsequent issues passed across from Jira to V1 via the VersionOne ServiceHost bridge integration tool no longer found their way into the desired point in the in the V1 project structure.
After some investigation it was uncovered that, in order for issues from Jira to find their way to a specific point of the project structure in V1, both the Jira and V1 project names had to match exactly. Having, reluctantly, changed the project name in Jira to match that of V1 the issues again dropped into the expected location in V1.
What would be very useful, from our perspective, would be the possibility to remove this close coupling of project names instead being able to create a mapping in the ServiceHost config file whereby a project (or projects) in Jira could be mapped to project node locations in V1. Perhaps such a setting could be contained in the DefectWriterService section of the config file
Something along the lines of:
<DefectWriterService>
…
…
…
<settings>
…
…
…
<jiraProject name=”Project1”>
<mapsToV1Project>V1_Project_1</mapsToV1Project >
</jiraProject>
<jiraProject name=”Project2”>
<mapsToV1Project>V1_Project_2</mapsToV1Project >
</jiraProject>
</settings>
</DefectWriterService>
by: Colin O. | over a year ago | Integration
Comments
The JIRA integration has been enhanced to support mapping Projects and Priority values between VersionOne and JIRA. Project mapping allows user to configure where defects are created in VersionOne based on JIRA project names. Priority mapping allows users to configure how JIRA priority values relate to VersionOne priority values.
For more information about this and other new features, please see the release notes:
http://community.versionone.com/Release%20Notes/ReleaseNotes2011Winter.aspx