Hi a8728c14549b, not sure if you can help but we're having issues with Linked Issue creation screens since Dec 16th 2024. When we created linked issues, the same fields present on the original issue and the linked one would be synced automatically (summary, description and also custom fields that were common to both issue types). Since the 16th, it doesn't do it anymore and our users have to fill all the fields manually. All our workflows were built with this nice behavior about copying same fields from original issue to linked one ... now it doesn't work anymore and I'm struggling to understand why. Are you able to help us solve this problem? Or direct us to the right way? Thank you.

HI,

very good news

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.

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