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.

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

We also need this functionality - and it opens up a wide range of other uses for Jira.
Specific use in mind: we want to hack in basic CMS functionality and replace our other system: link a 'client' issue from a task, then pre-populate contact details into another tab on task screen.
Implemented as a drop-down list of existing issues of a specific type would be perfect (+ link to create a new task of that type).

I also really need this. I have a special 'Project' issue that is present in all projects. This issue provides an interface to our PMs to apply extra budget to the Original Estimates of Issues. They would input a number and provide the ID of an Issue that they wish to add the budget to. It would be great if there was an Issue Picker field that allowed the user to 'search' in the same way they do when searching for an issue in Tempo to log work against.

As multiple hieracary is not possible in Jira (OnDemand), and a common usage of Kanban is Epic -> Stories -> Tasks, and Epic is not fully supported with Greenhopper Kanban boards, adding a required Linked Issue field "Is Story of Epic" or something similar would have been a great way to link Stories to a Epic.

I'm sure there are a thousand other useges as well.

Will you be implementing this?

I need too issue picker autocomplete textbox. we have been creating a plan issue screen in which, over the calendar needs to select issues for selected days.
I am not able to find "issue picker" textbox which can be used to select issues.

It would be really helpful if such control is available.

Thank You.

Our company needs that field too, for the same reasons Hemal Udani pointed out. We are using Jira 5.1 any plans to have this in future versions?

We need this as well. The issue linking works great, but for our use case, we need a dedicated field to enter the ID of another issue. We would like to make that field required as well. Issue linking cannot be mandated for a particular relationship type, but this field can be. So, voting for this one to be implemented.

Joining the voters group. Same reason as explained above.

Hi Bhushan,

At the moment this issue is not scheduled and therefore I am not sure when it will be implemented. We have thousands of new feature and improvement requests and we are trying to work our way through most popular ones. For more information on the way new feature and improvement requests are scheduled please see:
http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements

Please note that Custom Fields in JIRA are plugins, so it is possible to build your own. For more information on this, please see:
http://confluence.atlassian.com/display/JIRA/How+to+create+a+new+Custom+Field+Type

Atlassian also has partners who specialise in extending JIRA. If you are interested in working with a partner, please send an e-mail to:
partners at atlassian dot com

Cheers,
Anton

We too have exact requirement of "issue picker for custom field" the way it is explained by Raghu above. To justify the need, I will add following to what Raghu has mentioned above.

Issue linking is great facility and it serves the purpose most of the time, But if I simply link the issues, then I can't selectively display them in issue navigator along with appropriate headings. Everything is displayed under heading "links". So if one of the linking is more important and needs to be displayed on issue navigator then there is no way to show that.

Can we have update on this?

-Bhush

In the case of link, both outward and inward link descriptions are mandatory; so I cant have outward descriptions alone.

-raghu

I would also request for an issue picker, which lists all the issues from the same project. In our case we have a text field called 'RootCause' which has the value of an earlier issue. This field mentions the issue which was the Root Cause for this bug.

I know now you would suggest me to use the 'link' option, but then in my case on an average I have 30 to 40 issues pointing to one Root Cause. So if I use a link the Root Cause Issue page will have 30 to 40 links in that which I dont want.

-raghu

I think this sounds like issue JRA-6748 which would allow creation of a link at the time of issue creation.

We have the following scenario:
For one project we create two jira projects (project-customer, project-developers). The customer project is only visible for the the customer and the developer and use a special customer workflow. The developer project is only visible for the developers, so if a developer create a new issue with a special "create issue screen (with issuepicker)" in the developer project, he can choose an existing issue from the customer-project at creationtime.
I hope you understand my explanation.

Olaf,

Can you give me some more information about why you want this?

Cheers,
Scott