+1

+1

And an option to copy attachments into newly created Linked Issue.

+5. Because 5 people badly frustrating without this feature 

Please..

I, too, would like to see an update on this request.

Dears, is there an update on this case?

+1 users are asking for some changes on create linked issue screen...

+1 Please

+1

... not only that the lack off assigning a issue while using 'create linked issue' requires after creation additional steps for assigning (ah, no problem, I have plenty of time while I'm at work :-/ ), if the primary issue has some request participants set (public issue) and I want to create a IT-internal linked issue, the request participants are copied to the newly created issue and I have to take care to remove them manually ...

This renders the feature nearly unusable ...

A configurable screen for this step would be great.

Not only Linked issue screen but Clone issue screen too, you need to change some key automation custom field and couldn't without such custom screen!

Hi!

Thanks so much for all your great feedback on this feature request. We’d love to learn more about how your support teams collaborate with your developers, so we can work on improving Jira Service Desk for your use cases. If you'd like to help us by taking part in a 60-minute interview, please book an available time slot with us » https://calendly.com/mehark/60min

The Jira Service Desk team

That's silly.

Jira never ceases to amaze me at its lack of planning and forethought. Jira is a project for a highschool programming class turned into a hacked together product.

That worked. I had the field set as required for the Create Screen/Transition but not for the issuetype in the project. Thanks for the suggestion!

Joshua McManus

For my setup (comment made Sept 28, 2018) the required/mandatory custom field was only used in one of our projects, it was not used in our Service Desk setup. Because it was setup as mandatory in the Field Configuration for that Jira project it appeared on the Create Linked Issue Screen when creating an issue in that project. Do you have your required custom field already setup in a Field Configuration where it is designated as Required?

We have a required custom field for bugs in our Engineering Project and this field isn't in our Service Desk project...so we can't create linked bugs using this feature. Please help!

Having this issue as well. Commenting for momentum. Would be awesome if "Escalate" could equal "Create linked issue"

Using linked issues in anger for the first time today for problem management, and hit upon this limitation.  +1 for getting this addressed please Atlassian!

It would be great to be able to edit this screen, this functionality is needed. Put my vote in.

I tried the workaround in the duplicate linked issue https://jira.atlassian.com/browse/JRA-60483 and that worked for me. This was setting up a Field Configuration and marking fields as mandatory forcing them to appear on the Create Linked Issue screen. I was fortunate that the fields I needed on the screen needed to be mandatory as well. If you don't need the fields to be mandatory then it won't work for you. For reference we are using JSD Server, I can't say it will work for the Cloud version. 

PA-53589

Hi! We are new in Jira Cloud, and I agree with all others here.

This is is indispensable feature.

Best Regards, Áron Bóra

Agree with all others here.. this is needed now..

is there any update on this ?

Comment for momentum. 

Piggy backing with everyone else that this is a much needed feature.

Hello Jira Team, 

I totally agree, we really need this feature.

We use "Create a linked issue" as a Jira best practice to Escalate the JSD request to other projets (development teams) and it is really not understandable that we can't customize this screen. (you could add this feature in a "create a linked issue" action in the Screen Scheme for example).

We need to add some fields in the "Create a linked issue screen" to configure it when escalating so they (dev team) don't have to.

In addition, we would love if we can call the "Create a linked issue screen" when using an Escalate transition, so we could have only 1 action to do, instead of 2.

Thank you, 

Please Jira Team.

We really need this feature.

Thanks.

We need this feature!

Vote, We need this feature as well, while creating linked issue

We need the create linked issue screen to modify custom fields befor creating the linked issue.

It would be very helpful!

This feature is very important for us as well.

After implementing a custom Description field with pre-populated text it now seems it is not possible to display this field in the Create Linked Issue screen in Jira Service Desk. To say this is annoying is an understatement. Setting this field to Required does not resolve the issue as the pre-populated text does not appear - I've read that the text from Summary & Description in the Parent Issue is auto populated, perhaps this is why?

Any help on this would be appreciated & also an ETA on when we can expect this to be improved in the software... To be able to manage this screen like the Create \ View \ Edit screens would be great. Or for the Create Linked Issue screen to follow the configuration of the Create Issue screen would be ideal - I cannot think of a reason why you would not want to use this anyway when you're "creating an issue" (linked or not it's still creating an issue), it seems strange to me but I guess there must be a sensible reason?

Please help Atlassian! To give the ability to customise screens\fields etc is great but this is a big usage limitation in my view.

It would be nice.
Vote up!

I would also love this functionality. Please let us know when this change can be expected.

@Atlassian

Our users are also interested in an ETA for this change. 

One of the benefits of this functionality is to save time and prevent the duplication of effort when you need to assign a ticket to another team or project, and still keep the original. This is particularly useful for our service desk agents so we can get them to answer the next phone call as quickly as possible without the additional "paper"work. However, having to select the new assignee or reporter after the linked issue has been created causes a lot of confusion, increases the potential for mistakes, and it slows us down. 

Hello to all,

the problem we are facing is that when you create a linked issue Jira pre-fills the fields in the form with values from the parent issue, and this also for fields that are not visible in the form (because them are not required field).

This behaviour is counterintuitive and misleading for users. We are continuously receiving complains about they end up creating issues with fields they didn't want to show in linked issues.

The solution to the problem cannot be to force all fields as required fields.

Hi! 

It will be nice, if you implement it. 

Because workaround using tab is not good for our users

Cheers,

Gonchik Tsymzhitov

A work-around we use (and I'd like to share with you) is to open a new browser tab with Jira, create a new issue in the development project and in that screen, link it back to the service desk request.

This could still be improved by Atlassian. We have the benefit of using the same database for both projects so why should it be so hard to pass information through that same database? Reading and copying values (or choose not to) should really be made easy to save time and prevent mistakes.

It is common to escalate issue from Jira Service Desk projects to Software Projects. It should be doable from the Service Desk Ticket/issue to create a linked issue within the software project and fill the required params (Assignee, priority, ...) these fields are not showing in the create linked issue screen. This is frustrating, so what can be done one step, should be done in more than one, first create the linked issue, search the just created issue, open the edit screen, and fill the values. Customer service agents hate searching for fields among many shown on the edit screen. workaround play with field permission .... anyway would be great to have this feature.

Good day, colleagues!

I am also very interested on ETA for this issue. @Atlassian team can you review the status of the issue?

It would be very handy to be able to customise this. Is there any ETA on this?

@Patrick Savago
+1 

@Atlassian
Are you working on this? 

it appears that fields that are required via field configuration show up at least.

It would make more sense to load the Issue Creation screen for whatever issue type it is you're creating and linking to, and add the Linked Issues field to it.

As developers, we must often block progress on planned work to refocus on an urgent bug or other support request. We'd like a simple screen to set the 'blocks' link that can include additional fields, so we aren't interrupted later with questions about status.

As product managers, we need to know why work was delayed in a reportable way, so we'd like to require that developers select a reason using a (custom) field ONLY when setting the 'blocks' issue link type.

As service team members, we need to quickly locate the status of customer requests, but are often in different time zones from the devs or PMs doing the work. We'd like to create simple searches for blocked issues and blocker reasons that we can use in gadgets or on Confluence so we don't have to wait for answers, and to trust that the data is complete.

As a a Jira administrator, I'd like a simple way to help our teams with these totally common scenarios. I'd like to have a custom screen for issue links, and some way to require fields at the time of this action.

With a renewed focus on due dates we're making them required in the workflow for a great number of projects this year - and as a result are quickly finding how many people use "Create Linked Issue" because of the limitations described by this ticket.  This is painful.

I wish to add on link issue screen conditional steps so I may link issue ofr example if some customfield are filled or not. Link issue screen should be editable as a normal screen.

I wish Atlassian would develop against their own tools (like Screens) instead of making weird, useless, one-off features that offer no benefit outside of a tiny use-case.

Same pain here. +1

There should not be any need to always go and edit linked issue because we were missing the same fields, over and over.

+1

Please let us edit the screen for 'create linked issue'

"Please get this working. Having to open the linked issue to assign it, is a wasteful duplication of work."

yes, it doesn't make any sense at all to hide the field 'assignee'  here.  
Please let us edit the screen for 'create linked issue'......

Anyone found any workaround for this? Cloning and moving, and then linking manually seems an awful waste of time (or creating a linked ticket and then having to enter other field info)

This has been a consistent pain point for my company as well. We would like to be able to add our custom fields to this view so when multiple issues are created that they don't have to be manually edited. 

Agreed. If I can't assign a non-agent to a service desk issue, then at least give us the ability to assign someone in the create linked issue screen. Not to get off topic from the original request, but I would like to see this provided along with ability to customize the create linked issue screen (without having to retype any information that was provided in common fields between projects) 

Please get this working. Having to open the linked issue to assign it, is a wasteful duplication of work.

+1 for this, we need to specify Estimated Time. 

Ran into this in Service Desk as well. Our Change Request process requires fields that are not exposed in the create linked issue screen.

My thought process around designing a system for my company was to create a catalogue of items and to create a linked issue with all the fields of create issue being available for use. Unfortunately, that doesnt seem to be happening.

I don't want to use an add-on for such a basic feature.

At least give us de possibility to assign someone to a linked issue when creating one.

yes please! this is getting more difficult and duplicating work instead

Hi. Just confirmed that the theory works - if you use JIRA Misc Workflow Extension and copy the field from linked issue post-function on Create, you can copy the Reporter from the original service desk ticket to the linked one. If you're on cloud, you need to put it after the reindex postfunction - any earlier it either won't allow you to create linked issue or it just won't work. 

@charis JMWE addon allows you to copy fields from a linked issue so its a possible workaround

Is there any work around for this? We want to make the reporter of the resulting ticket from "Create Linked Issue" to be the original reporter. Is there a recommendation to make that happen? I looked into post function, but it allows copying the original reporter from a parent ticket, not pass it down to the child ticket. 

I agree with Two Sigma, we need the ability to modify/customize the Linked Issues screen

We have custom fields exposed to to Service Desk, that when we Create Linked Issue, we need those values also copied over. 

We really this because under Service Desk, we should not "move" tickets to the JIRA Software type project anymore (this loses the customers ability to find their ticket under the Service Desk portal, once the tickets are moved). "Move" used to let us copy over the values to custom fields, but with "Create Linked Issue" we do not have that functionality anymore. 

Service Desk is very limiting for us without being able to expose the custom fields in Create Linked issue. 

Can states be synchronized? In problems bound by the option: Create linked issues

Since "Create Issue Link" screen does not let adding watchers or change reporter, it loses the original story on who reported the original ticket. 

Being able to customize the Create Issue Link screen so that we can add our custom fields and reporter / watcher, it will reduce multiple steps required to edit the tickets created using "Create Issue Link". 

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!!  Must continue to use the Create and Link Config plugin from Service Rocket.

For the sake of the sixteen other watchers, let's take this discussion to https://answers.atlassian.com, feel free to @mention me there. If the discussion is relevant we can link the "question" back to this issue for others to see.

Hello Steve, I did it like you, with script runner because this improvement doesn't seem like a hight priority for Atlassian. To bad because it is a very important improvement if you want to use the service desk...

Also, there is a problem with scrip runner...when your open dialog screen, if you change the project or the issue type in the list select it doesn't work anymore...because the script with alows you to create the behavior works only with the initialized fonction...it is limited and I don't know yet how to performe this 

More over, I would like to have a script (also with script runner) whitch allows me to have automation when the linked issue is transitionned. Actually it doesn't work well with the service desk automation. Do you know how doing it ?

Currently the lack of functionality or configuration attached to the Create linked issue operation means I must code my own operation for my clients.

The Create linked issue operation initially seemed impressive but different requirements like clients asking for it to require a new Customer Request Type, copy custom fields, copy issue history, or copy issue comments means that ultimately we do NOT use it in any design or actual implementation.

I currently use Script Runner to achieve this for my customers by adding a web item and javascript to populate my own screen.

Could you please increase the priority of this improvement. In my company we have a lot of fields witch can not be used...and then we can not use the Service Desk because it is not mature enough

I want to be able to assign the new created issue directly to a assignee from the screen!

+1

It's unfortunate that this operation doesn't use a screen that we can configure. Why can't it just use the typical Create screen?

I think I chose the wrong issue type, could someone update that, I don't have permission to do it