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

Create Linked Issue vs. Create Issue Screens



I have a Jira Service Desk and several Jira Software projects and when I am in a Service Desk ticket and I use the Create Linked Issue option/form, the fields are different than when I use the Create Issue form for the same project.


The Create Linked Issue contains only a handful of fields and the Create Issue form contains many fields.


I'm having a hard time finding what scheme/form I need to update to include additional fields in the Create Linked Issue form.



2 answers

1 accepted

1 vote
Answer accepted

Hello @Lisa Tritt

Thank you for reaching out.

Indeed, it is not possible to change the fields displayed when creating linked issues. We understand how useful this functionality would be, so we created the following feature request:

As an administrator, I want to be able to change the create linked issue screen 

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

For now, the workaround we have to enforce a field to be displayed in the Create Linked issue screen is to first add it to the create issue screen relevant to the project and
then, in the field configuration, configure the field as "Required".

Let us know if you have any questions.

@Petter Gonçalves Can you please elaborate on

first add it to the create issue screen relevant to the project and then, in the field configuration, configure the field as "Required".


We are trying to do this and are not clear which project needs this adjustment?

Hello @Janene Pappas

You will need to apply those settings to all the projects/issue types you want to link issues. Basically, a required field enforces your link issue to open the complete create issue screen.

Giving you a practical example, let's suppose you have an issue in project A, and you want to create a new linked issue in project B. To ensure a specific field will be displayed when clicking to create a linked issue, you must:

  1. Navigate to Project B > Project settings > Screens > Make sure the field is added to all the screens
  2. Under project settings > Fields, ensure you configured that same field as Required

Let us know if this information helps.

Thank you Petter, that does help.

You are welcome @Janene Pappas

Have a nice day and let us know if you face any other questions.

Just another perfect engineering solution from Atlassian. I am so tired of these things, they are just everywhere.

Hello @Denis Zvonov

Thank you for reaching out.

I just would like to say that the workaround steps provided are not the solution to any problem or limitation. They just provide a possible way to edit the linked issue screen, however, we are tracking the real fix for this limitation in the mentioned feature request.

That being said, the workaround provided was not meant to discourage or low the priority to address that limitation, but to simply provide you with a possible way to avoid that limitation, although it might not work for some use cases.

Let us know if you have any questions about that.

Like Denis Zvonov likes this

Hi @Petter Gonçalves 

Actually your answer is the one and only thing Atlassian did regarding this issue. Better than nothing for sure, many other problems with JIRA don't have even a workaround. If you look at this ticket you will see that in almost 5 years - no progress.

And there are dozens or even hundreds of them. Obviously Atlassian has disinvested in the Server and DataCenter platform. Atlassian will regret.

Like Ryan Rosenthal likes this

Over two years after still no resolution... Why is Jira still advised by anyone as the go to solution for issue management still surprises me.

Sorry Atlassian, you had the lead, but you got greedy and you are now well behind your competition.

Like Jorge Fonseca likes this



All good and well, but this work around only works for custom fields and not for system fields.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events