One additional note which relates to this issue, but also JRACLOUD-82252 and JRACLOUD-60483:
The Team field and other Locked fields cannot be made 'required' in a field configuration. 

So the only way it to make them required in the Create transition of the Workflow. 

But this completely blocks the 'Create linked issue' function, because the Team field cannot be displayed on that screen, while the user gets an error about the field beging required. 

It would be very helpful if the requirement is implemented. 

96677a1d9b4c , can you please try to get this bumped up in priority? My agents are having to assign a Request type to each created linked issue, click refresh, and then continue entering the info they need to and it's time-consuming. I know Rovo, AI, Analytics and the other shiny stuff is fun to develop but this is a basic feature that a lot of folks need and would really appreciate. Thank you!

> Please vote for this suggestion (and comment below) if you would like to see JSM use the new experience.

What's the hold up?  JRACLOUD-60483 got closed prematurely and pointed to this one.  This is beyond frustrating!

Hi all,

Jira recently shipped the new 'Jira issue create experience'. 

This is not yet available in JSM as it does not pre-populate the fields in the linked issue with data from the original. We understand this is important functionality and so we are delaying implementing the new experience in JSM until this gap has been addressed.

More information can be found here.

Please vote for this suggestion (and comment below) if you would like to see JSM use the new experience.

Kind regards,

Sam Knight

7645729f7e9f and a620038e6229, checking in again. Is there a plan to re-deploy this into Jira Service Management projects like it was in the beginning of last year? It was reverted because of JRACLOUD-80501 (we would have even been fine with that experience with that bug... that is preferred over the current experience of not being able to touch optional field values and the old wiki markup create).

It also seems that the create linked issue screen is the newer screen for software projects only right now (not JSM nor Work Management), yet it does not pre-populate shared fields like it should in that project.

Hoping that this will be brought back into JSM like it was 1 year ago, with the only change being that the Reporter is the current user or blank as Martin described.

We have the option in our instance.  It shows up after you switch the project to the service project 

Hello there,

I noticed that at the start of this year the Crated Linked Issue screen had the optin to use Request Types but then it went away just a few days later. This is a major oversight in functionality and make it much more difficult for our teams to collaborate seamlessly.

Is there possibly any update to this?

JRACLOUD-78924 “Option to select the Request Type on Create Linked Issue screen for JSM Projects” was closed without a solution and just the following comment: 

7645729f7e9f added a comment - 13/Feb/2023 3:42 PM
We recently released an update where the Create linked issue screen starts surfacing the Request type field. This was tracked in JSDCLOUD-3917.Thank you,
Arbaaz Gowher
Product Manager, Jira Cloud

 
Where is the update where the Create linked issue screen starts surfacing the Request type field" because we don't see it?

This issue was reported 7 years ago and is still unresolved. Atlassian

Hi, 1786924f9c2c, your case seem a bit different than the scope of this feature request, which is specific to Jira Service Management. If you haven't done so yet, please raise a support request for our team to give it a look, from what I see it might be something that can be solved via configuration.