Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Add-on Version
5.26.0

6.1

6.2

6.36.47.07.17.27.37.4Release dateRelease Note
4.0-JIRA-6.0-6.4
    2015-11-24 

Summary: Major new release

Improving existing Administration screens

  • Additional optional settings,new functionalities and facilities.

New Administration screens

  • The Escalate Post Function Administration screen
  • The Mapping Scheme Administration, Mapping Scheme Configuration and Mapping Pattern Administration screens to configure mappings reusable on multiple Projects.

Usage facilities

  • Enabling the create another box
  • Issues ranking
  • Enabling Sync for JIRA link
  • JQL Functions.

 

4.0-JIRA-7.0
    

Summary: New Features and JIRA 7 compatibility

  • Improvements to existing Administration screens: additional optional settings,new functionalities and facilities.
  • New Administration screens
  • Usage facilities: enabling the create another box., issues ranking, enabling sync for JIRA link, JQL Functions, others
  • JIRA 7 compatibility
4.1-JIRA-6.0-6.4
     2015-12-01 

Summary: ScriptRunner compatibility and bug fixing

  • Quick linker compatibility with ScriptRunner v.3
  • Completed tasks not shown as completed and other Minor Bug Fixes
4.1-JIRA-7.0
    

Summary: Bug fixing

  • Completed tasks not shown as completed and other Minor Bug Fixes
4.1.1-JIRA-6.0-6.4
     2015-12-28

Summary: Performance improvements

  • Improved JQL hqlLinkedIssuesOf performance and other minor bug fixing
4.1.1-JIRA-7.0
    
4.2-JIRA-6.0-6.4
    2016-01-26

Summary: New Features

  • The Mappings Administration screen allows filtering displayed mappings.
  • A mapping can be configured to enable only creation &linking or just linking
4.2-JIRA-7.0
    

Summary: New Features

  • The Mappings Administration screen allows filtering displayed mappings.
  • A mapping can be configured to enable only creation &linking or just linking
4.3-JIRA-6.0-6.4
    2016-03-08

Summary: New Features and bug fixing

New Features

  • ServiceDesk compatibility 

Improvement

  • Improving 'linking existing issue' performance

Bugs

  • Error on queue log

 

4.3-JIRA-7.0
    
4.4-JIRA-6.0-6.4
   2016-04-02

Summary: New features, improvements and minor bug fixing

New Features

  • Custom fields available for syncing include Select List (single and multiple choice), Radio Buttons, Checkboxes (Local Partnership exclusively)

Improvement

  • Quick Link web panel: if no quick link exists, the panel is not displayed (e.g. only jira link)

 

4.4-JIRA-7.0-7.1
   
4.5-JIRA-6.0-6.4
   

2016-05-09

Summary: New features and bug fixing

New Features

Bug fixing

  • Create another does not display attachment field
  • Error Message 'Undefined missing quick-edit' pops up randomly
4.5-JIRA-7.0-7.1
   
4.6-JIRA-6.0-6.4
   

2016-06-09


Summary: New features and bug fixing

New Features

Bug fixing

  • Default values not initially loaded during upgrade from JIRA 6 to JIRA 7 (Sql Server database)
  • Other minor bug fixing
4.6-JIRA-7.0-7.1
   
4.7-JIRA-6.0-6.4
   

2016-06-23

 

Summary: New features and improvements

New Features

  • Custom fields available for syncing include Select List (cascading). The feature is provided for Local Partnership exclusively.

Improvements

  • Enhancing the information content displayed on the Permissions Administration screen
4.7-JIRA-7.0-7.1
   
4.7.1-JIRA-6.0-6.4
   

2016-06-28

 

Summary: Bug fixing

Bug fixing

  • Unexpected Synchronization failure alert 
  • Attachment synchronization doesn't work properly for .msg files 
4.7.1-JIRA-7.0-7.1
   
4.7.2-JIRA-6.0-6.4
   2016-07-26

Summary: Bug fixing

Bug fixing

    • Sync on create doesn't work when comments are synced on create.


4.7.2-JIRA-7.0-7.1
   
4.7.3-JIRA-6.0-6.4
   2016-08-06 

Summary: Bug fixing

Bug fixing

  • Herzum Quick Linker is not compatible with Behaviors.
  • A remote Partnership is not activated when the remote Partnership identifier doesn't exist on the local instance.
 
4.7.3-JIRA-7.0-7.1
   
4.7.4-JIRA-6.0-6.4
 
 
 
 
 
 
 
 
   

2016-08-23

 

Summary: Bug fixing

Bug fixing

  • the escalate issue post function fails when trying to synchronize a required target field with a text including the character '&' 
  • the remote screen doesn't display ant field when the logged user has not the privilege to create issue in the project that is loaded in the cache
 
4.7.4-JIRA-7.0-7.1
 
 
 
 
  
4.7.5-JIRA-6.0-6.4
   

2016-09-06

Summary: New Features and Bug fixing

New Features

  • Providing partial compatibility with Database Custom Field add-on

Bug fixing

  • the create screen doesn't display the expected fields when the target issue type is a sub-task or a custom issue type
4.7.5-JIRA-7.0-7.2
  
4.7.6-JIRA-6.0-6.4
     

2016-10-18


 

Summary: New Features

 New Features

  • A new configurable option allows to force synchronization without checking Screen configurations.
 
4.7.6-JIRA-7.0-7.2      
  
4.7.7-JIRA-6.0-6.4

     2016-11-25

Summary: Bug fixing

Bug fixing

  • Logout problem when creating the issue via partnership credentials
4.7.7-JIRA-7.0-7.2      

   
4.8-JIRA-6.0-6.4

     2016-12-06Summary: Data center compatible
4.8-JIRA-7.0-7.2      

  
4.9-JIRA-6.0-6.4

     2017-02-03

Summary: Bug Fixing and JIRA 7.3 compatibility

  • ServiceProxyDestroyed Exception when navigating the Global Configuration administration screen after disabling/enabling the add-on
4.9-JIRA-7.0-7.3      

 
4.10-JIRA-6.0-6.4

     2017-03-20

Summary: Enhancement

  • The Web panel on the issue displays all action buttons without having to click on "More".
4.10-JIRA-7.0-7.3      

   
4.11-JIRA-6.0-6.4

     2017-04-21

Summary: New Features

  • Capability to sync restriction on the visibility of comments
4.11-JIRA-7.0-7.3      

 
4.11.1-JIRA-6.0-6.4

     
2017-06-13

Summary: Bug Fixing

  • When the call URL Connection fails, logs don't inform on the cause
  • When the username applied on partnership credential has not permission to edit the remote issue, the issue is created but not linked
  • When a destination URL allows to reach a remote instance but it is not set as Base URL, it generates a loop
  • The message alerting of a Partnership creation failure, on the configuration screen, doesn't detail the cause

    Expand
    title Expand to view details

    New alerts allowing to troubleshoot a Partnership creation failure:

    • Source URL must be this instance's Base URL
    • Destination URL is invalid
    • Failure authenticating with Source Username when calling source URL from source URL 
    • Failure authenticating with Destination Username when calling destination URL from source URL
  • Other bugs
4.11.1-JIRA-7.0-7.3      

Image Added

Info

Case of JIRA Server 7, the add-on requires that JIRA Software has been installed in order to work properly.

...