JIRA project management and time tracking plug-ins - Ceptah

Get help with linking your JIRA to Microsoft Project

Please try to find answer using the below resources. If you still have a question, please get in touch with us by clicking the Support button at the bottom of the page or emailing directly at support@ceptah.com. Our office hours are from 9am to 6pm Sydney time, Monday to Friday. We will reply to you within 8 hours.

Release notes: version 3.0

New Features

  1. Running user-defined macros (VBA subs) at different stages of synchronisation and import.

  2. Ranking issues (in JIRA Agile).

  3. Synchronisation of the Created and Updated fields.

  4. An option to preserve time tracking data in MS Project up to a particular day. The feature is useful if there are already some actual hours and you do not want them to be erased during synchronisation.

  5. The ability to skip first n parents from the top when composing an issue name based on the path to the task.


  1. Support for the Rank field (read-only) in the Custom Field Mappings.

  2. The ability to leave the password field blank in the connection settings, in which case the password is not stored anywhere and the user is prompted to enter it whenever required.

  3. The ability to subtract the Work of the nested tasks from the Work of the published task when creating an issue.

  4. Optional Priority mapping.

  5. Sorting changes in the main synchronisation window by various columns.

  6. When the main synchronisation window is closed and then re-opened, its last size and position is restored.

  7. An option to always use basic authentication when connecting to JIRA. By default, Ceptah Bridge uses cookies authentication.

  8. Support for the CA Site Minder Proxy Server.

Bugs fixed

  1. A workaround for a JIRA defect - it may return sub-tasks in an invalid order, which resulted in the wrong order of imported sub-tasks.

  2. Ignore skipped parent tasks when synchronising issue links.

  3. The "Close Issues" feature produced an error when it was used with JIRA 5 if the issue being closed had Due Date specified.

  4. Error when opening Project Settings if the user did not have permissions to get the list of all agile boards.

  5. An unfriendly error message when creating a sub-task issue based on a task that had a parent that was marked with SKIP.

  6. An error when creating issue if the Time Tracking field was mandatory in JIRA and the task Work was 0.

  7. Support for custom JIRA fields that have round brackets in their name.