What's new with 4.0.0-RCv2?
Compatible with Jira Software 8.0-8.1
Minor bug fix for White Space
1. Log into your JIRA instance as an admin.
2. Click the admin dropdown and choose Atlassian Marketplace.
The Manage add-ons screen loads.
3. Click Find new add-ons from the left-hand side of the page.
4. Locate Tables via search.
The appropriate add-on version appears in the search results.
5. Click Try free to begin a new trial or Buy now to purchase a license for Tables.
You're prompted to log into MyAtlassian. JIRA Tables begins to download.
6. Enter your information and click Generate license when redirected to MyAtlassian.
7. Click Apply license.
If you're using an older version of UPM, you can copy and paste the license into your JIRA instance.
In the Custom Fields sections of JIRA Administration, select “Add Custom Field” and then select the “Tables Custom Field” option.
After giving the custom field a name and selecting the applicable contexts, go back to the Custom Fields section of JIRA Administration and select “Configure” in the options dropdown of the newly created Tables custom field. Then select "Edit Default Value".
You are now in the configuration view of the Tables custom field. From here you can Edit the Configuration to determine which Projects and Issue types will use Tables and Edit Default Values for your Table.
Let’s start out by Editing Default Values for our table. Click the hyperlink to Edit Default Values. You should now see the screen for editing the default values for your table. From here you can name your columns, choose the column types, set default values, set a default width for each column, determine whether each cell in the column requires a value (is not null), and if the column is a dropdown, define the enums for the dropdown. Note that every column requires a Column name. In the screenshot below the column name is highlighted in red indicating that a required value is not present in that cell.
For demonstration purposes, we'll make a text column. First, Give the column a name, type, a default value (optional), and determine whether a value is always required for this column. Note that if a value is always required, you must have a default value set in the configuration screen. Otherwise the "Default Value" cell for that column not pass validation and will be highlighted in red, indicating that the cell values did not pass validation.
A table with one column is not very useful, so let's continue by adding a column. Right click on the table, and a menu with options will appear. From this menu you can Insert Row Before (adds a column before), Insert Row After (adds a new column after), Remove Row (if there is more than 1 row in the table), Undo your last action, or Redo (reverts from your most recent Undo).
When your tables are displayed in your tickets, the columns will populate from left (row 1) to right (rows 1+n). Let's add a second column after the first we created by clicking insert row below. A new row will appear in the configuration table below our original row, For demonstration purposes, we'll make the type of this column a dropdown. Select "dropdown" from column type, set your default width, determine whether the dropdown is required by checking the box or not required by leaving it unchecked. To enter the options for our dropdown, we will use the standard format ['Option 1', 'Option 2', 'Option 3']. In the dropdown the options will be listed top-down as they are entered left-right in our enumeration. If we have chosen to not have a value be required, we do not need to enter a default value. However, if we have required data for that column, we must enter one of the values from our drop-down list, without the single quotes. (i.e. Option 1). If you do not enter a valid list, do not enter a valid default value the cell will highlight in red and when you try to set the default settings for the table by clicking the Set Default button, A message will pop up indicating which fields need to be corrected in order to set your defaults. JIRA tables also validates that the dropdown options have been formatted properly, and if they ware not will both highlight the Dropdown Options cell in red and provide a message notifying the user of the correct format to use.
After adding all of the columns that you need, enter in any default values that you want to be automatically displayed any time a user creates a new issue. Now just hit “Set Default” and your Table is all set!
To remove columns, just navigate to the configuration view right click on the column that you want to remove, and select “Remove Row” from the options in the right click menu.
Moving columns and rows is not currently available in JIRA Tables but you can delete and re-insert and if you use the same Column name the data will be preserved.
Searching your Tables data in JIRA 8.0 and up
Please note TEXT column type search is not currently supported.
When I export my JIRA data as an XML file will all of my Tables configurations and data be contained in that backup?
Yes! Because all Tables data is saved as a part of JIRA’s native custom field structure all of your configurations and content will be preserved and ready to use once restored.
What data types are supported?
Currently Tables entries can be configured as text, integers, dates, dropdown selections, and checkboxes.
Will my table be preserved when I clone an issue?
Yes! All data will be copied over to the cloned issue.
Will my data be preserved when upgrading to Tables 4.0.0-RCv2?
This Release is recommended for new users only. A subsequent version will be released in the near future to accommodate upgrades.
There are some things JIRA Tables 4.0.0-RCv2 will not do that we are aware of, which may be implemented in a future version/patch/release. We appreciate our user feedback and will continue to improve JIRA tables. For the current release, please note the following:
- This version is not backward compatible to previous JIRA versions.
- JIRA Tables 4.0.0-RCv2 is only intended to work on the "Main" page of JIRA Software without refreshing on tabbed pages.
- JIRA Tables 4.0.0 is only intended to work on Agent View for JIRA Service Desk, it will not render in the Customer Portal.
- This version has been tested for compatibility in Chrome, FireFox and Safari browsers.
- When multiple tables fields are added to one issue, the edit window defaults to the width of the narrower/shorter table.
If users find additional issues or other features they would like to see in JIRA tables, please submit a ticket via our Customer Support Portal.