Integration - Plugins
The integration plugins page allows to configure specifically the plugins with the Initiative/Release.
It contains 2 lists:
- The list of registered plugins: if the plugin is started, it's possible to update the configuration by clicking on “Configure”
- The list of available but not registered plugins: it's possible to register the plugin by clicking on “Activate”
The next sections explain the integration for each existing plugin with the Initiative/Release.
The plugins
The Redmine plugin
The Redmine plugin and its configuration are explained in the the administrator's guide.
The integration with the Initiative/Release covers the following capabilities:
- Create a Redmine's project with the Initiative/Release data
- Attach one or many Redmine's projects to the Initiative/Release
- Load the Redmine's issues of a project as Requirements of the Initiative/Release
- Load the Redmine's versions of a project as Iterations of the Initiative (not available for Release)
- Keep the relations between Requirements and Iterations
Attributes mapping for Requirements
Requirement (BizDock) | Issue (Redmine) |
---|---|
Defect | Depends of the Issue's tracker, see the Redmine plugin configuration for more details |
External ref ID | ID |
Name | Subject |
Description | Description |
Category | Category |
Status | Status according to the status mapping, see the Redmine plugin configuration for more details |
Priority | Priority according to the priority mapping, see the Redmine plugin configuration for more details |
Severity | Priority according to the severity mapping, see the Redmine plugin configuration for more details |
Author | Author |
Story points | Custom field, see the Redmine plugin configuration for more details |
Estimation | Estimated time |
Effort made | Sum of time entries attached to the Redmine issue |
Remaining effort | Custom field, see the Redmine plugin configuration for more details |
Iteration | Target version |
In scope | Custom field, see the Redmine plugin configuration for more details |
Release | Manually settled from BizDock |
Attributes mapping for Iterations
Iteration (BizDock) | Version (Redmine) |
---|---|
Name | Name |
Description | Description |
Closed | Status: if “open” or “locked” then false, if “closed” then true |
Story points | Manually settled from BizDock |
Start date | Not settled |
End date | Date |
Source | Computed with the pattern “Redmine - {redmineProjectName}”, for example “Redmine - CRM upgrade” |
Release | Manually settled from BizDock |
Activate the plugin
To activate the Redmine plugin with the Initiative/Release, click on the “Activate” button in the Redmine panel under “Available plugins”:
Then 2 options are proposed:
- Create a new project in Redmine: A new Redmine's project is automatically created with the name and the description of Initiative/Release, and is attached to it.
- Select an existing project from Redmine: A new page is displayed with the available Redmine's projects. The user should select one and confirm: The selected Project is attached to the Initiative/Release.
Configure the plugin
To configure the Redmine plugin with the Initiative/Release, click on the “Configure” button in the Redmine panel under “Registered plugins”:
It's not possible to configure a not started plugin.
The Redmine configuration page is composed by 4 areas:
- Plugin details: general information about the plugin
- Administration: list of actions that can be called
- Configuration: list of parameters that could be parametrized for the Initiative/Release
- Related Redmine projects: list of attached Redmine's projects
Administration
- Trigger the load: a new task is started to load the corresponding issues and versions from Redmine in order to create or update Requirements and Iterations of the Initiative/Release.
- Unregister the plugin: remove the registration with the Initiative/Release of the plugin
By unregistering the plugin, all Requirements and Iterations that has been created thanks it will be removed.
Configuration
- Iterations: if checked then the Redmine's versions are synchronized
- Needs: if checked then the Redmine's issues with a need's tracker are synchronized
- Defects: if checked then the Redmine's issues with a defect's tracker are synchronized
Related Redmine projects
The panel contains the list of attached Redmine's projects.
To attach a new project, click on the icon
To remove a project, click on the icon
By removing a project, all Requirements and Iterations that have been created thanks it will be removed.
The Jira plugin
The Jira plugin and its configuration are explained in the the administrator's guide.
The integration with the Initiative/Release covers the following capabilities:
- Create a Jira's project with the Initiative/Release data
- Attach one or many Jira's projects to the Initiative/Release
- Load the Jira's issues of a project as Requirements of the Initiative/Release
Attributes mapping for Requirements
Requirement (BizDock) | Issue (Jira) |
---|---|
Defect | Depends of the Issue's type, see the Jira plugin configuration for more details |
External ref ID | ID |
Name | Summary |
Description | Description |
Category | Should be manually mapped in the BizDock plugin of Jira, see the Jira plugin configuration for more details |
Status | Status according to the status mapping, see the Redmine plugin configuration for more details |
Priority | Priority according to the priority mapping, see the Redmine plugin configuration for more details |
Severity | Should be manually mapped in the BizDock plugin of Jira, and depends of the severity mapping, see the Redmine plugin configuration for more details |
Author | Creator, this attribute could be mapped to another Jira attribute thanks the BizDock plugin of Jira, see the Redmine plugin configuration for more details |
Story points | Should be manually mapped in the BizDock plugin of Jira, see the Jira plugin configuration for more details |
Estimation | Original Estimate, this attribute could be mapped to another Jira attribute thanks the BizDock plugin of Jira, see the Redmine plugin configuration for more details |
Iteration | Not mapped |
In scope | Should be manually mapped in the BizDock plugin of Jira, see the Jira plugin configuration for more details |
Release | Manually settled from BizDock |
Activate the plugin
To activate the Jira plugin with the Initiative/Release, click on the “Activate” button in the Jira panel under “Available plugins”:
Then 2 options are proposed:
- Create a new project in Jira: A new Jira's project is automatically created with the name and the description of the Initiative/Release, and is attached to it.
- Select an existing project from Jira: A new page is displayed with the available Jira's projects. The user should select one and confirm: The selected Project is attached to the Initiative/Release.
Configure the plugin
To configure the Jira plugin with the Initiative/Release, click on the “Configure” button in the Jira panel under “Registered plugins”:
It's not possible to configure a not started plugin.
The Jira configuration page is composed by 4 areas:
- Plugin details: general information about the plugin
- Administration: list of actions that can be called
- Configuration: list of parameters that could be parametrized for the Initiative/Release
- Related Jira projects: list of attached Jira's projects
Administration
- Trigger the load: a new task is started to load the corresponding issues from Jira in order to create or update Requirements of the Initiative/Release.
- Unregister the plugin: remove the registration with the Initiative/Release of the plugin
By unregistering the plugin, all Requirements that has been created thanks it will be removed.
Configuration
- Needs: if checked then the Jira's issues with a need's type are synchronized
- Defects: if checked then the Jira's issues with a defect's type are synchronized
Related Jira projects
The panel contains the list of attached Jira's projects.
To attach a new project, click on the icon
To remove a project, click on the icon
By removing a project, all Requirements that have been created thanks it will be removed.