Settings
The "Settings" tab of the configuration dialog allows you to setup some general configuration settings for The Connector.
Remember Last Login – This option will remember the username you specify between logins so you will not have to retype it.
Populate Microsoft Project Task Hyperlink field with the JIRA issue link – This option will put a link in the task hyperlink field. This allows a quick single click link into JIRA to view the issue.
Cache the project list in memory for faster project browsing – After the first request to JIRA to retrieve the project list is made, it is cached in memory by The Connector as used for subsequent requests. This greatly increases the speed at which the project list is displayed.
NOTE: If you project lists changes frequently, you may not want to use this function. Typically the project list you work with does not change that frequently and the data is only cached until Microsoft Project is restarted.
Use JIRA Components and Versions – If this option is enabled, you will see the components and versions tab on the issue editor and the import and sync functionality of The Connector will include these values.
Use JIRA Environment Field – If this option is enabled, you will see the environment tab on the issue editor and the import and sync functionality of The Connector will include these values.
Use JIRA Slave Project / Issue – The slave project / issue functionality of The Connector allows a single Microsoft Project task to be attached to two JIRA issues in two separate projects. This allows single updating of two sets of data during the synchronization option.
Use JIRA Custom Fields – This option enables the ability for The Connector to exchange custom field data with JIRA. When this option is available, a Custom Fields tab is available on the issue editor for setting values to be exchanged.
NOTE: This option requires the installation of the extended web services.
Resource Mappings – Resource mappings will allow you to use a mapping of your resource name to the JIRA username. You can store the JIRA username in a custom field of the resource. This allows you to have different resource names between JIRA and Microsoft Project.
The Resource Mapping lets you configure the JIRA user ID in either a custom field or using the Windows User Account.
NOTE: This option is only available in the Professional version of Microsoft Project.
Example: You may want your resource to be called “Bill Smith” in Microsoft Project, but Bill has a JIRA user login as “bsmith”. Using the mapping functionality of The Connector will allow for this support.
When Automatically Creating Resources – This option will control how The Connector creates new resources when you import issues into Microsoft Project. There are three options that can be set:
- Never create a resource entry automatically
If this option is checked, new resources will never be added to your resource list in Microsoft Project. If the resource exists and the option during the import is to assign the task, the resource will be set. Otherwise it is ignored.
- Populate Resource Name with JIRA username
If doing an import and the resource does not exist, a new resource is automatically added and the resource name is assigned the JIRA user name.
- Populate Resource Name with JIRA full name
If doing an import and the resource does not exist, the new resource is automatically added and the resource name is assigned the Full Name of the resource which gets pulled from JIRA. The JIRA username is stored in the field that is configured in the Resource Mapping section.
NOTE: This option is only available if you are using the Resource Mapping option.