Replace old Jira and Confluence links (#4937)

README.md

@@ -9,12 +9,12 @@ For more information oriented towards developers, check out our [developers page
 
 # Issues #
 
-For reporting issues use our [JIRA Bugtracking System](https://jira.catrob.at/secure/CreateIssue.jspa?pid=11800&issuetype=1). Before that, please browse our currently open issues [here](https://jira.catrob.at/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+CATROID+AND+resolution+%3D+Unresolved+ORDER+BY+priority+DESC%2C+key+DESC&mode=hide).
+For reporting issues use our [JIRA Bugtracking System](https://catrobat.atlassian.net/jira/). Before that, please browse our currently open issues [here](https://catrobat.atlassian.net/jira/software/c/projects/IDE/issues/IDE-234?filter=allissues&jql=project%20in%20%28%22Catroid%20IDE%22%2C%20%22Catroid%20Stage%22%29%20ORDER%20BY%20created%20DESC).
 
 
 # Contributing #
 
-If you want to contribute we suggest that you start with [forking](https://help.github.com/articles/fork-a-repo/) our repository and browse the code. Then you can look at our [Issue-Tracker](https://jira.catrob.at/secure/RapidBoard.jspa?rapidView=60) and start with fixing one ticket. We strictly use [Test-Driven Development](http://c2.com/cgi/wiki?TestDrivenDevelopment) and [Clean Code](http://www.planetgeek.ch/wp-content/uploads/2013/06/Clean-Code-V2.2.pdf), so first read everything you can about these development methods. Code developed in a different style will not be accepted. 
+If you want to contribute we suggest that you start with [forking](https://help.github.com/articles/fork-a-repo/) our repository and browse the code. Then you can look at our [Issue-Tracker](https://catrobat.atlassian.net/jira/software/c/projects/IDE/issues?filter=allissues&jql=project%20in%20(%22Catroid%20IDE%22%2C%20%22Catroid%20Stage%22)%20ORDER%20BY%20created%20DESC) and start with fixing one ticket. We strictly use [Test-Driven Development](http://c2.com/cgi/wiki?TestDrivenDevelopment) and [Clean Code](http://www.planetgeek.ch/wp-content/uploads/2013/06/Clean-Code-V2.2.pdf), so first read everything you can about these development methods. Code developed in a different style will not be accepted. 
 After you've created a pull request we will review your code and do a full testrun on your branch.
 
 If you want to implement a new feature, please ask about the details on https://catrob.at/mailinglist
@@ -23,7 +23,7 @@ Start setting up the working environment by following the instructions: https://
 
 Also make sure to read our guidelines for [creating a pull request](https://github.com/Catrobat/Catroid/wiki/Creating-a-pull-request)
 
-A first training ticket usually consists of writing a new Catrobat language test, see https://jira.catrob.at/browse/CATROID-390 for details.
+A first training ticket usually consists of writing a new Catrobat language test, see https://catrobat.atlassian.net/browse/CATROID-390 for details.
 
 
 # Resources and links #

automationScripts/createBetaTestingPocketCodeAPK.py

@@ -1,5 +1,5 @@
 # does all of this for you:
-# https://confluence.catrob.at/display/KNOWHOW/How+to+create+a+release+standalone+Pocket+Code+apk-file
+# https://catrobat.atlassian.net/wiki/spaces/KNOWHOW/pages/18286692/How+to+create+standalone+APK
 # plus generates the apk and copies it to this folder
 import shutil
 import os

automationScripts/increaseVersionByOne.py

@@ -1,5 +1,5 @@
 # does part of step 2, increasing version code:
-# https://confluence.catrob.at/display/KNOWHOW/How+to+RELEASE
+# https://catrobat.atlassian.net/wiki/spaces/KNOWHOW/pages/18286436/How+to+RELEASE
 
 # step 1. build.gradle changes
 buildGradle = open("../catroid/build.gradle", "r").read()