Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


Table Transformer - Transforming entire table

Federico Botero
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Nov 16, 2023

I have been fighting with this for days without a satisfying result.

I am loading data from Jira and need to transform it with Table Transformer to fit my needs.

Example and columns:

Key | ABC-657 (if S=Parent) or AAA-657 AAA-658 (If S=Child)

S | Parent or Child

Parent Key | ABC-657

Sponsor | Super Sponsor (SSAB)

Labels | #AA-Type or AA-Type or AA-TYPE

Description | Long Text Long Text Long Text Long Text Long Text Magic Sentence 1 Long Text Long Text Long Text Long Text Long Text Long Text Long Text Long Text Magic Sentence 2 Long Text Long Text Long Text Long Text Long Text Long Text


STEP 1 (Works fine): SELECT TOP 2 'Key', // just for testing purposes

STEP 2 (Works fine): CASE WHEN 'Labels' LIKE "%AA-Type%" THEN "AA-Type" ELSE NULL END AS AA-Type,

STEP 3: For 'Description' column, flatten the text VARCHAR
Then RETURN the String Between string "%Magic Sentence 1%" and string "%Magic Sentence 2%". ELSE IF String not Found THEN "Formating error" AS 'Short Description'

STEP 4: Hide 'Description' and 'Short_Description' column // to improve performance for testing.

STEP 5: COUNT CHAR 'Short_Description' AS 'SD_Count'. IF 'SD_Count' NULL OR <155 THEN "Description needs fixing" AS 'Error' ELSE "Description OK"

STEP 6 (Works fine): IF 'Sponsor' NOT NULL THEN
IF 'Parent Key' not NULL then

This code applies for 2 Tables which are then joined and a new Table transformer comes in:
Same Columns.

STEP 1: If 'Sponsor' NULL AND 'S'="Child", THEN MATCH value of 'Parent Key' with All values in column 'Schlüssel'. IF MATCH THEN RETURN Value for 'Sponsor' of matching row. ELSE IF 'S'="Parent" THEN Return value for 'Sponsor'. ELSE if no match THEN "Error - no Sponsor" AS 'Sponsor Short'

Step 2: IF 'S'="Parent" MATCH the value in 'Key' with all values in column 'Parent Key'.
IF No match, THEN "No Children" ELSE RETURN COUNT of MATCHES AS 'Children'


1 answer

3 votes
Stiltsoft support
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 16, 2023

Hi @Federico Botero ,

Better refer to our support. Attach the page storage format of your page (upper right corner -> menu ... -> View storage format), so we'll be able to recreate your macros and their SQL queries. And attach the screenshots of your Jira Issues macros (in a published state with visible headers and 4-5 rows of data) - these tables won't be recreated via the page storage.

In general, you may use the SPLIT function to split your string by your "magic sentence" markers (if they are stable across the column). For example, you may check the last reply of this Community thread.

To hide specific columns, you just need not to list them. I mean use not "SELECT * FROM ...", but "SELECT 'Column 1', 'Column 2' FROM ..." - here you list all the columns that need to be seen. But, as later you refer to them, you need to do it in the last (external) Table Transformer macro.

To count the length of your descriptions, you may use the LENGTH function. The previous link leads to a SQL simulator and here you may see an example of this function inside the Table Transformer macro. The statuses are set with the help of the CASE WHEN statement that seems to work fine for you on the Step 2.

Hope I was able to give you (and other users who will come across this question) some useful hints.

What concerns the last two steps when the second table is added, here I got confused without the real visual data. :) So, let's move to the support where you will be able to share your real screenshots - seems that it should not be that complex.  

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events