Hi @jpf_sylob
If “release date” is the issue-level date picker custom fields, you could import the number of changes in the field and analyze it by Time periods when the field was changed.
Hi @BRoger ,
If date changes are fixed in the issue change history and available in the issue JSON object retrieved by eazyBI, then you may import this information in eazyBI as JavaScript calculated custom field.
For example, if you have some custom date field then you may use custom field definition with JavaScript like this:
[jira.customfield_xxx_changes]
name = "Number of XXX date changes"
data_type = "integer"
measure = true
javascript_code = '''
var fieldChanges = 0;
//go through issue ch…
and
Hi,
Date-picker custom fields can not be imported as dimensions in eazyBI.
eazyBI does not allow importing another dimension with date type since there is already one “Time” dimension by default.
A workaround would be using a pre-calculated field (using Javascript in advanced settings) that returns the string output for every issue with all the dates and new timestamp when it was changed (see attachment with table report)
Then using MDX calculated measure this timestamp is converted to Date…
Martins / eazyBI support