Unable to use Parent in Two Dimensional Gadget (new Gen JIRA project)

Sapna Mogili

Unable to select Parent in X / Y axis in New Gen JIRA Projects in Cloud version in Two Dimensional Gadget, something similar to EPIC Link in Classic Projects used in Two Dimensional Gadget data

Ste Wright

Hi @Sapna Mogili 

Best option I've found it to use a workaround - in this case, a custom field and an automation rule

----------------------

What I did was:

• Add a custom label field to the Epic - "Epic Reference"
• Populate the "Epic Reference" for each Epic with a short name (manually)
• Add the same field to each child issue type
• Populate "Epic Reference" on child issues using an automation rule

The custom label field can be used on the dashboard gadget. You could also use a drop-down field if you prefer not to have underscores or hyphens in the names, although an Admin would need to add options each time a new Epic is added.

----------------------

The automation rule is a little more complex than usual. I'd usually use "Issue Updated" as the trigger, but a parent change in Next-Gen isn't classed as an update. Neither can you check for a modification to the parent itself.

These are the two options I found.

----------------------

Option 1 - Second Field:

1. Go to Project Settings > Issue Types
2. Create a custom field on a child issue - I used a checkbox. Give it a name/option related to automation, such as Automation (name) Activate (option).
3. Place the custom field on all child issue types
4. Next, go to Project Settings > Apps > Project Automation
5. Press the "Create Rule" button in the top-right
6. For the Trigger, use Issue Updated
7. Add an Action, use Edit Issue - choose to set "Epic Reference" - and for the value, select "Copy from Epic"
8. Add a second Action, use Edit Issue - choose to set "Automation" (custom field from Step 2) - and for the value, leave it blank to clear it

^ The way this rule would work is:

• Change the parent for an issue
• When doing so, also "check" the custom field from Step 2
• The rule activates and copies the "Epic Reference" from the Epic to the child
• The second action removes the value from the custom field from Step 2 so it's blank again

I used a custom field rather than the trigger "Manual Trigger" as I could place the custom field at the top of the context section - whilst automation is a fixed section part-way down the page.

----------------------

Option 2 - Schedule:

1. Go to Project Settings > Apps > Project Automation
2. Press the "Create Rule" button in the top-right
3. For the Trigger, use Scheduled - schedule the rule within a timeframe (eg. every 1 days) - and check the "Run a JQL search..." box. Use the JQL: issuetype != Epic
4. Add an Action, use Edit Issue - choose to set "Epic Reference" - and for the value, select "Copy from Epic"

^ The way this rule would work is:

• Each time the rule is scheduled to run, it would locate all issues which are not Epics
• It would then copy the "Epic Reference" from the parent Epic to all children
• This rule will run a little slower as it'll be checking / actioning against a lot more issues. There might also be a delay between a parent change and "Epic Reference" update, depending on when you schedule the rule to run
• But, it is more automated than Option 1 - and it can be run manually from the automation settings screen if needed

----------------------

This isn't an ideal option - it relies on you creating a custom field, which you set manually at Epic-level and then uses one of two automation rule options, neither of which utilise direct triggers.

But it does allow you to use Next-Gen and receive the result in the Two Dimensional Filter Gadget you're looking for

Ste