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?

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.

Hello, currently I have a couple of different "link issue" screens. 
The first is our Jira Business projects and the second is our Software projects

• Is the second the newer type?   (which is pulling from my "Create/Edit Screen")
  • I assume the Business projects will switch over at some point? Do you know roughly when?
• PROBLEM, the second/newer type does not auto-link to the issue the user is currently in, and has clicked  "create linked issue" in.
  • So we are having these two issue link screens one which sets the link and the other which does not. It is confusing, and we really need the issue to be auto-linked.

7645729f7e9f and a620038e6229, any idea of a timeline for when this will be re-deployed? We were fine with the reporter being copied to the new issue, but definitely understand why in some cases you would not want that (and glad you reverted while ironing it out).

Any updates on this issue please?

Hi, am I missing something here?  I tried the Create Linked Issue again, thinking it would show the same Create screen as shown when using a 'normal' create (via the blue Create button on top of screen).

These two screens are not the same though.  The available fields for Create Linked Issue screen always keep the same, no matter what Request Type I'm selecting.
These fields are:

• Project *
• Issue Type *
• Link type  (e.g. "created issue relates to")
• Linked Issues
• Summary *
• Description
• Copy Attachments

Note that in the Create Issue screen for the selected issue type, we have a lot more fields.
Some of them are set required via a Validator on the initial 'Create ' transition of the workflow.

Would new feature allow user to specify the Request Type on the Create Linked Issue as well?   Many automations run on Create and refer to request Type, so issues created this way or missing those steps.

Or is there another way to allow creation of a particular Request Type from Issue - by the user, not automation?

The above bug listed https://jira.atlassian.com/browse/JRACLOUD-80501 is close as obsolete.    Is there another bug that we can track progress of for the ability to create a linked issue with a different reporter.   That appears to be the biggest use case and is ours.  We need to create an identical issue with a different reporter.  Using create linked issue would work great if it had the reporter fied in there.

Hey all,

We, unfortunately, had to roll back the new Create linked issue screen due to the impact of the bug mentioned above, in addition to a few low-impact ones. To ensure the best experience for you, we'll roll out the new Create linked issue screen with these bugs resolved soon! Please stay tuned.

Thank you,
Arbaaz Gowher
Product Manager, Jira Cloud

Hi all, 

Thanks for flagging the bug with the reporter. This is being fixed as a top priority, you can follow it here: https://jira.atlassian.com/browse/JRACLOUD-80501

Sorry for the inconvenience, we are working to fix this ASAP. 

Best regards,

Jehan

@Jehan Gonsalkorale Why would the default workflow for autofilling the reporter when creating a new linked issue change from the logged user without notice to us...THE USERS... or at least provide us with an option to keep it the same way it has been all this time???

Exactly the same experience as @Sébastien.
For my organisation this needs to default to the Agent creating the linked issue BUT with the ability to overwrite this with somebody else (for us, a different Agent).

What's been implemented is a field that the Agent must remember to change when creating a linked issue to avoid creating a problem downstream.

• Leaving the Reporter field blank and mandatory would have been better.
• Leaving the Reporter field blank and mandatory with a Reporter select list that has the logged in user and RT reporter at the top even better.
• Defaulting the Reporter field to the logged in user with the ability to change this would be ideal.
• Defaulting to the logged in user with the ability to change the Reporter from a select list that has the Agents prioritised alphabetically at the top even better would have been perfect (for us at least).

Since the last week, when I'm in a service desk project type and I create a linked issue, the reporter is now equal to the initial request.

The problem is : the destination of the linked issue is not in the same project and if the reporter is a customer.

This may be out of scope, but is it possible to start(open) the create linked issue screen during a workflow transition?  We have been trying to do that using an automation and transition screen to ask for values but it would be much easier if we could just open the linked issue screen.  Then we don't have to worry about showing required fields, the linked issue screen does that for us.

Hi all, 

We have recently pushed out changes that will surface the create issue experience in the create linked issue experience. This will allow you to select a request type, which will result in the request type configuration being surfaced. 

Please let us know if this doesn't meet your needs or if you have any feedback, we can re-open the ticket or create a separate ticket to track any use cases that haven't been covered. 

Best regards,

Jehan Gonsalkorale

Product Manager, Jira Service Management

Hey Jehan,

I think  the main thing we're all searching for is a way to create a custom screen for creating a Linked issue.

At this time it only shows the mandatory fields when you create a linked issue and not other ones from the issue type you are going to.

So if you want e.g. go from an Incident to a Change and at creation add more information, you cannot 

Hi all,

We are working towards a release early next year (early 2023) where we will surface the same issue create experience when creating linked issues. 

This will enable you to customise field ordering and field names and they will appear as they do in the portal. This will not allow you to customise the "Copy attachments" check box or anything specific to that screen but will let you otherwise customise how fields appear. 

We'd love your feedback here to understand whether this will meet your needs. 

Kind regards,

Jehan Gonsalkorale

Hi all, 

Thanks for your interest here. We appreciate that this is an important need but we are currently unable to provide this solution yet. That said, we hope to revise this in future and see whether we can prioritise this in the medium term. 

Best regards,

Jehan Gonsalkorale

Product Manager, Jira Service Management

As a user who has customer feedback added to the service desk with specific questions I need to move to the linked ticket, its critical to have this ability.  Without it i'm manually making linked tickets which is a huge time waste.

Workflow is cumbersome without this option. 

Now I need to create the ticket and then open the linked ticket either way to update my custom fields, add label tags and components. 

Missing the option to choose request type of the linked issue. We use this feature to tie together 1, 2 and 3 line support and only having the option to choose a issue type not request type is limiting us. 

Hi all,

Thanks for your interest here. We are currently looking into this area and will provide an update soon once we prioritise whether or not we can resolve this at this time.

We appreciate your patience, entirely understand this is important to you and do want to provide a solution but need to do the appropriate discovery and prioritisation before we can make a commitment here.

Best regards,

Jehan

Can this please be fixed! Issue/ request was created in 2016

I would like to see this functionality work the same way in all project types, not just service desk.

Definetely +1

Suggested solution #2 would be perfect!

I think that the Create issue screen should be used during this "Create a linked issue" action.

Hey Jeff, just an fyi, it is actually the Create Issue screen for the applicable Screen Scheme that you are seeing, however it only allows you to edit values for fields that are required in the applicable field configuration (it's silly).  We just need them to allow Optional fields to show too.  I bring this up, because if you have shared fields with a shared context between the source issue and the issue that you are creating, as long as that field is on the create screen as optional, it will at least copy the value to it from the source issue on creation.  We use this all of the time and it helps fill some gaps that exist due to this .  Still is desirable to have optional fields that users can dynamically select though.

Some integration apps originally behaved like this and have been upgraded over the last several years... I wonder if this create linked issue screen is working like an app and needs to use a new method to show optional fields now too.

The behavior I expected was that I would simply be presented with the the CREATE ISSUE screen for the selected project and issue type. The last thing I would want is yet another distinct screen to manage.

+1

We are also interested in making the Create Linked Issue more workable so more of the information captured in JSD will transfer to Jira Backlog.

Kristine Johnson, AR Franchising, Clearwater FL

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