P4 Plan for Jira Server Release Notes

Version numbers

P4 Plan versions are named e.g. 2025.1/001, where 2025 is the release year, 1 is the release number and 001 is the build number.

Any version includes all changes of previous releases.

Versions prior to 2024.1 use the older format, for example 11.1055.

Release notes for the P4 Plan products

• P4 Plan Client & Server
• P4 Plan Web
• P4 Plan API
• P4 Plan for Jira Cloud
• P4 Plan for Jira Server
• P4 Plan for Perforce ALM
• P4 Plan for LDAP

Note

The product is now named P4 Plan. Read more about the change here: Introducing the p4 platform

11.1005

Release date: 2024-01-23

Fixes

• 9036 A: Jira integration crashes when syncing links
• 9037 B: Jira integration crashes on service stop

Compatibility and Upgrade Notes

• Requires Hansoft Server version 11.1055 or later.

11.1004

Release date: 2023-12-05

New features

• Support for Jira 9.11.3 added. The new plugin hansoft-support-11.1004-JIRA-9.11.jar supports Jira version 9.11.3.

Compatibility and Upgrade Notes

• Requires Hansoft Server version 11.1050 or later.

11.1003

Release date: 2023-09-19

New features

• Support for Jira 9.6 added. The new plugin hansoft-support-11.1003-JIRA-9.6.jar supports Jira version 9.6.

Compatibility and Upgrade Notes

• Requires Hansoft Server version 11.1041 or later.

10.2005

Release date: 2020-06-30

Fixes

• 7465 B: JIRA integration sync of Hansoft and JIRA sprints can stop working if Hansoft sprint synced to JIRA is removed in JIRA when integration is down
• 8102 B: JIRA sprint data is not shown in sprint column in Hansoft
• 47731 C: Hansoft wrongfully uncommits items in JIRA

Compatibility and Upgrade Notes

• Requires Hansoft Server version 10.2021 or later.

10.2004

Release date: 2020-06-16

Fixes

• 8108 B: WBS column is not synced to JIRA

Compatibility and Upgrade Notes

• Requires Hansoft Server version 10.2021 or later.

10.1012

Release date: 2020-02-28

Fixes

• 7810 Work log columns are missing in the integration: Work logged (JIRA), Work Original Estimate (JIRA), Work Remaining
• 7896 Support for Jira DC deployments where the nodes use different protocols: http vs https
• 7904 Intermittent NullPointerException exceptions in getUserName when processing changes on secondary Jira DC nodes

Compatibility and Upgrade Notes

• Requires Hansoft Server version 10.1039 or later

10.1008

Release date: 2020-01-14

New features

• Hansoft Jira Integration 10.1008 adds support for Atlassian Jira Data Center.
• Hansoft Jira Integration 10.1008 adds support for Atlassian Jira 8.5.

Compatibility and Upgrade Notes

• Requires Hansoft Server version 10.1035 or later

10.1007

Release date: 2019-11-26

Performance Improvements

• User matching errors are now turned off to reduce memory footprint. Can be turned on again with: SuppressUserMatchingErrors 0
• The poller for configuration changes, no longer listen to changes to workflows in Jira projects that are not synced.

Compatibility and Upgrade Notes

• Hansoft Jira Integration 10.1007 removes support for Jira versions prior to 6.4.
• Requires Hansoft Server version 10.1032 or later

10.1004

Release date: 2019-07-09

New Features

• Support for Jira 8.0 and later. The New plugin hansoft-support-10.1004-JIRA-8.2.jar supports Jira versions from 8.0 to 8.2. (The plugin hansoft-support-10.1004-JIRA-7.5.jar supports all Jira 7.x versions from 7.5 and forward.)
• Make sync of Hansoft releases optional. This sync is on by default, but can be turned off if Hansoft releases are not used in Jira. It can be found on the "Jira project synchronization" tab in the "Customize project integration settings" dialog.
• Performance improvements when syncing custom fields.
• Improved debug logging in Jira. From the Logging-Profiling screen in Jira, set se.hansoft to DEBUG to see what functions are invoked internally in the integration. Use TRACE for more low-level detials. This can be useful when troubleshooting integration problems.

Fixes

• 7318 A: Invalid ID error repeats in the Jira integration log due to missing project sync for SDK user
• 7645 B: Jira integration crash when Jira returns null as filter

Compatibility and Upgrade Notes

• Requires Hansoft Server version 10.1008 or later

10.0017

Release date: 2019-05-14

New Feature

• Improved exception logging when failing to rename a Jira release

Compatibility and Upgrade Notes

• Requires Hansoft Server version 10.0045 or later

10.0016

Release date: 2018-12-11

Fixes

• 39259 C: The "Default JIRA project ..." and "Default JIRA issue type ..." values are overridden by the last selected value in Hansoft

Compatibility and Upgrade Notes

• Requires Hansoft Server version 10.0036 or later

10.0016

Release date: 2018-12-11

Fixes

• 39259 C: The "Default JIRA project ..." and "Default JIRA issue type ..." values are overridden by the last selected value in Hansoft

Compatibility and Upgrade Notes

• Requires Hansoft Server version 10.0036 or later

10.0017

Release date: 2019-05-14

New Feature

• Improved exception logging when failing to rename a Jira release

Compatibility and Upgrade Notes

• Requires Hansoft Server version 10.0045 or later

10.0016

Release date: 2018-12-11

Fixes

• 39259 C: The "Default JIRA project ..." and "Default JIRA issue type ..." values are overridden by the last selected value in Hansoft

Compatibility and Upgrade Notes

• Requires Hansoft Server version 10.0036 or later

10.0014

Release date: 2018-11-13

Fixes

• 7420 D :Jira integration logs "The unique identifier specified to the function is not valid" after a card is moved

Compatibility and Upgrade Notes

• Requires Hansoft Server version 10.0027 or later

10.0013

Release date: 2018-10-02

New Features

• Sync Hansoft sprints to JIRA sprints. This is an option available in the "JIRA project synchronization" tab in Customize project integration settings.

Upgrade notes

• Hansoft sprints are no longer mapped to JIRA versions
• All JIRA versions created from Hansoft sprints will be deleted in JIRA
• Tasks committed to sprints in Hansoft will be converted to scheduled tasks, if they are committed to JIRA sprints in JIRA

Fixes

• 7211 B: JIRA throws IllegalArgumentException when there are two identical sprints
• 7212 B: JIRA throws IllegalArgumentException if you move a sprint up in time past its start date
• 7196 B: The columns "Board Column" and "Board Lane" are not available in JIRA
• 7342 C: "Committed bugs are not synced to JIRA

Compatibility and Upgrade Notes

• Requires Hansoft Server version 10.0027 or later

10.0012

Release date: 2018-08-21

New Features

• Sync only selected fields to Hansoft. The fields "JIRA URL", "Project - Issue type" and "Resolution" are always synced. Additional fields can be configured in the new "JIRA field synchronization" tab in the Project integration settings dialog.

Compatibility and Upgrade Notes

• Requires Hansoft Server version 10.0024 or later