Estimated time to finish: 7MD(confidence B).
The currently used GForge has a number of shortcomes we would like to improve on by moving to a more powerful issuetracker platform. The improvements include:
- Better search/filtering functionality: We need more powerful querying functionality to display the bugs/FR relvant foer a given contect
- Better listing view: We need to be able to define which bugs/FR attibutes we would like to display in the listing
- Better task management capabilities. We currently need to maintain a lot of task related information in this wiki. JIRA will be able to handle a lot of this.
- More powerful issue model: This includes: issue linking, sub issues, custom fields, time tracking, etc
- More powerful dynamic views: JIRA provides a much larger set of views to acces the issue model
- Rich Text Issue descriptions.
- Tool integrations: JIRA provides integration to Source code (through Fisheye), reviews (through Crucible), build server (Hudson).
- Integrations to JIRA: Fisheye, Crucible, Hudson, Eclipse, IDEA are all capable of integrating to JIRA.
- Newer Subversion version: Upgrade from 1.4 to newset 1.6 (1.7?)
- SSO with other SBForge apps: This includes SVN, Fisheye, Crucible and Hudson. May also in the long term include Confluence, Nexus and Sonar.
We are currently in the process of testing the SBForge prototype as replacement for GForge (TOOL-10 NetarchiveSuite migration). The current SBForge installations is only accessable from the SB and KB networks. The task involves:
Move NetarchieveSuite issues to SBForge JIRA
Move NetarchiveSuite mailing lists to SBForge
- Migrate svn repository to SBForge
- Move NAS-distributions to SBForge platform
The migration can not start before the SBForge platform has been put into production, which is planned to take place in december (see SBForge production installation)
The SBForge migration does not include migration of the wiki, but the task management information modellen in the wiki will be moved to JIRA.