Hi @tz_ger ,
Welcome to the eazyBI community. I am sorry your post didn’t get any input sooner.
Your workaround with scripted fields is a good alternative. With eazyBI, you can create a similar solution by defining a new JavaScript calculated custom field that passes a custom field value from Epic down to its children.
You can see two such examples in the linked eazyBI community posts below:
Issue link field dimension feature is in high demand. However, it applies to some Jira default fields only ( Fix Version, Label, Status, Resolution, Issue type, Priority ). We update a list of supported fields on our documentation as well.
Here are other options on how you can achieve the same with other options. It is limited to any Single value dimensions and values only, though.
You can use update_from_issue_key as an additional parameter for any field to pass down values to other issues. W…
Hi @adr-glz ,
Yes, the code looks all right and should work. You may slightly improve the look of code by moving up the parameter update_from_issue_key leaving the JavaScript code the last parameter.
[jira.customfield_wt_inherited]
name = "Work Type Inherited"
data_type = "string"
dimension = true
update_from_issue_key = "epic_key"
javascript_code='''
if (issue.fields. customfield_12345) {
issue.fields.customfield_wt_inherited = issue.fields.customfield_12345
}
'''
Probably it is a coinciden…
You can find more details on JavaScript calculated custom fields here - JavaScript calculated custom fields .
Let me know if you have any questions regarding this.