Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


[Video] Better support for Jira multi-valued fields

Hi all, we have introduced a change in the “Jira Issue Field” table in the Atlassian Data Lake to better handle and improve usability for multi-valued fields. Keep reading to learn more about this change and how it impacts you.


What is changing

Previously, if you have a Jira field that contains multiple values (lists or cascading fields), it was difficult to query or join that data in Atlassian Analytics because the values were in a single string (e.g. [10022,10027,10028,10029]). With this change, the values have been extracted into multiple rows and their option ID’s translated to the actual values to make it easier to consume and be used in charts.

The affected field types are listed as follows:

  • Select List (multiple choices)

  • Checkboxes

  • User Picker (multiple users)

  • Group Picker (multiple groups)

  • Version Picker (multiple versions)

  • Select List (cascading)

  • Request participants

  • Organizations


What to expect

This improvement is available now, so you can start seeing the changes in the “Jira Issue Field” table in your Atlassian Data Lake connection.

For multi-valued fields, when you query them their results will depend on the type of field:

  1. When a certain field contains more than one value, instead of one record that has all the values, multiple records will be returned by the query, one for each value within the field. For example, [10332,11734,10243] will return one record with the value 10332, another with the value 11734, and another with the value 10243.

    Issue Field Name Field Value 
    TIS-42 Record  10332 
    TIS-42  Record  11734
    TIS-42 Record 10243
  2. For multi-valued fields that are based on field options, the field value will be translated to the corresponding string value. For example, instead of [10332,11734], there will be one record with the value value1 corresponding to 10332, and another record with the the value value2 corresponding to 11734, assuming the field options mappings 10332->value1, 11734->value2.

  3. Cascading fields have parent and child values. For those fields, instead of a single record that has both values, there will be one record with (parent) appended to the field name, with the parent value (with the translated field option), and another record with (child) appended to the field name, with the child field value (with the translated field option). For example, instead of seeing a field called “cascade” with the value {"parent":"10118","childOption":"10121"}, customers will see one row with a field name cascade (parent) with the option value corresponding to 10118 (for example, Fruit), and another row with a field name cascade (child) with the option value corresponding to 10121 (for example, Mango).
    Field Name  Field Value 
     cascade (parent) Fruit 
     cascade (child) Mango


Arik, an Atlassian data scientist, recorded a video demonstrating how to query Jira multi-valued fields using Atlassian Analytics.


If you have any questions or concerns, please comment below and we will get back to you. Thank you!



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events