Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Replacement for 'Easy Links for JIRA' for custom fields that wrap issue links?

We have been using 'Easy Links for JIRA' to create custom fields for linking issues. Essentially, the plugin wraps existing standard issue links of a specific type into a multi-select lookup field.

However, the plugin did not receive any updates in quite a while and is not compatible with JIRA 8+. Today, I found out that the plugin seems to have just disappeared from the Marketplace. Going to its marketplace listing just gives me the version history. 

Does anyone know what happened to the otherwise fine product? 

Also, does anyone know a replacement (for server, not cloud)? Note that it is essential that the custom field just wraps standard issue links and does not store custom link data.

We already use 'Elements Connect' (previously nFeed) for other custom lookup fields, so I will send them a request. A quick search also showed up vLinks, which may be worth looking at (with just 64 installs though). 

Any other ideas? Any feedback would be highly appreciated.

2 answers

Would it be possible to sync the field with an issue link or does it store the data in the separate custom field itself? They have an example how to lookup an issue ("Require a link to another JIRA issue where they can only pick from a constrained list"), but provide no information what happens to the looked up issue. How is the link stored/reflected in the issue data?

ScriptRunner may be very powerful, but looks like a steep learning curve to me. 

I think it just stores the key as a string.

From there, Jira always picks up issue keys, stored as strings and creates a hyperlink.

Regarding issue link data, I'm afraid this won't work.

We are struggling with same problem. Used Easy Links before to link servicedesk issues with service and customer unit. 

We also have scriptrunner but we have not figured out how to create proper issue link with that,. All help appreciated

Hi @M_S_ ,


Did you received any update from Easy Links, how did you resolved your issue ?

I did not receive any response from the developer. The package seems to have re-appeared in the marketplace, but still does not support JIRA 8.x.

This issue is still unresolved and prevents us from updating. 

Anyone able to provide a replacement or re-animate the plugin is highly welcome.

I have the same problem. I've tried with vLinks plugin ( but i'm not able to fill the new custom field with previous links created with Easy Links.

If anyone of you have a solution for this it'll be welcome.


hi , 

I recently discovered that easylinks has an update for JIRA 8 and above but still didn't try it.


(As of the date of this comment...)

The add-in is only officially supported through Server 8.9.1 and not on Data Center.

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you