HI,

very good news

Atlassian Update - 3rd May 2023

Hi,

947 people have voted, we hear you and want your feedback.

Tell us about your personal experience so we can create the best solution possible.

The interviews will be conducted over Zoom and take up to 45-minutes. We want to gain an understanding of your context and how the problem impacts you.

If you are interested in being involved, please sign up via this link:

https://www.userinterviews.com/projects/6ZILrRtchw/apply 

As a token of our thanks, $100USD gift cards will be sent to those who participate.

Looking forward to speaking with you!

Lucy Devine

Jira Service Management, Data Center & Server

Lucy! Tell us there is hope! I'd settle for having the create linked dialog mirror the Create screen in full, as expected (not a minor bug, it's major pain point), but a separate action in the screen scheme would be even better.

For Jira Server/DC you can try this workaround, it works for me and plenty of others, but not for everything/everyone.

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

It's FAR from a perfect solution, but better than nothing, where Atlassian has chosen to do nothing for several years.

I've seen cases where fields are mandatory but still do not appear. Visibility for these should absolutely be linked to the Create screen action

thats only possible if those fields are mandatory via the field configuration

I want to add components and Assignee to the Create Linked Issue screen - how do I do that?

+1

+1 would be a great feature which gives a better overview !

How many wathers (408),votes(908) and commends(112) an Suggestion must have to become attention for Atlassian?

Why does Atlassian have feature requests? I've never seen one resolved.

+1

+1

+1

+1

+1

+1

+ 1

Would save me a lot of work (editing the created issue, filling the fields, which were not available during "Create linked issue")

Hi VVor, the workaround was written for Jira Server. You could try taking the part inside the <script> tags and running it in this free plugin: [JsIncluder | Atlassian Marketplace|https://marketplace.atlassian.com/apps/1211670/jsincluder?hosting=server&tab=versions]

I'm guessing that it may be more consistent than the announcement banner in service desk.

Hi. The workaround posted here by Chris M. works only if you are trying to Create a Linked issue inside the Jira Service Desk.
On my environment I must create linked issue in JSW with new Assignee (developer), so when I'm changing the Project field from JSD project to Jira SoftWare project the devil comes out to the scene - the Screen refreshes and the number of hidden fields decreases. And hidden Assignee field disappear from page code

The problem was caused by wrong user rights in JSD and JSW schemas (user had improper rights on the target JSW project)

+1

+1

+1

Thank you Chris, I did see the work-arounds. Unfortunately, none of those will work in our environment as there are strict controls around browser modifications and procurement of add-on/apps to Jira. The only solution for this that will work is one from the vendor. (for us anyway)

Hi Tom, Albert, just in case you missed the link to the workaround I posted last year, we've been using this in production without issue, maybe it will help you: 

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

Read on from there though, others have created derivative works as well, from browser add-ons to Jira apps.

We really need this in 2021

Having this ability as mentioned - a new screen related to issueTypes as the other screen options are - would allow the addition of fields without mandating that they always be filled with values. Example: I would like to include Story Points and FixVersion that would fill about 90% of my requests. I may opt for using the mandatory field setting in my field config as a work around to make them appear, but this can end up causing other issues for issues that should not retain these fields. So, again, having the relationship and editable nature of the create issue link screen for a project would allow us to make these adjustments for the cases that help our processes and not create additional work for when we should not use the additional fields we have added.

This would save processing time for users at multiple levels.

Thank you,

Tom

+1 This is definitely very useful feature.

+1 This would be a major upgrade!

Come on ,step up, this is not a "nice to have", it's basic functionality that is there for other screens, you have just not though to have this one configurable, .. well, time to do that

Barak Obama was still a president when this request was created....beyond unacceptable service! 
 

4 years and still "Reviewing"... Shame on you, Atlassian!

Well done, michirod. Much slicker implementation with the mutation observer. Unfortunate that this may have consequences for workflows counting on certain fields to be hidden, but that door was never closed on the server side. Something for admins to be aware of.

Thanks to Chris M. input I created a browser extension that shows hidden fields in the Create Linked Issue dialog.

This ticket is unreal.

Extension: https://addons.mozilla.org/en-US/firefox/addon/jira-create-linked-issue

Would really appreciate this being considered. This creates a significant amount of additional work for the team as they have to go back through and correct all the fields once making a linked ticket. It's like having to go through the ticket creation process twice...

Great feature. +1

I see a LOT of people having serious problems with this shortcoming.

I've just posted a workaround I'm using that makes the Create Linked Issue dialog show all Create screen fields. Please see here:

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

Atlassian has work to do on this, but I think this will solve the major issues for most admins.

An at least occasionally possible Workaround:
I noticed that mandatory fields are displayed on the create linked issue screen. You just have to set the desired fields mandatory in the corresponding field configuration scheme for the issuetype and they appear on the create linked issue-screen.
Its not an optimal solution and not always applicable but it helped me at least on some occasions, so I hope it could be of use to someone here

+1 here. 

Hi all, we wait for those features too, but as a workaround we use Automation for Jira in order to link the tickets and so we can add and change the fields we need in the linked ticket. 

Without the possibility to add needed fields on this screen we need to always edit a created issue which causes more work as it is difficult to control the flow of what needs to be actually added

+1

+1!

This is causing significant rework for our team and break downs in change management standards. Our team is providing information for change management fields that are then lost when the linked ticket is created. The rework required to transfer this over is large. Additionally, this violates many change management standards by defaulting the 'assignee' to the assignee in the original project.

+1 here.

We need to be able to customize the "Create linked Issue screen" by adding any needed fields.

+1

+1

+1

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

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'

Agree with Susan and Steven, easiest and best solution would be to use the Create screen for the target type with prefilled values. Then you would get all functionality from validators in create screen on place directly instead of building another new functionality. 

"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.