I have the same problem. I have required fields in the issue type but only the first field "first name" is showing up. The second required field "last name" is missing.

FYI - The workaround does NOT work for some fields, even if they are present on the Create screen for the issue type you're trying to create AND they're marked required. Case in point "Epic Link"

Hi Marc,

I did not publish the extension for chrome since google wants developers to pay a fee to do that.

I seem to remember that the code works for chrome too though. You can get the code  from here and install it or create your extension.

Hey   Chris, how can I use your script for Jira cloud ? Is it possible ?

And michirod your addon for Firefox works perfectly fine  but my firm is using Chrome most of the time.

I couldnt find a similar Addon for chrome though. Is it possible to do some for Chrome too ? That would be so perfect.

We need to see those fields.  

Thanks!

Marc

Chris, you a real life-saver! The "Create Link" button is cool add-on to your "reveal" script!

Thanks Sergey, great tool.

For anyone interested in having a "Create Linked" button in the issue toolbar (right after Add Comment), see the 2nd version of the code in my updated comment above

Hello Chris, your solution is very beautiful!

Reccomend use free plugin JsIncluder to free anouncement banner for it's purpose

Hello Chris,

thanks for the input - I will add this to the ToDo list for Optimize.

Maximilian, from your add-on can you extend it to look up an issue type's create screen format and only include those fields? That would make it a complete workaround

Optimize plugin works like a charm, thanks!

For the devs' sake, I thought to just try to filter field visibility according to the relevant create screen info for my workaround, but the chain of information needed for this is not accessible in the API - there's a bit of a gap in the implementation there.

We added an option to the existing addon Optimize, so every available field shows up in the dialog.

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

This just seems to be inexplicable on top of inexplicable. We require Epic Links which, for some inexplicable Atlassian reason, can't be required on the field config so the workaround doesn't work for this which is inexplicable in the first place as to why create linked issue screen behavior has to be different than normal Jira screen behavior. I just don't get it. 

Thx @Chris. The javascript hack worked perfectly for us!

Or you can try the already existing add-on STAGIL Create and Link

When I make an addon for all of these simple things that Atlassian wont fix, I will be sure to let you all know ;P

This is a very basic but needed feature.

 Hey Chris, thank you so much. This works like a charm for us!

I already (unsucessfully) tried to dig into it myself, but apparently those details are not in the html yet. So I don't see a solution by just fine tuning the script.

May be an upgrade to 8.7.0 could help (we are still using 8.4.1)

Thanks for the details, Claudia. I'll have to dig into the subtleties of how each field type is rendered and how tabs are managed and then fine tune the script. If anyone beats me to it, or can make it reliably event driven, please share.

In my case it is only partially working.
I'm using a tabbed layout and have a special issue/task type where not all fields are visible.
After I added the script, the fields are now visible - but not tabbed.
And I can see the summary that should not be visible. But this summary does not have a "wiki-style-renderer".

But it's nevertheless an improvement. Thank you

Thank you @Chris, works perfectly.

To continue Andrey and Carlos' story above, this is like thousands of people driving a model of car for 4 years whose rear left window won't roll down, only for one guy to discover on his lunch break that if you jam a coat-hanger into a certain spot, it works perfectly.

I have worked out a complete fix/workaround/hack (at least for Jira Server), which forces all Create Screen fields to appear in the Create as Linked box. They were there all along, just hidden using Javascript.

Just run some form of this html/javascript from your announcement banner:

<script type="text/javascript">
/* this script runs on every page in jira, used for customization via javascript */

// comment out the line below to show banner. Add content below /script tag

$("#announcement-banner").hide();

function forceUIMod() {
  
  // this will force all hidden fields to appear on "Create as Linked" screen
  $(".qf-field").css("display","block");

  // keep code light here, it runs often

}


setTimeout( function() { forceUIMod(); }, 500); // try to run right away

setInterval( function() { forceUIMod(); }, 2000); // respond to DOM changes

</script>
<!-- Content for announcement banner  -->


<!-- End content -->

I'm disclaiming against the possibility of unintended consequences, but it's live and working beautifully for me, among several other hacks.

Let me know if it works for you.

___

edit:

This is too good not to share...

If you'd like to add a button up front for users to easily find the Create Linked function, try this version:

<script type="text/javascript">
/* this script runs on every page in jira, used for customization via javascript */

// comment out the line below to show banner. Add content below /script tag

$("#announcement-banner").hide();

function forceUIMod() {
  
  // this will force all hidden fields to appear on "Create as Linked" screen
  $(".qf-field").css("display","block");

  // keep code light here, it runs often
  

  // optional: add Create Linked Issue button in toolbar
  var $injSite;
  var injStr;
  injStr = '<div id="opsbar-createlinked-issue_container" class="aui-buttons pluggable-ops"><a id="create-linked-issue-btn" title="Create a new issue linked to this one" class="aui-button toolbar-trigger add-issue-link issueaction-create-linked-issue" href="#" resolved="" ><span class="icon aui-icon aui-icon-small aui-iconfont-link icon-link"></span><span class="trigger-label">Create Linked</span></a></div>';
  $injSite = $("#opsbar-comment-issue_container");
  if ($injSite.length) {
    if ($injSite.is( ":visible" )) {
      if ($("#create-linked-issue-btn").length == 0) {
        $injSite.after(injStr);
      }
    }
  }
  
  
}


setTimeout( function() { forceUIMod(); }, 500); // try to run right away

setInterval( function() { forceUIMod(); }, 2000); // respond to DOM changes

</script>
<!-- Content for announcement banner  -->


<!-- End content -->

This feature is also needed, when the addon Dynamic Forms is used https://marketplace.atlassian.com/apps/1210820/dynamic-forms-for-jira?hosting=server&tab=overview.

There are fields that appear occasionally according to values of other fields. And if they are made required in the addon settings (not in field configuration) - I can't see  them in "Create linked issue" screen and can't create issue.

Hi

And workaround don't work for locked field like .. customer type request, organisation, as there are no option to manage those field in field configuration.

Andrey,

I will add one contrast that is painfully clear. In your example, the car manufacturer does not care about the car, the window, who wants to open it or why. They have no intention of looking at the window because once they have your money and you are locked into their product they have no more desire to help you.

This site illustrates the obvious. There are hundreds of rational, useful, functional and in many cases simple to implement requests and suggestions that go ignored for years before someone at Atlassian closes it because it would require work on their part to realize.

Atlassian simply does not care about its customers and has no intention of providing anything more than the most basic of India based email support. Every prospective customer should browse this site prior to spending any money on this java-coded nightmare.

Andrey, you just made my day. Thanks  keep posting!

Lots of emotional posts...  And I think I can explain it, because i lived it:

When you try to use "created linked issue" and don't see needed field,  you, as usually , going to "screens", to fix it, You did it dozen of times, and you know, that screens are configured there.

Half an hour later, you realize that it is not working, as you expected..  Then, you decide that your Jira is broken, and spend HOURS trying to find out what is wrong with your Jira instance. 

Probably, you even did a clean Install (not in prod,hope),  And conclude, that this is a weird-weird bug, You hurry to report it to the vendor, and expecting it to be fixed in next release...

And Then... You realize, that by vendor, it is not a bug, but feature.  And they are gathering interest for 3 years..

Here is an analogy (That is how i see this situation) :

You buy a car, and week later, you find out that passenger windows on the left side is not opening (other windows are ok)

You are reporting it to vendor,  and they say:  Well, thats by design. and we a gathering info on how many customers need to open left rear window.

This issue, amongst hundreds of others which continuously go unaddressed, prove that Atlassian is unresponsive to the needs of their customers.

I will NEVER recommend any Atlassian product.

I think this problem (like so many reported here) will never be fixed!

The whole system has almost more problems than benefits, this is why the developers have problems to get the Hydra under control.

This is completely unacceptable that this still isnt done. 'Gathering interest' for 3 years. Sure.

it would be nice if the create linked issue screen worked the same as create issue screen, showing the create screen available for that issuetype/project.

This is basic and needed functionality. You can edit other screens but not this one. This is yet another example of Atlassian not listening to the voice of the customer.

Voted.  

It's cumbersome that when I create a linked issue, I can't directly assign it to someone on the screen and have to click on navigate to the crated issue to update it. 😡

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.

We are creating a linked Bug from a Task and would like to have the ability to add an Attachment of a screen shot before it is saved and without editing the new issue. 

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.

The workaround suggested does not really work when you have a situation where you cannot make this field mandatory for all issues created on the project.  

We have a required field in a workflow for which we are trying to create a linked issue from Service Desk to Software project. I am unable to add this custom field (or any field) to that screen in order to use this functionality. How is this missing? Why can I adjust other screen layouts but not this one? Big miss, Atlassian!

Workaround does not appear to work for "Customer Request Type" as it is LOCKED and can't be edited to make required.

Need to add Assignee to this page. No required option for that field.

The suggested workaround works fine on Jira Software 7.5

For our client this is very needed function. Any news about putting it roadmap?

I would also love to see more administer functions to linked issues. Some important fields just don't appear on that screen not even the one's activated for the destination project. So please improve the settings for that!

This is hardly needed for us as business tickets are port of product development, sprint planning etc. So closed sprints added to new tickets and this makes our data inconsistent.

I would be fair enough when this uses the create screen where the ticket is going to be created in.

To make use of this new function in our servicedesk environment, we need to be able to customize the view. Surely this must've been forseen, concidering the amount of customization options that have already been put into place regarding screens and custom fields.

If not, we'll need to fill a lot of fields manually, at wich point we might as well just create issues and link them manually just like before. Forcing the fields to be mandatory to show up in the screen is not a suitable workaround for us.

There's already a very exthaustive screen-design system in place in jira, just let us select a screen for this new action and all problems would be solved.