Release note:
https://tablegrid.atlassian.net/wiki/spaces/TGED/pages/2426639/Release+Notes+-+Version+1.29
Fixed an issue with Oracle DB compatibility
Fixed an issue with Oracle DB compatibility
Compatibility with Jira 8.0
Now you can use Table Grid Editor with the 8.0 Jira
Bug Fixes and Improvements
Various bug fixes
When using the multi level cascading field, please upgrade to this hot fix which solves a data loss problem whenever a cascading field is cleared.
When using the multi level cascading field, please upgrade to this hot fix which solves a data loss problem whenever a cascading field is cleared.
1.27 brings to the table grid editor for server
* Issue level csv importFirst implemented on the cloud version of the table grid, the server version now also allows to import csv files straight into a grid.More information here
* Database support for Sybase 15 and higher
* Support for Oracle 12
* Bug fixes
Please check the release history.
Bug
Improvement
We're looking for beta users of our new table grid editor for cloud add-on. If interested - send a mail to support.tge@idalko.com.
We're looking for beta users of our new table grid editor for cloud add-on. If interested - send a mail to support.tge@idalko.com.
We're looking for beta users of our new table grid editor for cloud add-on. If interested - send a mail to support.tge@idalko.com
In this version, we deliver
Check out our release history for more information
* IGRID-3798: Jira UX fails in a number of cases with 1.25.1 and mssql
This multi level cascading select allows you to create a single custom field which is a combination of one or more drop downs. It allows you to create an unlimited number of select lists where the choice of the values available in a select list dependent on the values from any other list (or issue value)
Check Release History for more details.
In 1.21.0, we introduced the Table Grid Reader, which allows to view the content of any table in the context of an issue. This release completes this development epic, by supporting more properties such as gd.caption, gd.collapsedefault, gd.hideHeader, gd.hideFooter, gd.rownumbers, col.xyz.plain.width, col.xyz.renderer, col.xyz.tooltip, col.xyz.width, col.xyz.summary and col.xyz.formatDate.
Furthermore, we introduced a REST Api for the table grid reader.
In this release we fix an important regression introduced in 1.22.0. When using the col.xyz.query = customfield, it is expected that the value component of the dropdown box is identical to the label.In version 1.22.0 up to 1.23.1, the value was set to the option id of the customfield.
This version reverts that behaviour. This might have an impact if you have been using this property. Please contact us (support.tge@idalko.com) for more information.Also we address a long outstanding problem where storing i18n chars in Postgres would fail in certain cases.
Introducing a new property - gd.initFromParent. When set to true, the grid initial content will be copied from the grid of the parent.
Additionally a number of issues raised by our customers have been resolved.
Please check our release history for more details
Check Release History for more details
Introducing the 'connected' grid, which allows to visualise the results of an SQL query in the context of an issue
Assume you are using Jira for managing quotes for customers, and you want to show the user how much revenue a customer has been generating during the last 4 quarters to decide the level of discount this customer is entitled. Using the connected grid you can extract that information from your ERP directly into the context of the new opportunity.
Check the documentation
Meet us at Atlassian Summit to discuss how you use the table grid editor and how it be improved. We'll be at the Exalate booth (B22).
Table grid editor is now compatible with 7.2
We are looking for users who want to participate in establishing the future roadmap of the table grid editor and other idalko add-ons. If interested - let us know by sending a mail to support.tge@idalko.com, or meet us during Atlassian Summit in San Jose. We'll be at the Exalate booth (the flexible issue synchronisation solution)
Improvements
New Features
Check full release notes here
To accommodate a couple of user requests, we introducted additional properties to format the display of the grid using
With the new col.xyz.formatUser property, you can now format the display of users in user lists. And if you hover above a name, you will see the typical Jira user popup.
Also check out the Full Screen Dialogs add-on - see your tables in full.
This release fixes also an issue with displaying the grid in a Jira Agile issue detail panel.
In this version we deliver a public API which allows for enhanced automation. It covers use cases such as
The release provides
Also checkout the Java API: Groovy script examples. It contains a examples how to use the API.
And a couple of bug fixes - check out the release notes.
Happy Holidays !
PS. We are looking for users who want to be involved in the redesign of the user interface of the table grid. If interested - send a mail to support.tge (at idalko com)
This is mainly a bug fix release with following issues addressed
More details on the release history page
https://wiki.idalko.com/display/TGPD/Release+History
Note - for customers who are using the proprietary idalko license key, please contact us directly before installing the upgrade. We have been removing support for the proprietary license key, and we will convert your current key to a marketplace based key.
A set of bug fixes - thanks to our customers who raised them.
[IGRID-3368] - Wiki renderer UI defects[IGRID-3369] - gd.query does not fill data for dependent list in more complex user config[IGRID-3370] - Formula does not work in some grid configurations
Solves
* IGRID-3363 - Formula does not work if the col.xyz.name property is specified for the formula column.
Bug Fixes
Improvements
This release offers plenty of new functionalities in the grid. All these have been requested from our customers, so give it a try !
* col.xyz.type = datetimeSupport datetime
* col.xyz.type = userlistSupport userlist, can be filtered by group(s) and/or project role(s
* col.xyz.renderer = wikiNow supporting the wiki notation in text fields. Want to link to another Jira issue, just type its key ...
* SpanishThanks to our friends at Deiser, we now support spanish !
More information on this releasehttps://wiki.idalko.com/x/bIbg
(This release fixes a critical bug in 1.15.0)
In this release
And of course, as always, some more improvements and bug fixes.
More details on our release notes pages
In this release
And of course, as always, some more improvements and bug fixes.
More details on our release notes pages
Bug
Improvement
New Feature
Check also the pivot gadget - create cross tabulations with a couple of clicks.
Check Release Notes for more details
And some bug fixes ...
More detail available at http://wiki.idalko.com/x/bIbg
This release contains
More information available in the 1.14 release notes
Bug fixes in this release
Improvements
Check for more details our release history page.
We addressed a number of bugs reported by various customers, mainly in the area of filter handling, displaying of the grid and sorting of rows.
We also addressed tabbing such that the tab key brings the cell under edit to the next row.
The performance of the JQL grid function has been improved by 50%. The calculation of the defaultdate is now based on correct increments.
Check for more details our release history page.
We addressed a number of bugs reported by various customers, mainly in the area of filter handling, displaying of the grid and sorting of rows.
We also addressed tabbing such that the tab key brings the cell under edit to the next row.
This is a release candidate - a final version will be provided shortly after.
New in this release
Fixed in this release
* IGRID-2575 Validation error message pushes the grid out of inline editing pane
New in this release
Fixed in this release
New in this release
With this release, the table grid editor is made compatible with MS SQL Server (we tested MS SQL Server 2008 RC 2)
Note that this is a Release Candidate - allowing users to test the new functionality in test. The final release will be provided later on based on the collected feedback.
Fixed in this release
None.
New in this release
New in this release:
New in this release
New in this release:
Fixed in this release
16 bugs and 4 improvement requests, check the release notes for more details.
New in this release
* Datasource specifications support
* XSS attack protection
* Clone issue, now can also clone the rows associated to grids
Fixed in this release
New in this release
With this all new version we focused on making the grid less disruptive with a theme which is inherited from the Jira theme, collapsible grids, and the ability to hide the grid when it contains no (modified) data.
The formula's now also support list values, such that columns can be initialized based on the selection from a drop-down list.
Check more details in the release notes
With this all new version we focused on making the grid less disruptive with a theme which is inherited from the Jira theme, collapsible grids, and the ability to hide the grid when it contains no (modified) data.
The formula's now also support list values, such that columns can be initialized based on the selection from a dropdown list.
Check more details on the release notes
This is a release candidate allowing customers to validate the new version in staging, and provide feedback. We have some known issues around browser compatibility on IE8 and Linux.
* [IGRID-2101] - Plugin disables wallboards
* [IGRID-2107] - Scrollbars when inline editing a grid
* [IGRID-2109] - uniqueSequence not working - numbering not initialising to 1
This patch release solves an interaction issue with Jira Agile (version 6.3.0.2), and a usability issue which was introduced with v1.10
* [IGRID-2032] - Tabbing looses focus if cell is editing
* [IGRID-2042] - TGE disables the Sprint area in greenhopper 6.3.0.2
The fix for IGRID-1961 (Inline edit shows content of previous inline edit) affected the create issue operation. Switching project / issue type during create issue would not render the proper grid (s).
This issue is now fixed.
You can count on it !
With version 1.10 we introduce the capability to calculate values when entering data into the grid.
Just like a spreadsheet where columns are calculated based on values entered in other columns.
The grid supports a large array of formulas such as
Plain arithmetic
col.linetotal.type=number
col.linetotal.formula={weight} * {shipprice} * 1.10
Concatenation
col.label.type = string
col.label.formula = {company} + " " + {shipaddress} + " " + {contactperson} + " " + {weight} + "lbs"
Conditional
col.linetotal.type=number
col.linetotal.formula=if( {shipaddress} =~ ["London", "Birmingham"]) { {weight} * {shipprice} * 1.10 } else {{weight} * {shipprice} * 1.50 }
The formal specification can be found on Formula - formal syntax specifications and of course, examples are always helpfull : Formula - Examples
Bug fixes and improvements
* [IGRID-1569] - columnid is not always case insensitive
* [IGRID-1826] - Sonar reports critical violations
* [IGRID-1845] - Default value applies instead of null after "Insert Rows" while updating/creating issue
* [IGRID-1853] - Checkbox can not be incell-edited in edit mode
* [IGRID-1859] - Strange number column value conversion while persisting
* [IGRID-1866] - Checkbox doesn't work when col.xyz.unchecked=false
* [IGRID-1867] - No grids on view issue page for IE9
* [IGRID-1869] - Changing tablename for DTG brings to unpredictable table usage
* [IGRID-1883] - Data loss scenario reappears
* [IGRID-1737] - Add prefixes to column input ids to avoid collisions with Jira HTML element ids
* [IGRID-1813] - Redirect for "Log In" button
* [IGRID-1819] - Performance improvements for calculated columns
* [IGRID-1882] - Summary is not rounded
* [IGRID-1961] - Inline edit shows content of previous inline edit
* [IGRID-1962] - Grid doesn't display in Jira 5.0.7 (standalone)
* [IGRID-1971] - Sequence is not properly updated
* [IGRID-1987] - Grid hangs up pages on IE8 (Jira6)
* [IGRID-1989] - Remove description, environment, comments from data (rest) call
New release candidate with a couple of bug fixes.
* [IGRID-1961] - Inline edit shows content of previous inline edit
* [IGRID-1962] - Grid doesn't display in Jira 5.0.7 (standalone)
* [IGRID-1971] - Sequence is not properly updated
With version 1.10 we introduce the capability to calculate values when entering data into the grid.
Just like a spreadsheet where columns are calculated based on values entered in other columns.
The grid supports a large array of formulas such as
Plain arithmetic
col.linetotal.type=number
col.linetotal.formula={weight} * {shipprice} * 1.10
Concatenation
col.label.type = string
col.label.formula = {company} + " " + {shipaddress} + " " + {contactperson} + " " + {weight} + "lbs"
Conditional
col.linetotal.type=number
col.linetotal.formula=if( {shipaddress} =~ ["London", "Birmingham"]) { {weight} * {shipprice} * 1.10 } else {{weight} * {shipprice} * 1.50 }
The formal specification can be found on Formula - formal syntax specifications and of course, examples are always helpfull : Formula - Examples
Bug fixes and improvements
* [IGRID-1569] - columnid is not always case insensitive
* [IGRID-1826] - Sonar reports critical violations
* [IGRID-1845] - Default value applies instead of null after "Insert Rows" while updating/creating issue
* [IGRID-1853] - Checkbox can not be incell-edited in edit mode
* [IGRID-1859] - Strange number column value conversion while persisting
* [IGRID-1866] - Checkbox doesn't work when col.xyz.unchecked=false
* [IGRID-1867] - No grids on view issue page for IE9
* [IGRID-1869] - Changing tablename for DTG brings to unpredictable table usage [IGRID-1883] - Data loss scenario reappears
* [IGRID-1737] - Add prefixes to column input ids to avoid collisions with Jira HTML element ids
* [IGRID-1813] - Redirect for "Log In" button
* [IGRID-1819] - Performance improvements for calculated columns
* [IGRID-1882] - Summary is not rounded
Final 1.9.0 release which includes compatibility with Jira 6.0 and a small bug fix on the XML view of a grid.
We are looking for beta testers for our next release (1.10) which will include the capability to create calculated columns (ie. line totals and such). Interested - send us a mail : support@igrid.info.
Compatibility with Jira 6, and a number of bug fixes in the area of cascading columns
* [IGRID-1563] - XML view must encode data else we get rendering errors
* [IGRID-1695] - NULL in cascade_child_name column after edit popup
* [IGRID-1696] - Option name in cascade_child column after edit popup cascading
* [IGRID-1697] - Empty string in cascade_child_name column after in-cell edit cascading
* [IGRID-1698] - Value for cascade_parent column is not changed by in-cell editing
* [IGRID-1749] - JSON.parse error while cascading.
* [IGRID-1769] - Population column from custom field doesn't work
This version for our customers who are on Jira 4.4
Version 1.9.0 of the plugin (which is compatible with Jira 5 and Jira 6) contains all these fixes
* [IGRID-1563] - XML view must encode data else we get rendering errors
* [IGRID-1695] - NULL in cascade_child_name column after edit popup
* [IGRID-1696] - Option name in cascade_child column after edit popup cascading
* [IGRID-1697] - Empty string in cascade_child_name column after in-cell edit cascading
* [IGRID-1698] - Value for cascade_parent column is not changed by in-cell editing
* [IGRID-1749] - JSON.parse error while cascading.
* [IGRID-1769] - Population column from custom field doesn't work
New feature introduction - driving table support
Are you using lists of values in your table grid editor and you want a simple way to manage these lists, check out the driving table editor. The driving table editor allows you to configure, create and manage lookup values. These lookup values can be reused to initialize lists and grids as required.
Now it is really easy to manage product lists, survey questions, release numbers ...
This release contains following enhancements and fixes
* [IGRID-1427] - Merge of static and prepopulated rows does not work properly
* [IGRID-1429] - When accessing an issue create form 'full screen', grid doesn't show
* [IGRID-1489] - Radio button name is stored in DB instead of value
* [IGRID-1552] - Empty value for a date in popup if no defaultDate and DefaultValue defined.
* [IGRID-1553] - col.query.parameters causes an unreasonable error when creating an issue
* [IGRID-1561] - Refresh grid on create issue screen with a user or project query parameter causes NPE
* [IGRID-1562] - System locale conflicts with client-side date value validation
* [IGRID-1584] - Oracle ds, textarea and "Duplicate row" button
* [IGRID-1588] - Oracle ds, textarea and "clear all duplicates" button
* [IGRID-1042] - col.xyz.required=true permits empty row edition with "insert rows"
* [IGRID-1357] - bogus where clause doesn't provide necessary detail such that user can correct
* [IGRID-1412] - Security Level restricted issues are still accessible through the grid search facility
* [IGRID-1419] - A query starting from parenthesis causes NPE
This release contains following enhancements and fixes
* [IGRID-1427] - Merge of static and prepopulated rows does not work properly
* [IGRID-1429] - When accessing an issue create form 'full screen', grid doesn't show
* [IGRID-1489] - Radio button name is stored in DB instead of value
* [IGRID-1552] - Empty value for a date in popup if no defaultDate and DefaultValue defined.
* [IGRID-1553] - col.query.parameters causes an unreasonable error when creating an issue
* [IGRID-1561] - Refresh grid on create issue screen with a user or project query parameter causes NPE
* [IGRID-1562] - System locale conflicts with client-side date value validation
* [IGRID-1584] - Oracle ds, textarea and "Duplicate row" button
* [IGRID-1588] - Oracle ds, textarea and "clear all duplicates" button
* [IGRID-1042] - col.xyz.required=true permits empty row edition with "insert rows"
* [IGRID-1357] - bogus where clause doesn't provide necessary detail such that user can correct
* [IGRID-1412] - Security Level restricted issues are still accessible through the grid search facility
* [IGRID-1419] - A query starting from parenthesis causes NPE
Important Note
This is the last release which is compatible with Jira 4.4. Our next release (1.8) will contain a new feature which depends on active objects, which is only properly supported in Jira 5 and higher.
Of course we will keep delivering bug fixes until EOL of Jira 4.4
Criteria based grid search
This release contains a major new feature - demanded by about every customer - searching through the grid data. With version 1.7 of the table grid editor you can specify a JQL using the grid function, allowing you to select these issues with particular values (or combination of values) in the grid
For instance
issue in grid ("checklist", "status = 'Open' and due < now()")
Check for more details the page about the Criteria based grid search.
Create panel is updated correctly when switching project/issue type
When using Jira 5 or higher, the grid was not displayed when switching project or issue type.This has now been fixed.
col.xyz.width is now respected
In previous versions, the col.xyz.width was not respected in all cases. This has been rectified. Take into account that this might impact some of your existing grids - so check the grids (and the popup forms) after your upgrade.
Other issues addressed in this release
Criteria based grid search
This release contains a major new feature - demanded by about every customer - searching through the grid data. With version 1.7 of the table grid editor you can specify a JQL using the grid function, allowing you to select these issues with particular values (or combination of values) in the grid
For instance
issue in grid ("checklist", "status = 'Open' and due < now()")
Check for more details the page about the Criteria based grid search.
Create panel is updated correctly when switching project/issue type
When using Jira 5 or higher, the grid was not displayed when switching project or issue type.
This has now been fixed.
col.xyz.width is now respected
In previous versions, the col.xyz.width was not respected in all cases. This has been rectified. Take into account that this might impact some of your existing grids - so check the grids (and the popup forms) after your upgrade.
Other issues addressed in this release
Main focus of this release was to provide inline edit capability.
When using Jira 5.1 or higher, you can edit the content of the table grid while viewing the issue.
Bugs fixed in this release
* [IGRID-1153] - Row is added twice when user enters 'return' when the focus is on the 'submit' button
* [IGRID-1190] - When an issue cannot be inserted due to a duplicate issueid, the validation error flags that the table couldn not be created or updated
* [IGRID-1232] - Customfield dependent lists and lists with non-parameterized queries interaction
* [IGRID-1243] - igrid_test cannot access databases in the automated test scenario
* [IGRID-1254] - Fix for the CascadingColumnsJiraCase testcase
* [IGRID-1255] - Testcases fail on ElementNotVisibleException
* [IGRID-1259] - issue:type is unknown when creating an issue
* [IGRID-1299] - Column heading is not showed
* [IGRID-1300] - grid view mode - due to inline edit, grid can be refreshed but not maximized
* [IGRID-1308] - Documentation flaw: datasource.names=gridds is not mandatory
Improvements provided
* [IGRID-758] - issue value parameters must include issue:type
* [IGRID-1115] - Column id must be unique
* [IGRID-1121] - Remove the tracking fields from the edit form
* [IGRID-1197] - Use the correct logo in UPM
* [IGRID-1247] - Distinguish between refresh and reload ...
* [IGRID-1268] - Display a warning when the pluginlicensestorage component is missing
Main focus of this release was to provide inline edit capability.
When using Jira 5.1 or higher, you can edit the content of the table grid while viewing the issue.
Bugs fixed in this release
* [IGRID-1153] - Row is added twice when user enters 'return' when the focus is on the 'submit' button
* [IGRID-1190] - When an issue cannot be inserted due to a duplicate issueid, the validation error flags that the table couldn not be created or updated
* [IGRID-1232] - Customfield dependent lists and lists with non-parameterized queries interaction
* [IGRID-1243] - igrid_test cannot access databases in the automated test scenario
* [IGRID-1254] - Fix for the CascadingColumnsJiraCase testcase
* [IGRID-1255] - Testcases fail on ElementNotVisibleException
* [IGRID-1259] - issue:type is unknown when creating an issue
* [IGRID-1299] - Column heading is not showed
* [IGRID-1300] - grid view mode - due to inline edit, grid can be refreshed but not maximized
* [IGRID-1308] - Documentation flaw: datasource.names=gridds is not mandatory
Improvements provided
* [IGRID-758] - issue value parameters must include issue:type
* [IGRID-1115] - Column id must be unique
* [IGRID-1121] - Remove the tracking fields from the edit form
* [IGRID-1197] - Use the correct logo in UPM
* [IGRID-1247] - Distinguish between refresh and reload ...
* [IGRID-1268] - Display a warning when the pluginlicensestorage component is missing
* [IGRID-1218] - GRID Triple - Grids on additional tabs are not loaded
* [IGRID-1225] - Like '%{0}%' doesn't work for column queries
* [IGRID-1227] - Grids prepopulated on transition WF screen doesn't Work
* [IGRID-1218] - GRID Triple - Grids on additional tabs are not loaded
* [IGRID-1225] - Like '%{0}%' doesn't work for column queries
* [IGRID-1227] - Grids prepopulated on transition WF screen doesn't Work