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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Why am I not allowed to add the Epic Link to a JSD request form?

One of my users wants Jira Service Desk portal form to allow customers to specify an epic link. 

I am aware that Epics are usually associated with Jira Software and so is my user. I believe the use case is that a knowledgeable customer, who (presumably) has access to jira software, would create an issue in the portal and then associate it with an epic (presumably in a software project).

Whether this is a good idea or not, I found that I could NOT add the epic link field to the visible part of the form. I got a message "This field type cannot be shown - you must provide a preset value". I could add it ONLY if I gave it a preset epic link. This is true even though I added the epic type to the project. 

Can you tell me WHY I can't add an epic link to the visible part of the form and/or how I might accomplish this? 

2 answers

1 accepted

1 vote
Answer accepted


As that message indicates, you cannot add the Epic Link field to the portal forms. It's just not possible.

There are certain activities which customers will not be able to do, and this is one of them.

The answer "you can't do it because it can't be done" is not very satisfying but I think it's the correct answer. 

Hi @Dave Menconi ,

I think it is not possible because it doesn't make any sense.

Even if you would be able to add the field, the customer would not be able to select an epic, because they don't have access to them  they can only access their own request or the ones shared with them.

Thanks for your answer. I agree that it makes little sense to ask customers to who don't have access to epics to identify them. And the people who DO have access to the epics can simply open the issue afterward and add the epic, if they so choose (and have the privs). 

But I think the point was that SOME of the people who would be creating issues in the portal DO have access to the epics and that allowing them to add the epic in the portal, all in one operation instead of two, would be useful.

Still, it's hardly a significant hole in the system. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

209 views 1 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you