Hi @karim ,
I don’t recommend defining such calculated members in the Issue dimension. They are a performance risk.
If you don’t have the option to create a new custom field in Jira, define a new JavaScript calculated custom field in eazyBI. See more details on how to do that here - JavaScript calculated custom fields - eazyBI for Jira.
Add parameters similar to the one below to your eazyBI advanced settings:
[jira.customfield_developer_issue]
name = "Issue summary Developer"
data_type = "string"
dimension = true
javascript_code = '''
var result;
if (issue.fields.summary && issue.fields.summary.match(/.*developer.*/)) {
result = true;
} else {
result = false;
}
issue.fields.customfield_developer_issue = result;
'''
This particular JavaScript custom field will return the value “true”, if the issue summary has the word “developer”. Alter the parameters to fit your use-case.
You can then update the eazyBI advanced settings and select the newly defined custom field for import as a dimension in the import options. Finally, you can use the dimension in the pages of the report to filter the report results. See an example below:
Best,
Roberts // support@eazybi.com