Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Epic Link field option missing under Jira Linked Field list in ProForma-- any workaround?


Bit of context: Setting up a couple forms for easier issue generation and within my team's project we're requiring epic links for a majority of the issue types. 

I've had no issues linking other ProForma fields to existing & custom Jira fields, but when navigating through the Linked Jira Field list in the ProForma form builder, there is no option for epic link. 

The Epic Link field is present in the issue type this form is associated with, and I've tried the steps outlined here: to no avail.

I've also investigated the automation options within ProForma to see if there is a way to pre-set the epic link field upon issue creation but in-app automation options are fairly limited.

Has anyone run into a similar issue / is there a workaround for this? As it currently stands since one required field isn't showing up as a linkable option the entire form can't be submitted.


1 answer

1 vote
John Funk Community Leader Dec 22, 2021

Hi Chelsea - Welcome to the Atlassian Community!

What type of project is this? Company-managed? Team-managed? Jira Work Management? Jira Service Management?

Hey John-- thanks for the welcome, it's a Team-managed project. I'm in the process of trying to migrate issues & forms from a Service Management project into this Team-managed one and the above issue is one of the hurdles I'm facing. 

John Funk Community Leader Dec 22, 2021

Ah, suspected as much. Team-managed projects do not use the Epic Link. See if you can find the Parent field - that is what is used instead. 

Ah I see, thank you! I'll follow-up with my Jira Admin to see if they can let me know what that Parent field is. 

Once it's been determined, I should be able to link the ProForma field to the Parent field and that would satisfy the epic link requirement right? Or would it be changing the Epic Link requirement to a requirement for the Parent field and then linking that field in ProForma?

John Funk Community Leader Dec 23, 2021

To be honest, I have not used team-managed projects much. And definitely have not tried with the parent field with Forms like this. 

All good, your input has been super helpful-- still waiting to hear back from my admin, but I'll update this incase anyone else runs into a similar issue. Thanks again and happy holidays!

Like John Funk likes this


Did anyone get this to work (i.e. having a Bug created from a Form with a default Epic Link set) ?

In my Company-managed project, I have created a "Long Text" question on my Form, however "Epic Link" is not an available option in the "Link to Jira Field" dropdown.  

It has "Epic Name", but I'm unable to have that accurately set the Epic Name or Epic Link value when creating a Bug.

I tried the workarounds in the original link with no success.

I tried the same exact thing but it doesn't work

I am trying the same getting a bug to link to an epic upon intake and the only solution i can see available (but fails) is to prepopulate the "Epic Link" field with a default of the literal Epic Name .  Issue key is not available for selection ... Also tried hardcoding the URL of the issue (epic) but the jira fields dont map to urls..  Other ideas welcomed.  This is a software project that I'm an admin of.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events