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.
Here is one community post you can check as an example:
On Jira cloud, this is the only way how to access Epic Link value. There might be a slight modification for the same formula (Epic link has a bit different data structure in Issue JSON than single select custom field):
You would like to use Epic Link custom field ID instead of NNNNN. I used parent_issue_key as a parameter to pass down value from parent issues to sub-tasks.
On Jira server, I would suggest using a different option. We have an additional option to access Epic Link via issue links in Jira server. Issue link field import gives additional options to see the dimension similarly like issue dimension.