| Version | Compatibility | Date Released | Summary |
|---|
| 1.0.5 | Jira Server 6.2.1 - 6.4.14 | | First release |
| 1.0.6 | Jira Server 6.2.1 - 6.4.14 | | - LOOKUP-1 - Unable to change assignee with lookup manager during issue creation
- LOOKUP-2 - Lookup manager is unable to map user into userpicker field type
|
| 1.0.7 | Jira Server 6.2.1 - 6.4.14 | | - LOOKUP-8 - Column_ID cannot be cast into Integer in PostgreSQL
- LOOKUP-9 - To include null value check for the custom field used for lookup
|
| 1.2.0 | Jira Server 7.0.0 - 7.1.10 | | - Jira 7 Compatible
- Data Center Compatible
|
| 1.2.1 | Jira Server 7.0.0 - 7.3.9 | | - LOOKUP-1 - Unable to change assignee with lookup manager during issue creation
- LOOKUP-2 - Lookup manager is unable to map user into userpicker field type
|
| 1.2.4 | Jira Server 7.0.0 - 7.4.6 | | - LOOKUP-8 - Column_ID cannot be cast into Integer in PostgreSQL
- LOOKUP-9 - To include null value check for the custom field used for lookup
|
| 1.3.0 | Jira Server 7.0.0 - 7.5.4 | | - LOOKUP-10 - To be able to set Multi user picker custom fields
- LOOKUP-11 - To allow exporting of Lookup Tables
|
| 1.3.1 | Jira Server 7.0.0 - 7.8.0 | | - LOOKUP-13 - To provide graceful error message if lookup fails on Create Issue
- LOOKUP-14 - Assignee/Reporter field cannot be used for lookup on create issue
- LOOKUP-15 - Unable to access Lookup Table if user have changed username
|
| 1.3.2 | Jira Server 7.0.0 - 7.8.0 |
| Improvement - LOOKUP-18 - Allow source field to be left empty
Bug Fix - LOOKUP-19 - Unable to display proper error message when source field is a system field
- LOOKUP-20 - Unable to perform lookup using the latest value for issue
|
