moving back to TODO, I think we can find more valuable tasks that can help oVirt and the team.

clone of OVIRT‌-1447?

There is no actual need to use the Gerrit API. Once you figure out how to add weblinks to Jira tickets with the Jira JSON API (You'd probably want to use a Python wrapper around it rather then try to use the REST API directly over HTTP), we can just setup a Jenkins job or a Gerrit hook to run the code when commit messages change.

Look at any of my tickets that reference Gerrit patches to see how the web links should look like.

Regarding JIRA API, we're using the cloud instance, the JIRA we're currently using for this ticket actually, so you can check the help / about info on the top right.
This might be a good place to start looking: https://docs.atlassian.com/jira/REST/cloud/.
So you'll need to check if it's even available to use and how to configure it, since we don't have access to the system itself, just the UI interface ( we do have administrator rights though ).

Regarding Gerrit API, @Barak Korren will probably know better than me what to use, since we're using it in CQ already.

Before I start reading and learning the wrong APIs, we are talking about REST API?
for JIRA I found this: https://developer.atlassian.com/jiradev/jira-apis
can you please give me more info on where I can find documentation/tutorial on Gerrit python API ? is this the correct one? https://pypi.python.org/pypi/pygerrit/0.2.1