| Q: |
Why does not the JIRA menu item appear in the menu? |
| A: |
If you use a Bridge version prior to 1.2.26, uninstall it, download the latest version and install it.
The earlier versions have compatibility issues with Microsoft.NET framework 4.0.
|
|
| Q: |
I start the synchronization, but nothing happens. |
| A: |
Most likely, you have not specified resources for the tasks in your project. By default,
such tasks are skipped during synchronization. The number of skipped tasks is displayed in
the left bottom corner of the synchronization window. To solve the problem, either specify
the resources or change the synchronization settings.
|
|
| Q: |
How to make the Bridge skip some tasks during synchronization? |
| A: |
To skip a particular task, enter 'skip' in the field containing issue key.
|
|
| Q: |
An issue should not have a security level (components, fix versions, affects versions),
but when it is created or synchronized, the field(s) is(are) set to the default value(s) specified
in the mappings instead. |
| A: |
To overwrite the default settings and to specify explicitly that an issue should have the above
fields empty, enter '(none)' in the respective columns.
|
|
| Q: |
Why am I receiving the error:
"com.atlassian.jira.rpc.exception.RemoteValidationException: {customfield_9999=FieldName is required.} : []"
when an issue is being created? |
| A: |
Most probably, that's because the custom field is defined as required in JIRA. The Bridge cannot create
issues in JIRA 4.3 and earlier if there are any mandatory custom fields defined for them. It is a limitation of the
previous versions of the JIRA Remote Application Programming Interface we are using.
To fix the problem, please upgrade to JIRA 4.4+ and Ceptah Bridge 1.2.33+ or avoid defining
mandatory custom fields for the issues you are going to synchronise if the upgrade is not possible.
|
|
| Q: |
After an issue has been imported from Jira, the duration of the issue is less than it should be
according to the common sense. For instance, the duration is 2 days, while the start is Monday and
the finish is Wednesday. You would expect the duration to be 3 days, not 2. |
| A: |
Most probably, your default working time settings in MS Project are different from the working
time in the calendar of your project or resource. For instance, it may be 9AM-6PM by default and 8AM-5PM
in the calendar. When a date field is populated, MS Project uses the default working time settings,
but when it calculates durations, it counts hours according to the settings in the
calendar. In fact, this issue does not relate to the Bridge in particular - it is a general MS Project
usage problem. To fix the situation, adjust the default settings (Menu: Tools/Options, Tab: Calendar,
Fields: Default start time, Default end time) or the calendar (Menu: Tools/Change Working Time).
|
|
| Q: |
How do I synchronise cascading select custom JIRA fields? |
| A: |
Unfortunately, the cascading select fields are supported with the following limitations.
The values of Cascading Select fields are represented in MS Project by the numeric identifiers
of the list items in JIRA. There is no way to find out the identifiers of particular items
using JIRA itself. To determine the identifiers you can map such a field to a custom
text task field, specify the direction to be from JIRA to MS Project,
populate the field in JIRA with different values for different preliminary linked issues and
synchronise the issues with their tasks. The values in MS Project will show the identifiers of the
list items. The field codes can be used to synchronise the field in both directions.
You can use the fields customisation in MS Project to specify formulas or icon mappings for the
field in order to present the values in a reasonable way.
|
|
| Q: |
Why do I receive an error similar to one of the following when synchronising date or time fields: |
|
com.atlassian.jira.rpc.exception.RemoteValidationException: Fields not valid for issue:
Errors: {duedate=You did not enter a valid date. Please enter the date in the format
"dd/MM/yy", eg. "04/06/10"}
or
Resource dll could not be loaded
or
Invalid JIRA date format
or
Invalid JIRA time format.
|
| A: |
This message means that the date or time format used by the JIRA server does not match the
one used by the Bridge. To fix the issue, please make sure that:
- The JIRA date picker and date time picker formats matches the formats specified in the Bridge connection
settings. The format strings can be found on the Administration/Look and Feel JIRA screen.
Do not include the text in the brackets in the format string (refer to the following screenshot).
- The language of the JIRA user whose account is used by the Bridge matches the language
specified in the Bridge connection settings. The setting makes difference if the date/time
formats use month names.
|
|
| Q: |
What if my MS Project resource names are different from the JIRA user names? |
| A: |
In this case you will need to use a custom resource text field to map resources to JIRA users.
- For the local resources stored in your project, simply switch to the resource sheet view (Menu: View/Resource Sheet). For enterprise resources, open them from the enterprise resource pool (Tools/Enterprise Options/Open Enterprise Resource Pool). The latter should open the resource sheet view as well.
- Right-click a column header and select ‘Insert Column’ in the context menu. A dialog will pop up.
- Select Text10 in the Field name combo box.
- You can also rename the column, but in the Bridge settings you should still use the original field name (e.g. Text10).
- Press OK, and a new column for Text10 will be added.
- Enter JIRA user names for your resources in the Text10 field:
Now you can use the Text10 resource field to associate your resources with JIRA users when mapping the assignee field or time tracking information.
The screenshot below shows how to map resources to JIRA users using a custom resource field instead of the resource name. If you use this type of mapping, your JIRA users and MS Project resources can be completely different.
The same approach can be used in the Time Tracking section for the work log mappings.
|
|
| Q: |
Why am I receiving the "There are more than one issue types with the name '???' in JIRA." error? |
| A: |
Most probably, there are two issue types named '???' defined in your JIRA. One of them should be a sub-task,
and the other one is a regular issue. Older JIRA versions allowed this to happen. If you are using JIRA 4.x,
most probably the issue types were created in JIRA 3.x, which was upgraded to JIRA 4.x later.
To fix the issue, please rename one of the issue types so that they have
different names. Please note that just using different casing won't be enough.
|
|
| Q: |
I've just installed Ceptah Bridge, but it did not appear in the MS Project menu. |
| A: |
Please make sure that the bitness of your MS Project matches the bitness of the Bridge package installed.
- If you are using MS Project 2010 64 bit, Ceptah Bridge 64 bit needs to be installed.
- If you are using MS Project 2000, 2002, 2003, 2007 or 2010 32 bit, Ceptah Bridge 32 bit needs to be installed.
If you have a wrong Bridge package installed, please uninstall it and install the right one.
|