Interesting that it's "won't fix".   i could use this too.   Because right now the "links" field can be overloaded with too many tickets of varying relaltionship

Hi, I too need an Issue Picker as a custom field. Given JIRA is so customisable why not add this feature also?

I have a slightly different use-case, but I think still valid:

As a project manager, I would like to see a field on my epics listing all of the issues blocking children of that epic, because I do not want to dig through all of the children 1-by-1 to see this information.

I can use ScriptRunner to update the field, but having an issue field rather than needing to craft instance-specific HTML so that the issues are linked would be a nice plus.

I have a JIRA project with a list of 4000 customers in it. I have another JIRA project with helpdesk tickets in it. I want to link a helpdesk ticket issue to the customer information issue in the customer project. I'd like a field that says Customer information and has this JIRA link to the actual customer information. It is not intuitive or easy for many to understand they need to use linked issues. There is a need for this type of field. Please reconsider. The coding of this is probably peanuts too. Thanks. 

hi all, stumbled upon this - would need this as well. I understand Atlassian must handle thousands of issues but why do we have Project picker, Version Picker but not Issue Picker? Links are not solving my problem well enough. I would need this to overcome the simplistic and not sufficient Jira's take on the structure of Projects and Issues....cheers.

Don't worry though. We'll release this very soon: https://confluence.kepler-rominfo.com/display/KCFPRO/Home

Besides it will do issue picks (among other things), it will and may be used to control how the autocompletes work, through SIL power ... If you want to help us by beta-testing it, we're here ...

Examples: https://confluence.kepler-rominfo.com/display/KCFPRO/Examples

Regards,
Radu Dumitriu

Hi everyone,

The JIRA team has no plans to implement this type of custom field in the foreseeable future. We believe we solved the vast majority of use cases with issue links many years ago.

I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform

The issuepicker customfield plugin solves this issue to a certain extent.

+1

This would also be really useful for us - we'd like to be able to use an issue picker box (ideally with a JQL filter behind it) so that we can say which timesheet code should be used for particular stories and tasks.

This plugin seems to have a way to do this:

https://marketplace.atlassian.com/plugins/com.atlassian.jira.toolkit

See: https://ecosystem.atlassian.net/wiki/display/JTOOL/JIRA+Toolkit+Plugin

EDIT: Nevermind... seems to not work quite the way I was expecting...