Adding a new hierarchy based on a custom field defined in Epics

Questions & Answers
1

Hello,

I’m trying to define a new dimension, to group Epics in a kind of work package. We have a custom field of type label (multiple values) that is set for Epic issue type.

The objective is to be able to use it as a hierarchy as : Work Package → Epic → …

I have used the samples proposed : Additional Issue hierarchies - eazyBI for Jira

But, my main problem is that I was able to use it for Epic level, but it’s not cascading to sub issues.

Could you please advise ?

BR

2

Hi @RCi!

eazyBI supports inheriting down in hierarchy single value fields. The use case of the multiple value custom fields falls within a narrow area where there are not too many good suggestions as to create issue link field dimensions or hierarchy in Issue dimension.

Nevertheless, I can suggest you force the inherited Work package to be a single value field (comma-separated list of values). You can do this with the following setting; make sure to use the correct Work package ID instead of NNNNN.
Add following advanced settings to create a new field that inherits the work packages down from epic.

[jira.customfield_epicWP]
name = "Epic Work packages"
data_type = "string"
dimension = true
multiple_values = false
update_from_issue_key = "epic_key"
javascript_code = '''
  if(issue.fields.customfield_NNNNN) {
    issue.fields.customfield_epicWP = issue.fields.customfield_NNNNN;
}
'''

This field can also be used in the hierarchy:

[[jira.issue_hierarchies]]
name = "Epic Work packages"
all_member_name = "All Issues by fruits"
levels = [
  {name="Work packages",key_column="customfield_epicWP"},
  {name="Epic",key_column="epic_key"},
  {name="Parent",key_column="epic_parent_key"},
  {name="Sub-task",key_column="subtask_key"}
]

Lauma / support@eazybi.com

3

Hello @lauma.cirule ,

Thanks for the response. While testing it, I have such error when importing :
«no implicit conversion of ThreadSafe::Array into String»

The custom field has been turned to a single line text field, so no more multiple values can be define here.

any advice ?

here is the custom field value from rest api :
image

4

@RCi, Sorry for the trouble!

I would need a more detailed error message from the log files. Could you please send me the eazyBI log. You can send them via email (support@eazybi.com) or upload them in our contact form.

Please add which steps you have performed so far and when you get the error? Also, add the link to this conversation, so we don’t miss the beginning of the conversation.

Lauma / support@eazybi.com

5

Hello @lauma.cirule

Sure, mail sent to the support.

BR

1 Like