Unhandled exception message in MS Project for some Jira configurations when connection fails.
Web Login option supports Jira configurations with a custom SSO where REST API returns the login page with status 200 for unauthenticated calls instead of 401.
Error in synchronising Tempo worklogs.
Only first 50 Tempo Accounts and Teams were displayed in the dropdowns.
Changed to the Tempo API Version 4. Version 3, which was used by the previous Ceptah Bridge releases, is no longer supported by Tempo.
Added support for importing Team field from JIRA Cloud. This is a new field different to the team custom field used in Advanced Roadmaps (com.atlassian.teams:rm-teams-custom-field-team).
Added support for response compression when calling REST API.
Better handling of the situation when the saved password or API token is inaccessible for the current user.
Synchronisation can be restarted throug the API from within the "Import Run: After Apply" and "Sync Run: After Apply" event handlers.
Added support for Personal Access Tokens for JIRA Server / DC.
All passwords are encrypted in such a way that they can only be accessed by the Windows user who saved them. The passwords saved by the older versions can still be retrieved.
Improved support for the Team field in JIRA DC prior to 8.22.
Addressed breaking changes in JIRA API for JIRA DC 8.22 in relation to the Team field.
More descriptiove messages for HTTP errors 401 and 403.
Addressed breaking changes in JIRA API for JIRA DC 9.0 in relation to Security Levels.
Pass null to SynchroniseSilent API method as a value for the 'indexes' parameter.
Crash when Reporter field was blank.
OAuth authentication for JIRA Server.
Addressed the "Oops, something went wrong." problem with the Web Login caused by changes in JIRA Cloud.
Added support for some Tempo versions for JIRA Server. Previous Ceptah Bridge versions could display the "Can not convert Object to String." error.
Ceptah Bridge activation works when The Federal Information Processing Standard (FIPS) compliance is enforced on the computer.
Addressed breaking Changes in JIRA DC 9.0+. The 'Issue Does Not Exist' was returned when creating issues in JIRA DC 9.0 or higher.
'The given key was not present in the dictionary' error could be generated when projects were mapped by name.
Problem with synchronising the Prtfolio / Advanced Roadmaps Parent Link field.
Parent field mapping. The Parrent field replaces Epic Link and Parent Link fields in JIRA Cloud in May 2022. The mapping can also be used instead of the Sub-task mapping.
The ability to map multiple JIRA link types to a single predecessor type in MS Project. This works only if the direction of synchronisation is from JIRA to MS Project.
The ability to escape the "/" symbol in the value of a cascade select field. To escape the character, prefix it with "\". In other words, you need to replace / with \/. To enter \ itself use \\. If you have Cascading Items A/B -> C/D, the value in MS Project should be A\/B/C\/D, which is "A\/B" + "/" + "C\/D".
Supporting the Project field for tasks in MS Project.
Updating Task Usage could cause an error message under some circumstances.
The History Mapping did not work correctly in some cases because it relied on the history events being returned from JIRA in a particular order. The JIRA API implementation changed at some point and started returning records in a random order. Now Ceptah Bridge does not rely on JIRA to sort the history entries.
Full support for the Parent Link field, which works similar to the Epic Link mapping. The Parent Link field is used by Advanced Roadmaps (Portfolio) for organising issues in a hierarchy in the Plans view.
An option for suppressing e-mail notifications when updating issues. The option can be overridden from the Main Window.
New API methods for silently importing and synchronising issues.
Improved synchronisation performance by loading issues from JIRA in batches.
Support for Service Desk Organisations custom field.
A workaround for JIRA bug that causes duplication of system custom fields after version upgrades.
Improved rounding for Work and Actual Work.
Support for the Option custom fields.
Support for mapping Statuses to %complete when there are multiple statuses with the same name coming from the Next Gen projects.
Possible crash when cancelling synchronisation.
Epic Link can be mapped to a parent task on a particular level in the hierarchy. That allows linking to issues that are not immediate parents of the task.
Epic Link can be mapped to the first parent task up in the hierarchy that satisfies an issue type filter, e.g. an Epic. That allows linking to issues that are not immediate parents of the task.
Issue Links can be mapped to a parent task on a particular level in the hierarchy. That allows linking to issues that are not immediate parents of the task.
Issue Links can be mapped to the first parent task up in the hierarchy that satisfies an issue type filter, e.g. a Story. That allows linking to issues that are not immediate parents of the task.
Tempo worklogs can be imported instead of the native JIRA worklogs.
Billable time from Tempo worklogs can be imported instead of the native JIRA worklogs.
Wrong sprint is picked as the last sprint when multiple sprints are associated with an issue in JIRA Cloud.
Errors in the sprint field synchronisation.
Supporting Epic Link mapping for NexGen projects.
Supporting duplicated issue type names for NextGen projects without adding ids in brackets. Now Ceptah Bridge selects the issue type based on the destination NextGen project if the ID is not provided. The <Issue Type>(<id>) format is supported as well.
Supporting new Sprint field format in REST API. After breaking changes in JIRA REST API previous Ceptah Bridge versions became incompatible, and the Sprint mapping stopped working for JIRA Cloud.
Supporting JQL queries and issue key lists of an unlimietd length when importing issues. They were not saved properly when exceeded 256 symbols.
Shorter text of the request and reply in the offline activation. The text is now short enough to be entered by hand when copying and pasting to and from the activation screen on the website is not possible.
Error while synchronising sprints when the text of a sprint goal had multiple lines.
Error when square brackets are used in a sprint name.
Support for GDPR changes in JIRA Cloud for the Watchers mapping.
API token in Connection Settings for connecting to Tempo Cloud.
Error when updating the Parent Link field in JIRA Server.
When using HTTP instead of HTTPS in JIRA URL, the Connection test would succeed while the connection was not working.
Added links to documentation in the Connection Form.
"The username query parameter was not provided" error when updating Assignee in JIRA Server.
Mapping for Issue ID.
An option to import only the first level of linked issues or sub-tasks.
Error when synchronising Worklogs on user-by-user basis if the users are mapped by Username in JIRA Server.
Logging in through JIRA UI. This authentication method can be used when JIRA is configured to use SSO (Single Sign-On).
An option to prevent the synchronisation of Assignee for summary tasks.
The ability to synchronise predecessors of different types (FS/FF/SS/SF) individually.
A single installer for both 32 and 64 bit MS Project.
Mapping JIRA Assignee to MS Project resources by name, e-mail and Cloud Account Id in addition to username, which is being removed from JIRA Cloud by Atlassian.
Mapping JIRA WorkLog authors to MS Project resources by name, e-mail and Cloud Account Id in addition to username, which is being removed from JIRA Cloud by Atlassian.
Mapping JIRA Reporter name, e-mail and Cloud Account Id to a task field in MS Project.
Copying user name, e-mail and Cloud Account Id into resource fields when importing users.
Saved import parameters were discarded after updating Project Settings.
Updating Issue Security Level in JIRA did not work properly.
Added support for Portfolio Parent Link when synchronising Custom Fields.
A new method in the API to get global connection settings.
Always use Basic Authentication for JIRA Cloud as the cookies authentication was removed.
Digitally signed add-in.
Old values for updated epic links where not displayed.
Allowed to change dependency type regardless of the direction as it matters during import even if the direction is from MS Project to JIRA.
Invalid tooltip for the Priority field.
Support for duplicated issue type names. Now this can happen in JIRA if the Agility Project template was used. The duplicated issue types should have their name in the following format: 'Story (7)', where Story is the name and 7 is the issue type ID. The issue type names can be viewed in the Default Project dropdown in the Project Settings.
On rare occasions, Ceptah Bridge could identify the wrong sprint as current.
Comments Synchronisation.
Watchers Synchronisation.
Password protection for project settings (this is only for preventing accidental changes in the mappings; an experienced MS Project user will still be able to remove the password).
Synchronisation of the Tempo Team attributes.
An option to insert sub-tasks after parent tasks during import without making them children in MS Project.
Escape the "[", "]" and list separator characters in user names when importing resources.
Ignore duplicated link types if they are not used in mappings (this was generating an error before).
The command-line utility mspjb.exe exits with a non-zero code if there was an error during execution.
Link, Sub-task or Epic Link synchronisation could fail if some parent tasks were collapsed.
Support for JIRA 5 and older has been discontinued. Please use Ceptah Bridge 3.5.8 for these versions of JIRA.
Two rounds of synchronisation were required when Status was mapped to both %complete and an additional field.
More informative error message when the user cannot create issues in the project.
Empty remaining estimates were ignored when copying data from JIRA to MS Project.
Complain about duplicated issue type names only when the types are actually being used.
Handle the changed format of the Tempo Account and Team fields.
Potential problems with importing issues on some systems.
Status transition date synchronisation. Ceptah Bridge finds a particular transition based on a filter and synchronises it with an MS Project field. For instance, a date when issue went into the In Progress state can be copied to Actual Start.
Support for Tempo Account fields.
Synchronisation of the Description, Start Date, Release Date and Released Flag attributes for Fix Version.
Importing linked tasks even if they are not covered by the import condition.
API for controlling Ceptah Bridge from VBA or another programming environment.
Synchronisation of the name path back to MS Project.
Increased JIRA API access timeout.
Fixed problems with synchronising Tempo Account custom field.
Do not scroll to top after finishing comparing issues with tasks.
The ability to synchronise Issue Status with %complete and a filed at the same time.
The option to specify the MS Project dependency type for predecessors in the Link Mapping (SF, SS, FS or FF).
The ability to apply changes only to JIRA or only to MS Project.
Select the last focused task or the next available task after re-comparing in the Main Window.
The Remaining Work and Duration fields were removed from the drop-down list in the Remaining Estimate mapping section to avoid confusion (see http://www.ceptah.com/Bridge/FAQ/FAQ.aspx#time-tracking). The fields can still be mapped by manually entering their name in the box.
Allow duplicated Tempo Account names. There still will be an error if the ambiguous name is used during synchronisation.
Deny updating the Scheduled Start, Scheduled Finish and Scheduled Duration read-only fields on the mappings level.
When a read-only field was updated in MS Project or the new value had an invalid value, the error message could be hidden by another error message.
The synchronisation outcome statistics were not displayed at the bottom of the synchronisation window.
Fixed tooltip for the Populate Epic Name check box.
Digitally signed installer.
An error message when opening Project Settings or synchronising if Visual Basic for Applications is not installed.
Proxy server parameters can be specified when running the command-line utility mspjb.exe.
Deactivation through the command-line utility mspjb.exe.
Measure ActualDuration, BaselineDuration, BaselineXXDuration, DurationXX, DurationVariance, EnterpriseDurationXX, EnterpriseProjectDurationXX, RemainingDuration, and ScheduledDuration in hours when synchronising.
Do not subtract children's work for inactive tasks.
MS Project would not start after a Windows Update when Ceptah Bridge is installed.
Importing all users from a selected group or all users who have access to a particular project.
The name of the last file the mappings were loaded from is displayed at the top of the Project Settings window.
An option to ignore work log entries after the project Status Date.
A command to toggle direction for all mappings at the same time (under the Advanced button in the menu of the mappings window).
An option to ignore and preserve assignments for non-work (cost and material) resources.
Ignore " [x]" at the end of user name (added automatically in JIRA for inactive users).
In the synchronisation window, the "Issue changes" and "Task changes" columns are renamed to "JIRA" and "MS Project" respectively.
Compare time with 1 min tolerance because that is the accuracy of time values in MS Project. Otherwise, Ceptah Bridge was identifying differences in time field values that could not be synchronised.
"Time estimate" field name was changed to "Remaining Estimate" in the changes preview.
Fixed some memory leaks.
Occasional "There is already a request in progress" error.
Ignore the order of values in the list fields, e.g. labels.
Ignore 'External' tasks.
Load filters on demand in the Import Dialog Box.
The main window would have an invalid position when reopening MS Project after it has been closed with the main window minimised.
'Object reference not set to an instance of an object' error when applying changes one by one.
The ability to provide JIRA user name and password as parameters to the command-line utility (mspjb.exe).
The SyncTaskBeforePrepare event was not raised.
Error if the priority mapping was off and the disabled priority direction was from JIRA to MS Project.
Possible crash in mspjb.exe with project server 2003.
Occasional RPC_E_SERVERCALL_RETRYLATER error when synchronising for the first time after starting MS Project.
Running user-defined macros (VBA subs) at different stages of synchronisation and import.
Ranking issues (in JIRA Agile).
Synchronisation of the Created and Updated fields.
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.
The ability to skip first n parents from the top when composing an issue name based on the path to the task.
Support for the Rank field (read-only) in the Custom Field Mappings.
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.
The ability to subtract the Work of the nested tasks from the Work of the published task when creating an issue.
Optional Priority mapping.
Sorting changes in the main synchronisation window by various columns.
When the main synchronisation window is closed and then re-opened, its last size and position is restored.
An option to always use basic authentication when connecting to JIRA. By default, Ceptah Bridge uses cookies authentication.
Support for the CA Site Minder Proxy Server.
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.
Ignore skipped parent tasks when synchronising issue links.
The "Close Issues" feature produced an error when it was used with JIRA 5 if the issue being closed had Due Date specified.
Error when opening Project Settings if the user did not have permissions to get the list of all agile boards.
An unfriendly error message when creating a sub-task issue based on a task that had a parent that was marked with SKIP.
An error when creating issue if the Time Tracking field was mandatory in JIRA and the task Work was 0.
Support for custom JIRA fields that have round brackets in their name.
Sprint field synchronisation. Sprint Name, Start, End and Completion dates as well as State can be mapped to MS Project fields.
Support for Tempo Account and Team fields. The fields can be mapped using the custom field mappings.
Resolution Date mapping (JIRA 6+).
Map JIRA project by name (in addition to mapping by key).
If there is a mapping for a status to %complete=100%, that mapping overrides the Actual Work mapping and Actual Work is not updated for the issues that have that status. Using that combination of mappings you can track progress by updating Actual Work based on Time Spent (which automatically updates %complete as well) while keeping %complete=100% for closed issues regardless of their Time Spent.
'Preserve %complete' option in the Remaining Estimate mapping. Changing Work or Duration may change %complete in MS Project. Turing the option on ensures that the %complete value is preserved when Work, Duration or any other field is updated by the Remaining estimate mapping.
'Update closed issues' option on the 'Options' tab page of the Project Settings. If the option is on, Ceptah Bridge will update closed issues. If the option is off, closed issues are not updated even if they are out of sync because they are read-only in JIRA by default.
If there is a problem with updating a particular MS Project field, Ceptah Bridge adds a waring to the synchronisation results and continues synchronisation.
The 'Finish' task field can be updated for manual summary tasks. Ceptah Bridge still does not try to update this field for automatically scheduled summary tasks as in that case it is read-only in MS Project.
Logging improvements.
More verbose mspjb.exe output.
Order projects in the drop-down list by key.
Added the User Agent header to requests when reading issue XML (JIRA 5-) and performing rest calls.
A waring is displayed during link synchronisation if a parent or dependant issue is not published in JIRA. The previous version generated an error and stopped synchronisation for the issue.
MS Project could be left running in background if there was an error during synchronisation using the command-line tool (mspjb.exe).
Ceptah Bridge resorted to SOAP in case of any errors, which could mask the original error. Now it only uses SOAP if it could not connect using REST.
Use Units=100% when importing time scale data from JIRA on resorce by resource basis. It used to be Units=0, which could result in incorrect task allocation.
Direction had no effect and was always from MS Project to JIRA when Epic Link was mapped to a field.
Use basic authentication instead of putting credentials in URL when retrieving issue XML (JIRA 5-).
/J command-line option documented.
Support TLS 1.1 and 1.2.
Error when Fix Versions, Affects Versions or Components field is mapped and the field is hidden for an issue by the assigned field configuration.
"Null Reference Exception" error when synchronising a project created with a previous version of Ceptah Bridge that has issue links mapped to parent in MS Project.
Issue Type filters were not disabled for the link and epic link mappings when the linking mode was not 'Parent'.
An error during activation if installed over an older version.
New sub-task mapping, that can be applied to particular issue types.
New epic Link mapping, that can be applied to particular issue types and task outline levels.
The ability to set Epic Name for Epics to the Summary value.
The ability to apply issue link mappings to particular issue types and task outline levels.
The option to delete tasks that are linked to issues that do not longer exist.
Offline activation.
Activation using the command-line tool.
The ability to synchronise Project Server projects using the command-line tool. The project name should be formatted as '<>\project name'.
Some fields could not be synchronised in JIRA 5 or earlier when connecting through a proxy server.
"Method not found: 'System.Object Newtonsoft.Json.Linq.Jtoken.ToObject(System.Type)'" error on some systems.
Ceptah Bridge could crash MS Project under some circumstances.
Error when trying to clear the Affects Versions, Fix Versions or Components fields in JIRA.
Ceptah Bridge would always fall back to the SOAP Api when connected to JIRA through a proxy server.
Renaming custom fields based on the mappings. The feature is controlled by an option in the project settings. If the option is on, the fields are renamed whenever project settings are saved. Also, renaming can be initiated from the menu.
Adding all mapped fields to the current task view. The feature is controlled by an option in the project settings. If the option is on, the missing fields are added whenever project settings are saved. Also, fields can be added from the menu.
A new time-tracking option that controls whether Time Spent should be added to Remaining Estimate during synchronisation when the direction is from JIRA to MS Project.
A new time-tracking option that controls whether Actual Work should be subtracted from Work during synchronisation when the direction is from MS Project to JIRA.
Worklogs can be imported for JIRA users that do not exist anymore when resources are mapped to JIRA users using a resource custom text field. Ceptah Bridge creates a resource for each deleted user.
Import issues filtered with a JQL query.
Logging of changes applied during synchronisation. The information is written into the My Documents\Ceptah Bridge\Logs\Sync.log file.
The ability to update Original Estimate in JIRA (for JIRA 6 and higher).
The ability to synchronise only existing issues without creating new ones (ignoring unlinked tasks during synchronisation).
A new log files location (My Documents\Ceptah Bridge\Logs). The log files folder can be opened from the Ceptah Bridge menu.
An error when pasting individual segments of the serial key during activation.
Variations in the line ending formats were not ignored when comparing multiline text fields from JIRA and MS Project.
The 'Object reference is not set to an instance of an object.' exception when synchronising with JIRA 5- and a field type is not selected for a custom JIRA field. The new version displays a sensible error message.
The ability to update parent (move task) in MS Project when applying a link mapping with the 'Parent' mode on the MS Project side.
Error when importing from JIRA 6 with the Worklog mapping enabled.
Error when synchronising DateTime custom JIRA field (in JIRA 6).
The ability to connect to JIRA through a proxy server.
Incorrect handling of the Epic Link custom field for JIRA 6+. There is still a problem with this field - the link cannot be removed (set to a blank value) during synchronisation. We are currently trying to raise the issue with Atlassian.
The "Accept remote API calls" option was still required for the "Close Resolved issues" function to work with JIRA 6+.
"The type initializer for 'java.util.Locale' threw an exception." error on some systems. The problem is fixed for JIRA 6 and higher. It may still happen when working with JIRA 5 and earlier.
If you are experiencing the issue and you are running MS Project 32 bit on Windows 64 bit, please
copy the following files from the "C:\Program Files (x86)\Ceptah\Msp Jira Bridge" folder into the
C:\Windows\SysWOW64 folder:
vjsnativ.dll
vjsvwaux.dll.
For all other configurations, if you are experiencing the issue, please copy the above files from the "C:\Program Files\Ceptah\Msp Jira Bridge" folder into the C:\Windows\System32 folder.
As of this version, Ceptah Bridge requires the .NET Framework 3.5.
The first row in the list of changes cannot be selected/unselected by clicking the checkbox in the row.
Work around: use the context menu to check/uncheck the check box.If the date format in the connection settings has invalid syntax, the 'Dll not found' or 'Resource dll could not be loaded' error is shown.
Work around: Read the message as 'The date format specified is invalid'.The first row in the list of changes cannot be selected/unselected by clicking the checkbox in the row.
Work around: use the context menu to check/uncheck the check box.If the date format in the connection settings has invalid syntax, the 'Dll not found' or 'Resource dll could not be loaded' error is shown.
Work around: Read the message as 'The date format specified is invalid'.The first row in the list of changes cannot be selected/unselected by clicking the checkbox in the row.
Work around: use the context menu to check/uncheck the check box.If the date format in the connection settings has invalid syntax, the 'Dll not found' error is shown.
Work around: Read the message as 'The date format specified is invalid'.The first row in the list of changes cannot be selected/unselected by clicking the checkbox in the row.
Work around: use the context menu to check/uncheck the check box.If the date format in the connection settings has invalid syntax, the 'Dll not found' error is shown.
Work around: Read the message as 'The date format specified is invalid'.The first row in the list of changes cannot be selected/unselected by clicking the checkbox in the row.
Work around: use the context menu to check/uncheck the check box.If the date format in the connection settings has invalid syntax, the 'Dll not found' error is shown.
Work around: Read the message as 'The date format specified is invalid'.The first row in the list of changes cannot be selected/unselected by clicking the checkbox in the row.
Work around: use the context menu to check/uncheck the check box.If the date format in the connection settings has invalid syntax, the 'Dll not found' error is shown.
Work around: Read the message as 'The date format specified is invalid'.If you are using a version of the software earlier than 1.2.19, after installing the version 1.2.21 your general settings and licence key information will not be saved. Please reenter your general settings and licence key.