"Link Problem" in Incident Form does not seem to work right? How do I do it correctly?

Question

1. The Link Problem tool in the task pane on our Incidents, do not seem to actually link the Incident to the Problem.
2. I can link the two by going to the Problem and adding it on the related items tab, but this is very time consuming in a call center environment, especially during an outage where we are relying a lot more on Problem and root cause analysis.
3. I have tried creating the incident and applying, then doing the Link Problem tool and selecting the problem, then applying again and selecting OK to close the incident. Again it doesn't work for me.
What am I doing wrong, number one?
Can we do this without manually opening the problem for every incident and attaching from there?
3. Can I build an incident template that will automate the Attachment to the problem at creation? (Tried this today to and it wouldn't work, but then again, the Link Problem might again be the culprit) This would be great for real time  saving during
an outage. Once outage is found, I could create the template with all the necessary items filled out, and would like to have it automatically attach to the specific problem I choose at template creation, and that way analysts can simply apply template, and
click OK when they get a call related to the outage.

Answer 1

Thanks  for the response Thomas!
The functionality seems to work just fine. I use the LINK PROBLEM and it pops up the problem search box, I search for and select a Problem, I then select it and click ok, and I get no error saying the relationship was not created.
The problem is, when I open the problem after that, there is never any relationship showing in related items there, as it says there should be.
Also, to point out, I am talking about newly created Incidents. I tried even using APPLY prior to doing the LINK PROBLEM but it still did not work. I suspect it may be a workflow problem, where the workflow to create the incident has not completed, there
for the relationship is not completed.... and I get no error.
In my work environment, we have analysts during outages taking a call every 30 seconds, and I need a more efficient way for this system to work. As of now, they spend 1-2 minutes doing the ticket, and that is too long.
I have decided to try a newb way, where I created an Incident (GENERIC OUTAGE) that folks can use, and every 15-30 minutes during an outage, I can open the problem and search for open incidents with that title, and attach all that I find from the problem
side. This is assuming that once attached they will not show up in the search to attach the next time lol. Also this assumes that if attached from the problem, they will auto resolve when the problem is resolved.
I am rusty on my programming, and am currently trying to get refreshed. I am sure that would come in handy for this :)
Oh and lastly, one additional tidbit that will make this clearer, with regard to work flow, we re also running our Service Manager in our help desk, virtualized, as they have not upgraded to Win 7 yet :(. So that compiles my time to add ticket issue :(.