Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
Qlik-Developer
Creator
Creator

Qlik Sense Rest API Connector for Jira/Getting custom fields with their names from jira to Qlik

Hi Everyone,

Good Evening,

My source is jira, Loaded data from Jira through REST API into qlik sense, while loading Issue table custom fields are loading into Qlik like Custom filed ids as lable, so its difficult to identify what is the actual filed name from jira.

Due to requirement in project few field were added in Jira by Jira developer those fields called custom fields. These newly added fields by Jira developer are coming into qlik as custom filed with id (ex: custom field 250,custom filed 340).

While creating the REST connection defined the filed names in the parameters, even though custom filed with ids are loading.

Do i missed something while loading,please help on this.

Thanks in Advance!!!!!!!!!!!

 

Varsha.

 

 

 

Labels (2)
119 Replies
Qlik-Developer
Creator
Creator
Author

After entering a string in Jira,When i load data into qliksense 100's of custom filed tables are appearing under select data to load ,so to find the string  what i entered in jira do i need to load all the custom tables appearing under select data to load?

stevedark
Partner Ambassador/MVP
Partner Ambassador/MVP

The thing to do is create a new app and use the Select Data wizard and load all of the data from the connector. Enter a unique value into all of the columns you want to take. Delete all of the residents loads from the load script before reloading. Once the data is in you can use the global search to find the custom_xxxx fields for all of the values you want. Once you have these you can build the statement you need to pull just the fields you want and create mapping tables to give them the right values with the right names.

It's a bit long winded, but hopefully you will be able to get to where you need to.

Qlik-Developer
Creator
Creator
Author

Where the data wizard option will available? do you mean it is data manager?

 

 

stevedark
Partner Ambassador/MVP
Partner Ambassador/MVP

Just when you click Select Data next to the connector on the right hand side. You can select to bring in the root table and all tables beneath it in one go.

Qlik-Developer
Creator
Creator
Author

we need to enter unique value in jira while creating a ticket.

stevedark
Partner Ambassador/MVP
Partner Ambassador/MVP

You don't need to, but it can make the column easier to find.

Qlik-Developer
Creator
Creator
Author

then where we have to enter unique values into all of columns?

stevedark
Partner Ambassador/MVP
Partner Ambassador/MVP

It's not a necessity to enter unique values anywhere, you just need some way of being sure that you have the correct custom field. By entering values into Jira that will pull through via the API you can be sure when you find that value in Qlik that you have the correct column.

Qlik-Developer
Creator
Creator
Author

Thing is  "story points"  field is created by jira developer so its custom field from jira.but when i tried to create ticket "story points" filed  column is not coming to enter the string for easy identification of columns in qlik.

stevedark
Partner Ambassador/MVP
Partner Ambassador/MVP

Yes, I see the problem. In a feed I pull from the Story Points are in a custom field in the main body of the request (which means no ApplyMap is needed for that field):

alt(customfield_10026, 0) as [Story Points],

Obviously, the custom field will not necessarily have the same suffix.

As the field can only contain an integer value it will not be possible to put in a string that you can search for. In that case you will need to pick a ticket with story points on it and select it in the data. Then search for all of the fields that have that value. Then create a table with Ticket ID and all of the fields which were a match for that one ticket and find which of those fields are most likely to be the story points field.

The fact it is in the main body of the data, rather than joined with a FK, should make it a lot easier to find.

Good luck!