Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Custom Field to Link Issues

Hi

Is there a custom field to link isses at time of entering in the details of a bug, rather than have to do if from the view screen?

Thanks

Simon

4 answers

Hi ,

You can try a free plugin I've made: Easy Links for JIRA. It provides two new custom field types: Single Issue Link Picker and Multiple Issue Link Picker. These custom fields are displayed as dropdown select lists, which you can filter and autocomplete by typing on it (see screenshots). Also, you can configure the customfields to restrict the available issues to select (using a JQL expression when creating the custom field), and the link type that the field will be associated to. When you select a value, a new issue link is created between the current issue and the selected one(s), that you can manage as a regular issue link.

In addition, you can use the custom field in JQL queries (for example: "Blocking Task" = TEST-123), and in dashboard gadgets (pie charts, filters, etc).

I hope it can solve your issue,

greetings!

 

 

HI Fernando,

This looks like a very useful plugin. Does it work on JIRA 6.4 ?

Best Wishes

 

Hi Edward,

at this moment it is only available for 7.x.x, sorry sad

Regards

 

Hi Fernando,

Is this plugin(Easy links for JIRA) compatible with JIRA Core(7.xx) Server?, as i could see its compatible with JIRA Service desk application only.

Is it okay to add that plugin via upload add-on button?

Regards,

Kavitha

Vinu
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Dec 20, 2018

Hi Kavitha

We are using this plugin for Jira software and it works just fine. I see no reason on why it should not work on core.

Hi Fernando. We have been using your easylinks addon for about 12 months and its been great. However it no longer works in JIRA 8.0.2 and we have it on a few of our issue forms. This is preventing users from creating these issues and we are not sure what to do. 

Can you help. Many thanks

Jon

I'm super keen to see this work in 8 too

Like Neil Taylor likes this

No, it does not work on 8.0.2, unfortunately.

+1 for having this upgraded for Jira 8 - this is a fantastic addon - we would definitely still be interested if it was paid as well.  Currently it is holding up our upgrade to v8.  Are there any plans to upgrade it or does anyone know of any similar alternatives?

Like Gautham likes this

+1. We also need it!
There is no mention to this app anymore on Marketplace!
The nearest I found was https://marketplace.atlassian.com/apps/1220571/custom-fields-issue-picker?hosting=server&tab=overview, a paid one!

I'm looking forward for a reply from the author of Easy Links for JIRA...

Dario B
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 11, 2020

The app is still available in the marketplace and it supports Jira Server 8.x:

Will you be building this for Cloud? 

I second that, having this on cloud would be really great.

0 votes
JamieA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 08, 2011

You can add the "Issue links" (or some similar name) field to the create screen, providing you are on jira 4.4 onwards.

It is throwing the following exception for version 6.4.13. Please help.

-----------

2017-03-03 18:44:02,874 UpmAsynchronousTaskManager:thread-1 INFO admin 877x2185x3 qqibm8 0:0:0:0:0:0:0:1 /rest/plugins/1.0/installed-marketplace [atlassian.plugin.loaders.ScanningPluginLoader] No plugins found to be installed

2017-03-03 18:44:02,874 UpmAsynchronousTaskManager:thread-1 INFO admin 877x2185x3 qqibm8 0:0:0:0:0:0:0:1 /rest/plugins/1.0/installed-marketplace [atlassian.plugin.manager.PluginEnabler] Resolving 0 plugins

2017-03-03 18:44:02,874 UpmAsynchronousTaskManager:thread-1 INFO admin 877x2185x3 qqibm8 0:0:0:0:0:0:0:1 /rest/plugins/1.0/installed-marketplace [atlassian.plugin.manager.PluginEnabler] Enabling 0 plugins: []

2017-03-03 18:44:03,214 UpmAsynchronousTaskManager:thread-1 ERROR admin 877x2185x3 qqibm8 0:0:0:0:0:0:0:1 /rest/plugins/1.0/installed-marketplace [atlassian.plugin.loaders.ScanningPluginLoader] Unable to deploy plugin 'com.codedpoetry.easylinks.easy-links' from 'Unit: /Users/ranjusachdeva/myPlugin/amps-standalone-jira-6.4.13/target/jira/home/plugins/installed-plugins/plugin_8541425109212871393_easy-links-1.1.3.jar (1488527042000)'.

2017-03-03 18:44:03,214 UpmAsynchronousTaskManager:thread-1 ERROR admin 877x2185x3 qqibm8 0:0:0:0:0:0:0:1 /rest/plugins/1.0/installed-marketplace [atlassian.plugin.loaders.ScanningPluginLoader] Because of the following exception:

com.atlassian.plugin.PluginParseException: Unable to scan for host components in plugin classes

 at com.atlassian.plugin.osgi.factory.transform.stage.HostComponentSpringStage.execute(HostComponentSpringStage.java:62)

 at com.atlassian.plugin.osgi.factory.transform.DefaultPluginTransformer.transform(DefaultPluginTransformer.java:146)

 at com.atlassian.plugin.osgi.factory.OsgiPluginFactory.createOsgiPluginJar(OsgiPluginFactory.java:324)

 at com.atlassian.plugin.osgi.factory.OsgiPluginFactory.create(OsgiPluginFactory.java:229)

 at com.atlassian.jira.plugin.MasterPluginFactory.create(MasterPluginFactory.java:81)

 at com.atlassian.plugin.loaders.ScanningPluginLoader.deployPluginFromUnit(ScanningPluginLoader.java:155)

 at com.atlassian.plugin.loaders.ScanningPluginLoader.loadFoundPlugins(ScanningPluginLoader.java:117)

 at com.atlassian.plugin.loaders.PermissionCheckingPluginLoader.loadFoundPlugins(PermissionCheckingPluginLoader.java:30)

 at com.atlassian.plugin.manager.DefaultPluginManager.scanForNewPlugins(DefaultPluginManager.java:850)

 at com.atlassian.plugin.manager.DefaultPluginManager.installPlugins(DefaultPluginManager.java:799)

 at com.atlassian.jira.plugin.JiraPluginManager.installPlugins(JiraPluginManager.java:163)  <+3> (NativeMethodAccessorImpl.java:62) (DelegatingMethodAccessorImpl.java:43)

 at java.lang.reflect.Method.invoke(Method.java:498)

 at com.atlassian.plugin.osgi.hostcomponents.impl.DefaultComponentRegistrar$ContextClassLoaderSettingInvocationHandler.invoke(DefaultComponentRegistrar.java:134)

 at com.sun.proxy.$Proxy319.installPlugins(Unknown Source)  <+3> (NativeMethodAccessorImpl.java:62) (DelegatingMethodAccessorImpl.java:43)

 at java.lang.reflect.Method.invoke(Method.java:498)

 at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)

 at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:58)

 at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:62)

 at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)

 at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)

 at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)

 at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)

 at org.springframework.osgi.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:56)

Suggest an answer

Log in or Sign up to answer