Ceptah Bridge FAQ
Installation and connection
'JIRA' is missing from the ribbon (or from the menu for Project 2007 or earlier)
In 99.99% of cases this is because the bitness of your MS Project is different from the bitness of the installed Ceptah Bridge package.
If you are using MS Project 2000, 2003, 2007 or the 32-bit version of 2010, 2013 or 2016, the 32-bit package needs to be installed
even if the Windows is 64 bit. For MS Project 2010-2016 64 bit, use the 64-bit installer. No matter how confident you are that you are
running the correct version, please go to FILE > Account > About Project and double-check. It will be right at the top.
If the bitness does not match, uninstall the product and install it using the right installer.
Make sure that you uninstalled the other package before installing the correct one because failing to do so may create issues as well.
The full list of possible causes of the problem can be found here.
Error 401 (Unauthorized)
This is because your login or password is incorrect. Please check the user name, re-enter the password and try again. Be mindful of the following:
JIRA Cloud allows logging in with the user's e-mail, but that does not work for the JIRA API that is utilised by Ceptah Bridge. Do not
use your e-mail to configure Ceptah Bridge - enter your JIRA login instead.
There are the global and the project-level settings, which override the global ones, if provided.
Make sure that you are testing the settings in effect.
Error 403 (Forbidden)
The most common cause of this error is a locked JIRA account. It gets locked after a few attempts to log in with invalid credentials.
To resolve the issue, do the following:
Open the effective connection settings, check the login and re-enter the password. You need to fix the password before unlocking the account.
If you try to open the project settings while the password is invalid, the account will be locked again because Ceptah Bridge will try to access JIRA
with the wrong credentials.
Log in to JIRA through the web UI in the browser. If you are logged in, log out and log in again. If JIRA has added the CAPTCHA test to the regular log-in screen,
that means that the account is locked. After you have logged in, the account will be unlocked.
Test the connection in Ceptah Bridge and save the settings.
"There is more than one issue type..." error
In your JIRA, there are two issue types with the name stated in the error message. One of them may be a sub-task, and the other one may be a regular issue.
JIRA does not permit such duplication, but it seems that either older JIRA versions or some 3-rd party plug-ins allow this to happen. The latter
assumption is supported by the observation that in majority of cases the duplicated name is 'test'.
To fix the issue, please rename one of the issue types so that they have different names. This is a good idea even irrespective of Ceptah Bridge because
having two different things with the same name may be quite confusing.
How to create sub-tasks in JIRA
To create subtasks, you will need to map JIRA Issue Type to an MS Project text field (e.g. Text12) and then populate the field with a subtask issue
type (e.g. 'Sub-Task') for the MS Project tasks that should produce sub-tasks in JIRA. Please also make sure that the parent tasks of these tasks
are or will be associated with JIRA issues (e.g. will not be skipped during synchronisation) because the new sub-tasks will need a parent.
How to map JIRA users to MS Project resources without using their logins as resource names
Please review this tutorial.
How to make the Bridge skip some tasks during synchronisation
To skip a particular task, enter 'skip' in the field containing issue key (Text10 by default).
How to map MS Project Server Enterprise fields
The Enterprise Fields are supported, but they are not available in the drop-down lists.
Please enter the field names manually where required.
Notes on the Time Tracking mappings
The most (if not the only) sensible way of mapping Remaining Estimate to the MS Project *Work fields is either
depending on the desired direction of synchronisation. This is the default configuration in Ceptah Bridge.
Always consider how fields are related in MS Project. For example, mapping both Work and Finish with the direction from JIRA to MS Project
will not work properly because changing Work will change Finish and updating Finish resets Work. It is extremely unlikely that both mappings will produce
compatible results, thus one of the fields will always be out of sync. The solution here is to configure
one of the mappings to copy data from MS project to JIRA. This is a sensible thing to do because it will allow you utilising MS Project for what
it is good at - planning and scheduling. It will take effort from JIRA, schedule the activity and send back the Finish date. Alternatively,
you can import Due Date, calculate the effort required to arrive on it and publish the Remaining Estimate in JIRA.
It may appear logical to map Remaining Estimate to Remaining Work, but, in practice, that will not work because MS Project will automatically
reflect any Remaining Work changes in the total Work field, and the task will grow or shrink even if the total effort in JIRA has not changed.
Probably we should not have added the Remaining Work field to the dropdown box at all so that it would not confuse the users.
Mapping Original Estimate to Duration is not a good idea either. Firstly, because Original Estimate is original and is different
from the actual effort. But most importantly, because they have a different measure - the JIRA estimates are man-hours, whereas MS Project Duration
is just the number of working hours between Start and Finish. It is much better to update Work based on the values from JIRA and let
MS Project calculate Duration and Finish for you. As an option, then you may want to set Due Date in JIRA to Finish from MS Project to close the
A good fit for Original Estimate is Baseline Work.