It took them 20 years to finally decide not to include basic functionality.   You want to know why users actively seek competitor alternatives to move away from Atlassian?   This.

I found a workaround for this. If I have to bulk link 100 test scripts to 1 defect, since there is no bulk link functionality, I go to the defect and Link then paste all 100 defect ID's in the associated link box. It selects all 100 issues and vola the link has been established. 

We used to be able to do this, so how it is too difficult to address this need when you created it in the first place by allowing in in previous versions?

More than 400 votes and still "Not being considered"... at what point can we get this going?

Hello there folks in Atlassian

Pls get these kinda basics done!

Thx 
Michele

We have a problem with too many issues linked to a single issue.  Atlassian are unable to assist short of saying there should no limits contrary to my experience.  So we are looking for alternative approaches and now I find I will have to manually delete > 5k issue links.  Please review this request.

Please do reconsider on reopening this request. Its a pain to do this in the current mechanism. 

Atlassian, your response is sadly unacceptable. Everything about this canned response is disingenuous.

While we believe this suggestion would improve the product  ----  You demonstrate by your inactions that you do NOT believe this.

We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here. -- Nope!  We don't appreciate anything about this.  You are NOT transparent, and you are NOT candid.

How about just telling us WHY you won't provide this functionality?  And do NOT use priorities as an lame excuse. 16 years, seriously???  Just be honest and tell us that the original code base was poorly written and is now too complicated to refactor...or maybe, Atlassian knows better on how we should perform our work and can educate us on what we're doing wrong. 

We'd actually appreciate that kind of candid communication!

Thanks for transparent communication. It is appreciated.  Nevertheless, this bulk change suggestion will indeed help organizations in their current ongoing transformation to adapt current issues to the new reality and link accordingly.

Jira team is not interested in this request, even though its missing feature by JIRA. How they cannot allow a basic need . I would say crappy Jira without this feature.

Will be raising this up via the Corporate Channels at Atlassian

https://www.atlassian.com/company/contact/contact-ceos

Kinda agree with @Gary Bates...its a bit ridiculous for this to be 15 old now.  Would still like to see this in a future build!

It's in 'Review' status and unassigned. So, no one's working on this?

15 years Atlassian? Are you kidding me?!

Hi everyone,

Sharing your concerns, I've just published a new App to solve that issue! You can check it out here:

https://marketplace.atlassian.com/apps/1219169/bulk-linker?hosting=server&tab=overview

We've all been waiting for this for too long! As Bulk Linker is new to the marketplace, feel free to send some feedback through the support channels: 100% satisfaction is our goal!

Cheers

Hi All,
 
      I have found the solution, Please follow the steps to copy links from one to many. let me know if you have any questions 
 
Step1 - By using JQL query get the BUG issue list and select export EXL to get issuekeys.
 

Step2 - Find the issuekeys in excel sheet - copy it.
 

 
Step3 - Select link from "More" option.
 
Step4 - Paste issuekey - Note: After pasting remove the source link issue key (it will throw a error - You cannot link an issue to itself )
 

Step5 - Now you can see the links will start reflecting to the given issuekeys. 
 
 
Thanks
Jeeva
 
 
 
 

No news bad news

Guinness World Records ?

This has been open since 14 years? 

Any plans? 

Regards,

Gonchik Tsymzhitov

Any update here ??

As of 26 August 2014 this was on the 12 month plan. Today is 25 May 2017, 33 months later.

Any update on when we might expect to see this feature?

Hi all,

You can actually use the Easy Link free addon, which creates a custom link field. And that custom field can be bulk changed, which updates the link normally.

That's how I managed it.

Regards

Please implement this feature.  It definitely would provide a productivity boost when loading a large set of user stories into JIRA for quick management and reporting. 

Please add.

Must have, simple requirement.

i agree.....functional feature +1

We need this for change management, how is this not already a functional feature? I see multiple requests and tickets for this request.

Steffen, this feature isn't resolved yet because Atlassian don't care about their customers. That's the simple fact of the matter.

Don't expect this to be fixed any time in the next 3-4 years. You should take this into consideration as to whether you continue to use Atlassian products, or find an alternative vendor that responds to customer problems in a timely manner.

I have a list of about 10 issues I'm interested in, all of which would give material benefits to my company's use of Jira. Instead of fixing any of these, Atlassian persist in spending time changing the UI, confusing my users and not adding any value to my company. Overall Jira isn't so broken as to be unusable for my company however, so we persevere.

I cannot understand, why this feature does not get resolved. If I am currently importing issues and want to link them to "Parents" (NOT as a subtask, but as  "dependency of") issue, the "relates to" option to import the link will give me a wrong link ("depends on") (making the parent the child = wrong direction of dependency). I have no option to bulk change all link types from "depends on" to "dependency of". Together with the issue that links cannot be edited but just deleted and set new, this is extremly anoying and costs me a lot of time. Core feature not available. To me, this is a complete dropout, an with respect on how JIRA dreals with JRA-3097 in combination a simple failure.

Solve this, please!

Any updates on this? The description was changed in 2015, saying "we want to do this but it'll take 12 months...", it's been more than 24 months... what's the ETA?

Thanks! Looking forward to this!

One thing I noticed is that if you delete a link type, it asks you what type of link you want to replace those links with - this may not work for everyone but it fits my use case exactly !

Comment to @barbara.ilves196897325 - your solution works for adding several links to a single issue, but it doesn't address the requirement of changing one link type to a different link type for a list of issues. 

My child will have graduated college before this issue is resolved.  Almost every business process I model, the user asks how they can link a bunch of issues to a single issue.  Come on guys, this can't be that hard.

+1

Is it possible to display a customlink next to "Copy Permalink" in the comments section to open a new page which will display some custom functionality?

I used the Blitz Actions add-on to provide a simple "Bulk Link" button right at the issue (without the nasty export). The action is capable of linking to all issues defined in a JQL statement or in a comma separated list.

Works like a charm...

The easiest way to bulk link issues is to find all the issues you want to link with your issue in issue search, export those to excel, copy the key column and then choose the ticket you want to link them with, choose more, link, select linking type and copy all those keys to issue field, then press link. Took me about 2 minutes

Typical...

Issue created: 2003
Last message from Atlassian: 2014
Votes: over 180

This year is the 13th anniversary of this ticket, and the two year anniversary of the message saying "this is important, and we plan to do it, just not within a year"

Definitely need to be able to change link types from (for example) "relates to" to "contained by" on 1 or more tickets at a time instead of having to create a new link between the same tickets & the delete the old link.

I filed an issue for a related bug: currently, JIRA does not allow pasting multiple issue keys at once into the "Link issue" dialog. If this was fixed, we would have at least a partial workaround for the lack of a real bulk link operation (see JRA-41157 for details).

We'd like this too to support this workflow:

• Our monitoring system creates a JIRA issue if there is a component failure in our live environment (we've created an issue type of alert)
• When we get into the office we fix the problem and log the work we did under an issue (we've added an issue type of incident)
• We then want to link the the alerts to the incident so we can see the root cause that triggered the alerts.

Our requirement is to bulk change a group of Jiras from a list view and then change the link. Example: check 30 Jiras from a list view - edit - change link - belongs to FIN-1234 to belongs to FIN-5555

The script is highly customized for our scenario, but you basically have to authorize a user

$link = $_REQUEST['server']."/rest/api/2/user?username=".$_REQUEST['user']."&expand=groups";
$command = "curl -X GET -H \"Authorization: Basic ".$this->authorize."\" -H \"Content-Type: application/json\" \"".$link."\"";

then read a CSV or a textfield, parse the values, build a JSON:

$json = '{"object":{"url":"'.$this->content[$i]["link"].'","title":"'.$this->content[$i]["linkname"].'","icon":{"url16x16":"'.$_REQUEST['favicon'].'"}}}';	

then fire curl commands:

$command = "curl -X POST -H \"Authorization: Basic ".$this->authorize."\" -H \"Content-Type: application/json\" --data '".$json[$i]."' \"".$this->remaining[$i]['remote']."\"";

Dear Fabian ,
can you please share the link script ?

You can also write scripts using JCLI. I export lists of issuekeys into Excel and build my batch files from there...

The ability to bulk link in JIRA would be slightly more convenient though...

is there maybe any plug-in? its a shame that heres nothing going on....

I wrote a web script that utilizes the REST API to link issues based on a comma separated list of issues. Not optimal, but better than manually linking them

This feature would be very helpful - and I agree with previous observations that it seems reasonable to expect it from JIRA, which so far for me is otherwise fairly unsurprising in its limitations.