What table the JMCF custom field value is stored in jira database?

[Pedro Paulo da Silva]

I am struggling to find the JMCF Transition Date/Time custom field value in jira database.

I tried in customfieldvalue table, but no way. I got others types but none of them were from third parties

I wanna write a sql to export my issues to my power BI model using PBI Data Flow.

thanks

[David Fischer]

Hi @Pedro Paulo da Silva 

JMCF offers calculated fields, which means that these fields are not stored but calculated on the fly (because their value can change at any time). You therefore won't find their value in the Jira DB (or anywhere else). They are, however, accessible through the Jira REST API, or through Jira DC's Data Pipelines feature, which is the recommended way to synchronize Jira with a data warehouse.

[Pedro Paulo da Silva]

Hi David,

Thanks for replying. I knew calculated fields are not stored, but I was hoping to find others non calculated types like JMCF Transition Date/Time in database.

Unfortunaly, Data Pipeline is only for Data Center. My version is Jira server 8.20.2

[David Fischer]

Hi @Pedro Paulo da Silva ,

since Atlassian is retiring its Server products, you'll soon be migrating to a single-node DC license, which will make Pipelines available to you.

[Nic Brough -Adaptavist-]

Depends on the specific type of the field, and the content may be smeared across 1-4 tables too.

Your best option for reporting on JMCF fields, and other types, is to stop looking at the database and use the REST API, or use apps that understand it so you don't have to.

The database is a nightmare, and you're just making life hard for yourself.

[Pedro Paulo da Silva]

Hi Nick,

Thank for replying. We already deliver analytcs services using API, but we are facing performance problems loading large volumes calling rest/api/2/search.  We also have EazyBI, but most of users work with power BI solutions.

We have succeed loading diretcly from database for years in our old tibco spotfire solution. Working with the tables was not a issue until we wanted to get some special types like JMCF Transition Date/Time.