Release Notes

2024

Release notes v.3.16.6 (06 Mar 2024)

New Features
  1. 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).

Improvements
  1. Added support for response compression when calling REST API.

Release notes v.3.16.3 (22 Jan 2024)

Bug fixes
  1. Better handling of the situation when the saved password or API token is inaccessible for the current user.

2023

Release notes v.3.16.2 (31 Oct 2023)

Improvements
  1. Synchronisation can be restarted throug the API from within the "Import Run: After Apply" and "Sync Run: After Apply" event handlers.

Release notes v.3.16 (9 Oct 2023)

Improvements
  1. Added support for Personal Access Tokens for JIRA Server / DC.

  2. 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.

Release notes v.3.15.10 (9 Aug 2023)

Improvements
  1. Improved support for the Team field in JIRA DC prior to 8.22.

  2. Addressed breaking changes in JIRA API for JIRA DC 8.22 in relation to the Team field.

  3. More descriptiove messages for HTTP errors 401 and 403.

  4. Addressed breaking changes in JIRA API for JIRA DC 9.0 in relation to Security Levels.

Bugs fixed
  1. Pass null to SynchroniseSilent API method as a value for the 'indexes' parameter.

  2. Crash when Reporter field was blank.

Release notes v.3.15 (24 Jan 2023)

Improvements
  1. OAuth authentication for JIRA Server.

  2. Addressed the "Oops, something went wrong." problem with the Web Login caused by changes in JIRA Cloud.

2022

Release notes v.3.14.8 (7 Oct 2022)

Improvements
  1. Added support for some Tempo versions for JIRA Server. Previous Ceptah Bridge versions could display the "Can not convert Object to String." error.

Release notes v.3.14.7 (28 Sep 2022)

Improvements
  1. Ceptah Bridge activation works when The Federal Information Processing Standard (FIPS) compliance is enforced on the computer.

Release notes v.3.14.6 (28 Jul 2022)

Improvements
  1. 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.

Bugs fixed
  1. 'The given key was not present in the dictionary' error could be generated when projects were mapped by name.

Release notes v.3.14.4 (1 Apr 2022)

Bugs fixed
  1. Problem with synchronising the Prtfolio / Advanced Roadmaps Parent Link field.

Release notes v.3.14 (25 Jan 2022)

New Features and Improvements
  1. 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.

Release notes v.3.13 (07 Jan 2022)

New Features and Improvements
  1. 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.

  2. 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".

  3. Supporting the Project field for tasks in MS Project.

Bugs Fixed
  1. Updating Task Usage could cause an error message under some circumstances.

  2. 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.

2021

Release notes v.3.12 (19 May 2021)

New Features and Improvements
  1. 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.

  2. An option for suppressing e-mail notifications when updating issues. The option can be overridden from the Main Window.

  3. New API methods for silently importing and synchronising issues.

  4. Improved synchronisation performance by loading issues from JIRA in batches.

  5. Support for Service Desk Organisations custom field.

  6. A workaround for JIRA bug that causes duplication of system custom fields after version upgrades.

  7. Improved rounding for Work and Actual Work.

  8. Support for the Option custom fields.

  9. Support for mapping Statuses to %complete when there are multiple statuses with the same name coming from the Next Gen projects.

Bugs Fixed
  1. Possible crash when cancelling synchronisation.

2020

Release notes v.3.11 (30 Sep 2020)

New Features
  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. Tempo worklogs can be imported instead of the native JIRA worklogs.

  6. Billable time from Tempo worklogs can be imported instead of the native JIRA worklogs.

Release notes v.3.10.2 (10 Sep 2020)

Bugs fixed
  1. Wrong sprint is picked as the last sprint when multiple sprints are associated with an issue in JIRA Cloud.

Release notes v.3.10.1 (7 Sep 2020)

Bugs fixed
  1. Errors in the sprint field synchronisation.

Release notes v.3.10 (3 Sep 2020)

Improvements
  1. Supporting Epic Link mapping for NexGen projects.

  2. 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.

  3. 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.

  4. Supporting JQL queries and issue key lists of an unlimietd length when importing issues. They were not saved properly when exceeded 256 symbols.

Release notes v.3.9.9 (11 Mar 2020)

Improvements
  1. 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.

Bug fixes
  1. Error while synchronising sprints when the text of a sprint goal had multiple lines.

2019

Release notes v.3.9.7 (11 Oct 2019)

Bug fixes
  1. Error when square brackets are used in a sprint name.

  2. Support for GDPR changes in JIRA Cloud for the Watchers mapping.

Improvements
  1. API token in Connection Settings for connecting to Tempo Cloud.

Release notes v.3.8.8 (28 May 2019)

Bug fixes
  1. Error when updating the Parent Link field in JIRA Server.

  2. When using HTTP instead of HTTPS in JIRA URL, the Connection test would succeed while the connection was not working.

Improvements
  1. Added links to documentation in the Connection Form.

Release notes v.3.8.5 (30 Apr 2019)

Bug fixes
  1. "The username query parameter was not provided" error when updating Assignee in JIRA Server.

Release notes v.3.8.4 (23 Apr 2019)

New Features
  1. Mapping for Issue ID.

  2. An option to import only the first level of linked issues or sub-tasks.

Bug fixes
  1. Error when synchronising Worklogs on user-by-user basis if the users are mapped by Username in JIRA Server.

Release notes v.3.8 (31 Mar 2019)

Bug fixes
New Features
  1. Logging in through JIRA UI. This authentication method can be used when JIRA is configured to use SSO (Single Sign-On).

Improvements
  1. An option to prevent the synchronisation of Assignee for summary tasks.

  2. The ability to synchronise predecessors of different types (FS/FF/SS/SF) individually.

  3. A single installer for both 32 and 64 bit MS Project.

Release notes v.3.7 (13 Mar 2019)

New Features
  1. 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.

  2. 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.

  3. Mapping JIRA Reporter name, e-mail and Cloud Account Id to a task field in MS Project.

  4. Copying user name, e-mail and Cloud Account Id into resource fields when importing users.

Bug fixes
  1. Saved import parameters were discarded after updating Project Settings.

  2. Updating Issue Security Level in JIRA did not work properly.

Release notes v.3.6.7 (31 Jan 2019)

Improvements
  1. Added support for Portfolio Parent Link when synchronising Custom Fields.

  2. A new method in the API to get global connection settings.

Older

Release notes v.3.6.5 (3 Oct 2018)

Improvements
  1. Always use Basic Authentication for JIRA Cloud as the cookies authentication was removed.

  2. Digitally signed add-in.

Bugs fixed
  1. Old values for updated epic links where not displayed.

  2. Allowed to change dependency type regardless of the direction as it matters during import even if the direction is from MS Project to JIRA.

  3. Invalid tooltip for the Priority field.

Release notes v.3.6.2 (12 Jun 2018)

Improvements
  1. 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.

Bugs fixed
  1. On rare occasions, Ceptah Bridge could identify the wrong sprint as current.

Release notes v.3.6

New Features
  1. Comments Synchronisation.

  2. Watchers Synchronisation.

  3. 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).

  4. Synchronisation of the Tempo Team attributes.

  5. An option to insert sub-tasks after parent tasks during import without making them children in MS Project.

Improvements
  1. Escape the "[", "]" and list separator characters in user names when importing resources.

  2. Ignore duplicated link types if they are not used in mappings (this was generating an error before).

  3. The command-line utility mspjb.exe exits with a non-zero code if there was an error during execution.

Bugs fixed
  1. Link, Sub-task or Epic Link synchronisation could fail if some parent tasks were collapsed.

Other changes
  1. Support for JIRA 5 and older has been discontinued. Please use Ceptah Bridge 3.5.8 for these versions of JIRA.

Release notes v.3.5.8

Bugs fixed
  1. Two rounds of synchronisation were required when Status was mapped to both %complete and an additional field.

Release notes v.3.5.7

Improvements
  1. More informative error message when the user cannot create issues in the project.

Bugs fixed
  1. Empty remaining estimates were ignored when copying data from JIRA to MS Project.

Release notes v.3.5.6

Improvements
  1. Complain about duplicated issue type names only when the types are actually being used.

  2. Handle the changed format of the Tempo Account and Team fields.

Release notes v.3.5.4

Bugs fixed
  1. Potential problems with importing issues on some systems.

Release notes v.3.5

New Features
  1. 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.

  2. Support for Tempo Account fields.

  3. Synchronisation of the Description, Start Date, Release Date and Released Flag attributes for Fix Version.

  4. Importing linked tasks even if they are not covered by the import condition.

  5. API for controlling Ceptah Bridge from VBA or another programming environment.

Improvements
  1. Synchronisation of the name path back to MS Project.

  2. Increased JIRA API access timeout.

Bugs fixed
  1. Fixed problems with synchronising Tempo Account custom field.

Release notes v.3.4.1

Improvements
  1. Do not scroll to top after finishing comparing issues with tasks.

Release notes v.3.4

New Features
  1. The ability to synchronise Issue Status with %complete and a filed at the same time.

  2. The option to specify the MS Project dependency type for predecessors in the Link Mapping (SF, SS, FS or FF).

  3. The ability to apply changes only to JIRA or only to MS Project.

Improvements
  1. Select the last focused task or the next available task after re-comparing in the Main Window.

  2. 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.

  3. Allow duplicated Tempo Account names. There still will be an error if the ambiguous name is used during synchronisation.

  4. Deny updating the Scheduled Start, Scheduled Finish and Scheduled Duration read-only fields on the mappings level.

Bugs fixed
  1. 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.

  2. The synchronisation outcome statistics were not displayed at the bottom of the synchronisation window.

  3. Fixed tooltip for the Populate Epic Name check box.

Release notes v.3.3.2

Improvements
  1. Digitally signed installer.

Release notes v.3.3.1

Bugs fixed
  1. An error message when opening Project Settings or synchronising if Visual Basic for Applications is not installed.

Release notes v.3.3

New features
  1. Proxy server parameters can be specified when running the command-line utility mspjb.exe.

  2. Deactivation through the command-line utility mspjb.exe.

Improvements
  1. Measure ActualDuration, BaselineDuration, BaselineXXDuration, DurationXX, DurationVariance, EnterpriseDurationXX, EnterpriseProjectDurationXX, RemainingDuration, and ScheduledDuration in hours when synchronising.

  2. Do not subtract children's work for inactive tasks.

Bugs fixed
  1. MS Project would not start after a Windows Update when Ceptah Bridge is installed.

Release notes v.3.2

New features
  1. Importing all users from a selected group or all users who have access to a particular project.

  2. The name of the last file the mappings were loaded from is displayed at the top of the Project Settings window.

  3. An option to ignore work log entries after the project Status Date.

  4. A command to toggle direction for all mappings at the same time (under the Advanced button in the menu of the mappings window).

  5. An option to ignore and preserve assignments for non-work (cost and material) resources.

Release notes v.3.1.4

Improvements
  1. Ignore " [x]" at the end of user name (added automatically in JIRA for inactive users).

  2. In the synchronisation window, the "Issue changes" and "Task changes" columns are renamed to "JIRA" and "MS Project" respectively.

  3. 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.

  4. "Time estimate" field name was changed to "Remaining Estimate" in the changes preview.

Bugs fixed
  1. Fixed some memory leaks.

  2. Occasional "There is already a request in progress" error.

  3. Ignore the order of values in the list fields, e.g. labels.

Release notes v.3.1.3

Improvements
  1. Ignore 'External' tasks.

  2. Load filters on demand in the Import Dialog Box.

Bugs fixed
  1. The main window would have an invalid position when reopening MS Project after it has been closed with the main window minimised.

Release notes v.3.1.1

Bugs fixed
  1. 'Object reference not set to an instance of an object' error when applying changes one by one.

Release notes v.3.1

Improvements
  1. The ability to provide JIRA user name and password as parameters to the command-line utility (mspjb.exe).

Bugs fixed
  1. The SyncTaskBeforePrepare event was not raised.

  2. Error if the priority mapping was off and the disabled priority direction was from JIRA to MS Project.

  3. Possible crash in mspjb.exe with project server 2003.

  4. Occasional RPC_E_SERVERCALL_RETRYLATER error when synchronising for the first time after starting MS Project.

Release notes v.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.

Improvements
  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.

Release notes v.2.10

New Features
  1. Sprint field synchronisation. Sprint Name, Start, End and Completion dates as well as State can be mapped to MS Project fields.

  2. Support for Tempo Account and Team fields. The fields can be mapped using the custom field mappings.

  3. Resolution Date mapping (JIRA 6+).

  4. Map JIRA project by name (in addition to mapping by key).

  5. 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.

  6. '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.

  7. '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.

  8. If there is a problem with updating a particular MS Project field, Ceptah Bridge adds a waring to the synchronisation results and continues synchronisation.

Improvements
  1. 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.

  2. Logging improvements.

  3. More verbose mspjb.exe output.

  4. Order projects in the drop-down list by key.

  5. Added the User Agent header to requests when reading issue XML (JIRA 5-) and performing rest calls.

  6. 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.

Bugs fixed
  1. MS Project could be left running in background if there was an error during synchronisation using the command-line tool (mspjb.exe).

Release notes v.2.9.4

Bugs fixed
  1. 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.

Improvements
  1. 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.

Release notes v.2.9.3

Bugs fixed
  1. Error when Fix Versions, Affects Versions or Components field is mapped and the field is hidden for an issue by the assigned field configuration.

Release notes v.2.9.2

Bugs fixed
  1. "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.

  2. Issue Type filters were not disabled for the link and epic link mappings when the linking mode was not 'Parent'.

Release notes v.2.9.1

Bugs fixed
  1. An error during activation if installed over an older version.

Release notes v.2.9.0

New Features
  1. New sub-task mapping, that can be applied to particular issue types.

  2. New epic Link mapping, that can be applied to particular issue types and task outline levels.

  3. The ability to set Epic Name for Epics to the Summary value.

  4. The ability to apply issue link mappings to particular issue types and task outline levels.

  5. The option to delete tasks that are linked to issues that do not longer exist.

  6. Offline activation.

  7. Activation using the command-line tool.

Improvements
  1. The ability to synchronise Project Server projects using the command-line tool. The project name should be formatted as '<>\project name'.

Bugs fixed
  1. Some fields could not be synchronised in JIRA 5 or earlier when connecting through a proxy server.

  2. "Method not found: 'System.Object Newtonsoft.Json.Linq.Jtoken.ToObject(System.Type)'" error on some systems.

Release notes v.2.8.3

Bugs fixed
  1. Ceptah Bridge could crash MS Project under some circumstances.

Release notes v.2.8.2

Bugs fixed
  1. Error when trying to clear the Affects Versions, Fix Versions or Components fields in JIRA.

Release notes v.2.8.1

Bugs fixed
  1. Ceptah Bridge would always fall back to the SOAP Api when connected to JIRA through a proxy server.

Release notes v.2.8.0

New Features
  1. 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.

  2. 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.

  3. 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.

  4. 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.

Improvements
  1. 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.

Release notes v.2.7.0

New Features
  1. Import issues filtered with a JQL query.

  2. Logging of changes applied during synchronisation. The information is written into the My Documents\Ceptah Bridge\Logs\Sync.log file.

  3. The ability to update Original Estimate in JIRA (for JIRA 6 and higher).

  4. The ability to synchronise only existing issues without creating new ones (ignoring unlinked tasks during synchronisation).

Improvements
  1. A new log files location (My Documents\Ceptah Bridge\Logs). The log files folder can be opened from the Ceptah Bridge menu.

Bugs Fixed
  1. An error when pasting individual segments of the serial key during activation.

Release notes v.2.6.2

Bugs Fixed
  1. Variations in the line ending formats were not ignored when comparing multiline text fields from JIRA and MS Project.

Release notes v.2.6.1

Bugs Fixed
  1. 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.

Release notes v.2.6.0

New Features
  1. The ability to update parent (move task) in MS Project when applying a link mapping with the 'Parent' mode on the MS Project side.

Bugs Fixed
  1. Error when importing from JIRA 6 with the Worklog mapping enabled.

  2. Error when synchronising DateTime custom JIRA field (in JIRA 6).

Release notes v.2.5.0

New Features
  1. The ability to connect to JIRA through a proxy server.

Bugs Fixed
  1. 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.

Release notes v.2.4.1

Bugs fixed
  1. The "Accept remote API calls" option was still required for the "Close Resolved issues" function to work with JIRA 6+.

Release notes v.2.4

New features
  1. Test Connection button in the Connection Settings.
  2. Full support for the cascading select custom fields.
Improvements
  1. Only REST API is used to communicate with JIRA 6 or higher. The deprecated SOAP API is no longer engaged when working with these JIRA versions and the "Accept remote API calls" option does not need to be turned on. For earlier JIRA versions Ceptah Bridge still falls back to the SOAP API and issue XML downloading for some operations.
  2. If entered, a trailing slash is automatically removed from the JIRA URL in the connection settings.
  3. Improved performance when working with JIRA 6 or higher for the cases where synchronisation was slow due to extremely slow JIRA authentication. For unknown reasons, JIRA Authentication may take much longer with some JIRA instances (irrespective of Ceptah Bridge). When synchronising some fields that required downloading issue XML, the authentication was performed repeatedly, which significantly slowed down import and synchronisation. Now, when working with JIRA 6 and higher, authentication is performed only once.
Bugs fixed
  1. "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.

Release notes v.2.3.3

Bugs fixed
  1. "There are multiple tasks associated with the following issue(s): SKIP." error during import when using SKIP in the issue key column to skip tasks.

Release notes v.2.3.2

Improvements
  1. The Duration field is added to the list of MS Project fields in the Remaining Estimate mapping. The Duration value is converted from the JIRA estimate value correctly now.
Bugs fixed
  1. "The parametervalue must be between '0' and '3579139.40666667'. Parameter name: paragraphWidth." error on some computers when configuring issue links.
  2. Null reference exception when the linked issues were not mapped to a task (in the predecessors mode).
  3. Spaces in the issue key field were treated as an issue key and a new issue for the task was not created.
  4. "An item with the same key has already been added" error when multiple tasks were mapped to the same issue.
  5. A JQL error was raised during import from a JIRA project when the project key was a reserved JQL word (e.g. OR, NEXT, etc.) and the number of issues exceeded 100.

Release notes v.2.3.1

Improvements
  1. A more descriptive error message for the case when a date in JIRA has a time component.
  2. A check to prevent Ceptah Bridge for installing on .Net 4.0 Client Profile.
Bugs fixed
  1. 'Compare Selected' operation could not be executed using the drop-down button in the main Ceath Bridge window.
  2. Unticked tasks were marked as cancelled after synchronisation.

Release notes v.2.3.0

New Features
  1. Issue links mapping. JIRA issue links can be mapped to predecessors, the parent/child relation or a text field in Microsoft Project.
Bugs fixed
  1. 'Activation data corrupted' problem that happened on some computers.

Release notes v.2.2.0

New Features
  1. JIRA user import. Existing JIRA users can be imported into Microsoft Project as resources and optionally assigned to the selected tasks. If JIRA users are mapped to resources by a custom resource field, the field is populated automatically.
  2. Automatic JIRA user import. JIRA users are imported automatically as resources during issue import and synchronisation as required. This is different from the previous versions where the resources had to be created and mapped to JIRA users manually prior to synchronisation if the 'by resource field' resource mapping method was used.
  3. Added an option to make imported tasks 'Automatic' in MS Project 2010/2013. In the previous versions that behaviour was not optional and all new task were always Automatic. Now, if the option is switched off, new tasks will be either Manual or Automatic, depending on the Microsoft Project settings.
  4. Support for blank Start, Finish and Duration fields for Manual tasks in MS Project 2010/2013.
Bugs fixed
  1. 'Activation data corrupted' problem that happened on some computers.

Release notes v.2.1.2

Improvements
  1. When using with JIRA 5, it is no longer required that the JIRA account used by Ceptah Bridge has permission to edit issues, providing that no JIRA data is updated. Earlier versions always required the edit permission.
  2. When using with JIRA 5, it is no longer required that the JIRA account used by Ceptah Bridge has the administrator permissions to display the dropdown list of custom JIRA fields in the custom field mappings grid.
Bugs fixed
  1. Technical error if there are two resources with the same name. Now a user-friendly message is displayed.
Important notes

As of this version, Ceptah Bridge requires the .NET Framework 3.5.

Release notes v.2.1.1

Bugs fixed
  1. Incorrect synchronisation of the Remaining Estimate field during issue creation.
  2. The Compare button is not repositioned when the Synchronisation window is resized.

Release notes v.2.1

New features
  1. Full support of the Microsoft Project Server enterprise fields.
  2. Original Estimate mapping.
  3. The ability to synchronise only selected MS Project tasks.
  4. The ability to exclude the child task work from the summary task work when synchronising it with the Time Remaining.
Bugs fixed
  1. Error if there is an empty row in the resource sheet.

Release notes v.2.0

New features
  1. New look.
  2. "Labels" standard issue field support.
  3. "Labels" custom issue field support.
  4. Detailed tooltips for each mapping option.
Improvements.
  1. User Guide in the standard Windows Help format instead of the PDF.

Release notes v.1.2.35

Bugs fixed
  1. "Input string was not in a correct format." error when using Ceptah Bridge with JIRA Studio.

Release notes v.1.2.34

Bugs fixed
  1. Empty table cells in the Close Issues Window.
Improvements
  1. Optimised import for a large number of issues.

Release notes v.1.2.33

Improvements
  1. Issues can be created in JIRA 4.4 and higher even if there are required custom fields. Previous versions of Ceptah Bridge would fail to create issues if there were required custom fields defined for the issues.

Release notes v.1.2.32

New features
  1. Sub-tasks creation in JIRA (JIRA 4.4 and higher).
  2. An option to turn the case-insensitive JIRA user synchronisation on and off.
Improvements
  1. Some error messages became more self-explanatory.

Release notes v.1.2.31

Bugs fixed
  1. Error: 'MS Project task field 'Finish': The argument value is not valid.' when trying to update Finish for a summary task in MS Project 2003/2007.
  2. Case-insensitive JIRA user synchronisation (the case did matter with the previous versions).

Release notes v.1.2.30

New features
  1. Activation through a Proxy Server.
  2. Case-insensitive synchronisation of the assignee field - the source value in MS Project does not have to be lower-case anymore.
Bugs fixed
  1. 'No management object instances' error during activation on some hardware configurations.

Release notes v.1.2.29

New features
  1. Support for empty priority field.
Bugs fixed
  1. 'HTTP Status 417: Expectation Failed' during activation under some configurations where the Bridge was behind a proxy server that did not support the "100 continue" expectation.

Release notes v.1.2.28

New features
  1. Worklog entries for subtasks can be merged with the worklog of the main issue when detailed time tracking information is synchronised.
Bugs fixed
  1. Error when Issue Description contains multiple lines of text and it is mapped to a custom MS Project text field.
Activation
  1. If you have a previous version of the Bridge installed on the computer, you will still need to activate the new version using a new format licence key, which is different from the old format key you received in a confirmation e-mail when you purchased the product. The key can be found in the list of your licenses on www.ceptah.com. Please contact the support team at support@ceptah.com if you have any problems with reactivating your product.

Release notes v.1.2.27

New features
  1. An option to synchronise time tracking information either on the task or assignment level. The option is available only when the JIRA Assignee field is not mapped or mapped to a custom task field. Otherwise, the information is always synchronised for the entire task.
Bugs fixed
  1. "MS Project task field 'Name': The argument value is not valid." error when an issue summary contains unprintable characters (e.g. tabs).
  2. The Bridge silently failed to update standard JIRA fields if they were not displayed on the default issue editing screen. Now an error is shown in this case.

Release notes v.1.2.26

Installation
  1. You will need to manually unstall a previous version of the product. This version does not remove it from the computer.
New features
  1. Microsoft Project 2010 support, including the 64-bit version.
Bugs fixed
  1. A project could slow down if its synchronisation settings were imported from an XML file a number of times. To fix an affected project, open it, launch the Settings Dialog box and click OK.
  2. Former custom field mappings were not removed during settings XML file import. As a result, the mappings were duplicated.
Known issues
  1. 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.
  2. 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'.

Release notes v.1.2.25

Bugs fixed
  1. If a custom field did not appear on the default screen for an issue in JIRA due to its inapplicability to the issue or configuration, the "'JIRA field 'FieldName': Issue custom field 'FieldName' was not found" error was shown when the issue was imported, created or synchronised. The current version raises an error only when such a field is assigned a value different from null during issue creation or synchronisation. For a field to be set for an issue, the field still should appear on the default screen of the issue in JIRA.
  2. The 'Time format' field was not saved when entered in General Settings Dialog.
  3. If the user password contained some specific symbols, such as '&', an attempt to synchronise time tracking data or import subtasks resulted in the "'100' is an unexpected token. The expected token is '"' or '''. Line 25, position 57." error.
  4. %complete field synchronisation failed with the following error: Specified cast is not valid.
Known issues
  1. 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.
  2. 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'.

Release notes v.1.2.24

New features
  1. Sub-tasks import.
  2. Extended custom fields support.
Bugs fixed
  1. Versions and components synchronisaton did not work correctly for versions or components having names with leading or trailing spaces.
Known issues
  1. 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.
  2. 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'.

Release notes v.1.2.23

Bugs fixed
  1. Worklog synchronisation/import did not work for JIRA versions earlier than 3.13.2.
Known issues
  1. 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.
  2. 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'.

Release notes v.1.2.22

New features
  1. Worklog synchronisation/import for all supported JIRA versions (used to be only for JIRA 4.0 and higher).
Bugs fixed
  1. Task name path -> Issue summary synchronisation did not work.
Known issues
  1. 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.
  2. 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'.

Release notes v.1.2.21

New features
  1. Worklog synchronisation/import (JIRA 4.0 and higher).
  2. The option to select whether the time tracking information of the subtasks should be counted in when a task is synchronised or imported.
Bugs fixed
  1. Minor user interface issues.
Known issues
  1. 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.
  2. 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'.
Version upgrade

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.

Release notes v.1.2.20

New features
  1. Export and import of the synchronization settings to/from an XML file.
  2. An exported or manually created XML file can be used to specify the settings for the command-line tool.
  3. User's Guide can be launched from the menu.
Bugs fixed
  1. An unassigned issue could not be synchronized when the Assignee JIRA field was mapped to a resource field.
Version upgrade
If you are using a version of the software earlier than 1.2.19, after installing the version 1.2.20 your general settings and licence key information will not be saved. Please reenter your general settings and licence key.

Release notes v.1.2.19

New features
  1. Bi-directional Issue Summary synchronization.
  2. Bi-directional Issue Due Date synchronization.
  3. Bi-directional Issue Assignee synchronization.
  4. The ability to use Task ID in the custom fields mappings.
  5. Command-line import/synchronization utility mspjb.exe located in the default installation folder (C:\Program Files\Ceptah\Msp JIRA Bridge or C:\Program Files (x86)\Ceptah\Msp JIRA Bridge on x64). Please refer to User's Gide for details.
Bugs fixed
  1. The software could not be installed on Windows 7.
Version upgrade
If you are using a previous version of the software, after installing the version 1.2.19 your general settings and licence key information will not be saved. Please reenter your general settings and licence key.

Release notes v.1.2.18

Bugs fixed
  1. Import of the issues of a selected project from JIRA 4.0 failed with the following error message: com.atlassion.jira.util.dbc.Assertions$NullArgumentException: clauseValue should not be null.
  2. When the assignee synchronization was disabled, under some cirqumstances import and synchronization could fail with the following error message: The project settings are corrupted. Please, reset the settings.

Release notes v.1.2.17

Bugs fixed
  1. When using JIRA professional edition, an attempt to specify default component or either of versions, as well as to synchronize components or versions, would result in an error messge. Now the message is generated only when trying to work with security levels, as the feature is not supported in the professional edition of JIRA.

Release notes v.1.2.14

Bugs fixed
  1. If the time zone on the JIRA server was fractional (e.g. GMT+4.5), an attempt to synchronize would result in an error message.

Release notes v.1.2.13

Improvements
  1. Assignee mappings have been extended. It is now possible to map assignee to a custom text task field.
  2. When assignee in JIRA is updated with a value from MS Project, it is now possible to change the direction of synchronization of the field in the details section of the synchronization window and update the MS Project task using the assignee from JIRA instead.

Release notes v.1.2.12

Bugs fixed
  1. A connection over SSL (https) did not work.

Release notes v.1.2.11

Bugs fixed
  1. Import crashed if there was a gap between tasks in MS Project.
Improvements
  1. Status mappings have been extended. In particular, status can be mapped to a custom text field now.
  2. Time tracking mappings have been extended. The 'Time spent' and 'Remaining estimate' mappings are independent now, and both can be mapped to custom numeric fields instead of 'Actual Work' and 'Work'.

Release notes v.1.2.10

Bugs fixed
  1. During import, if there were already tasks in the project, the new issues would have the same outline level as the last task. Now all imported tasks are created on the first level.
Improvements
  1. Flexible status mappings – any issue statuses, including custom statuses, can be mapped to the values of the Percent Complete task field.
  2. A mapping for the 'Resolution' issue field has been added.
  3. A mapping for the 'Reporter' issue field has been added.
  4. A mapping for the 'Environment' issue field has been added.
  5. A mapping for the 'Votes' issue field has been added.
  6. Temporary evaluation keys are now supported. An evaluation key can be generated from the My Account section of the web site and allows using the software without any functional limitations for one month.

Release notes v.1.2.9

Bugs fixed
  1. Error "Issue type with id='?' was not found" when importing subtasks.
Improvements
  1. It is now possible to specify a non-default format for dates in JIRA as part of the connection settings. In previous versions date-related communications with JIRA would fail if a non-default date picker format was set.
  2. The “All” import mode in the import dialog was replaced with the “Project” mode. The mode allows the user to select the project to import issues from.
  3. When the import dialog opens, the fields of the form are pre-populated with the values used for the last import into the project.
  4. If the import mode is by issue keys, and an issue does not exist, the invalid issue key is shown in the respective row on the synchronization window (it used to be blank in this case).