Happy New Year, everyone! May it be filled with joy, success, and - who knows - maybe even some miracles. Like Atlassian resolving to fix this bug. We can dream, right?

e3ea4b6190c9 
As long as you have mandatory fields, it doesn't matter if you use the create issue screen or a 4th screen.
You'll need those fields on the screen as you can define them only once as mandatory.
So we're talking only about showing optional fields on the screen or not, which you don't have to fill out, if you need to quickly raise a ticket.
In your case you would need a screen with a minimum of fields and the option to not care for the mandatory fields, which are not on the screen and create an issue without them.
As Atlassian couldn't manage over 8 years to just pop up a screen they already have and pre-fill the linked issue field there, your request really means rocket science to Atlassian and at least 10 more years to wait, i guess...

I do not fully agree with the latest statements, even if I can understand where they come from.

I'd expect a 4th screen in the schemes for create linked issue next to "view, edit, create", by default taking the create which would cover the before mentioned needs. 

But there are some cases where a little difference between linked issue and create issue screen is needed, easiest example is the linked issue field itself. Also there are cases within support for example, where an agent just needs to "quickly" create a linked task for DEV while talking directly to a customer and cannot provide the as needed marked fields DEV usually would require!

I agree with Bernhard G., that the best would be to just call the create issue screen for create linked issue and prefill the fields linked. That way it would be easy for any user, even with limited Jira knowledge, to create a linked issue without any complexity.

So 8 Years without a solution.

The fields are already there, they are just hidden, you can see with developer tools..

on "create-linked-issue-dialog" > "jira-dialog-content" > "qf-container" > "qf-form" > "form-body" > "content" > see the style of every field.

if you put "style="display:none"" to "style="display:block"" it works just as expected ...

Is it that hard to just display those fields?

Currently this is blocking us really much.
In Jira Server we where able to link Issues with "Create Task" in a normal issue. There we saw the "Create Issue Screen" and not the "Create linked issue Screen" that's why we did not had the issue there.

So it's just standard functionality that is not available in Cloud.

It's already working for the normal issue screen that the shown fields depending on the project you choose.
In my opinion it would be the easiest and best solution to use the create issue screen for create linked issue too and just fill out the issue link automatically.
At least for us I don't see any use case where I would need a different screen to create a linked issue than create an issue. It should just fullfill me the linked issue field - that's enough.

I guess that would already help a lot of people and couldn't be the rocket science as the screen already exists and just needs to automatically fullfill one field when it gets opended. Can't comprehend why this issue is already waiting since 2016.

@Atlassian: Still no plans for that?

Also looking forward to this one, it'll save a lot of manual effort longer term

Looking forward to it

Merry Christmas to everyone and I wish us all that Atlassian has many New Year's resolutions - e.g. to solve this issue!

This feature would be highly appreciated

from 2016 till now gathering interest !!

I think we are well past the "gathering interest" phase. There is interest. Please just make some helpful updates.

I'm looking forward to it!

Looking forward to it

Really looking forward to this functionality being brought back.

The Create Button, Linked Issue Button, and Customer Portal not being in sync is fostering undesirable inconsistency in our organizations use of JSM and requires us to have stricter and more time consumer procedures than we'd like when linking issues.

@Marco Müller

Dear Sir,

Please do not transition your narrow needs on others.

Thank you.

for all*: just remember your Key / Summary and use regular create button. this screen has all you need.

*that have a narrow need like me

Yes please, this would be a very useful improvement

G'day Atlassian! Just checking in if you are still awake, it has just been a mere 7 years, so no rush...

Interested

That would be a great feature!

Very interested!

Same for me !

Please add this option. Easiest fix would be to use the same create issue screen for create linked issue screen.  I expected those to be the same.

Interested

For us most important part of the requirement: in Service Management you usually chose "Request Types" (not Issue Types). This is very important as without request types, reporters will not receive notifications!

So if an agent creates a linked issue by "Create linked issue" screen, he only can choose issues types, not request types --> if missed to add request types subsequently --> no notifications!

Interested

Interested

I have workflow rules that require certain fields to be populated on the creation of various issue types. For example we set an inintial priority which drives which resolution SLA is applied. I can't edit the Create Linked Request Screen which to add this field so I essentially can't create linked tickets for my SLA governed Incidents and Requests.

Removing priority as a required field isn't really a solution to this.

Wanted to add my experience here.
Wanted to create an issue link that contains copied attachments. However the project where the linked issue would reside has a validator where attachments are required. It doesn't see the copied attachments when the linked issue is being created because copied attachments are added after the initial creation - so it failed to meet the validator of the workflow.

Would be good to be able to add the copied attachments during the create transition instead of afterwards so any validators added to the create transition are actually met.

Interested in this feature.

This is a great idea. We would love to have the ability to customize the screen associated with create a linked issue (by issue type, obviously) as the issues we often need to create linked to service desk issues have their own custom fields. Hope to see this in the next 10-20 years. 

Hey I want to see the assigned Person on the "create issue screen" but I cant give the field the attribute "Required". Is there another way to show the field in the create linked Issue screen?? Thank you all.

Just to clarify, I don't work for Atlassian.  Just trying to help you out.  It kind of sounds like you are talking about a NextGen setup (which is just a mess).  If you are in a classic project, go to <yourinstanceURL>.atlassian.net/secure/admin/ViewFieldLayouts.jspa and you have the ability to setup a field configuration and then apply it to a field configuration scheme that you can use in your project.  If you are able to make the field required and do it that way, it will definitely show up on the create linked issue screen (which is a great function because it copies all values into the create screen screen when you are creating it.... it actually copies optional field values too if they are shared... but many times you want to show optional fields to let the user change the value).

Hi, G, 

I don't think you are correct. I have seen that the field is required for Create Issue screen, and works just fine to create a new issue. Also, this is all in reference to the default configuration of the "Change Management workflow for Jira Service Desk", which we cloned for our project and I believe no changes have been made from the default. Operating on Jira Cloud, in case that matters, as I notice the tag for this request says affects-server. 

If we need to talk more about this I can open a ticket, but honestly, it's easier (work around) just to go back to opening a ticket manually, since linking a ticket is very simple to do so using this broken shortcut would have only saved me a couple of clicks - I'm just frustrated to constantly run into so many broken internal integrations in a massively successful SaaS company.

Hey Andy, I'm guessing that you are using validators on your create transition of your workflow for your required fields (I could be wrong though).  If you actually make them required in the field configuration for the issue types that you need, those fields will indeed show on the Create Linked Issue screen (you cannot decide the order though).  However, this can cause other problems... there are a lot of times where you need an optional field to be visible and cannot rely on this workaround.  This screen should definitely be able to be controlled (like you said).  Hoping that they will tackle this as part of the Create Screen redesign with New Issue View.  We need to make sure that we stay on top of Atlassian for this (this great feature seems to get overlooked a lot).

I literally cannot use "Create Linked Issue" for certain issue types because of certain required fields not allowing me to complete the Create Issue form, since the field does not appear in this unmanageable screen. I thought it would save me a click or two to search for an issue whose page I'm already on when creating a subtask, but instead, the workflow is completely broken. Please consider this with slightly more weight than "Suggestion" as this is a basic feature that we expect to be able to control without compromising on basic functionality like required fields.

Hope this works for you:

https://jira.atlassian.com/browse/JRASERVER-60483?focusedCommentId=2466560&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-2466560

I want to add my voice to this request. Our PO would like more of the information captured in JSD to come into the Task in the Jira Backlog.

Kristine Johnson, AR Franchising, Clearwater, FL 

Our team needs this as well, the process is cumbersome to work around.

How many "votes" are needed to transition this issue (bug really) into something Atlassian actually cares about?

in service desk, if we need to create a linked issue for the Jira project associated with the ticket, there is no fields to assign the new issue to a user or to assign the issue to a sprint. Once we select the project for the linked issue, is there any way to customize that screen to show more fields, in particular assignee and sprint (epic and due date would be nice too, especially if we are using SLA, due date would be helpful to let the developer/assignee know when this needs to be resolved). The more tickets we create, the more the backlog fills up which means we have to have someone manually go through the backlog to assign these tickets to developers and to sprints and update due date. The service desk operator should be able to do this from Create Linked Issue so issues don't automatically drop into the backlog (also known as the black hole)

To make use of this new function in our servicedesk environment, we need to be able to customize the view. Surely this must've been forseen, concidering the amount of customization options that have already been put into place regarding screens and custom fields.

If not, we'll need to fill a lot of fields manually, at wich point we might as well just create issues and link them manually just like before. Forcing the fields to be mandatory to show up in the screen is not a suitable workaround for us.

There's already a very exthaustive screen-design system in place in jira, just let us select a screen for this new action and all problems would be solved.

Why in the world would not the Create Linked Issue invoke the Create Screen for the target new Issue.  That would be the most sensible, easiest thing to do.  Bit baffled by this Atlassian!!

It will be important to be able to edit create linked issue screen from the service desk.
When a ticket is qualified to a bug in a software project it is very important to have all the information filled, to understand the meaning of the problem...for that it is important to choose witch fields we want to show or mask in the screen.

Running into this same issue but with more disastrous results.

I have a workflow initial transition with Component as a required field, but the field doesn't show up in this screen. I can't edit it in any way and the "Missing Fields" button is absent. So, creating a linked issue with that workflow using this button is impossible.

This is very confusing and frustrating because huge workaround must be made to counter this situation. It should be feasible to edit this screen as all other screens within JIRA.