This repository is no longer maintained. This repository is archived for parties interested in the standalone functionality that this repo once offered. Now, the functionality has been moved to OpenReq Issue Link Map. For full details of capability and intended usage, please see OpenReq Issue Link Map.
Before this project was archived it passed the sonarqube quality metrics. 
This web application was created as a result of the OpenReq project funded by the European Union Horizon 2020 Research and Innovation programme under grant agreement No 732463.
This web application visualizes the links between issues inside Qt’s JIRA. It uses the microservices of UH (API references) to manage links and the similarity detection of UPC (API references) to recommend missing links. The OpenReq services milla, mallikas, keljucaas, mulperi, palmu, nikke and the similarity detection are used by this web application and need to be running in order for the web application to function.
- Spring Boot
- Tomcat
- Vis.js
- Google Gson
- Okhttp3
- Maven
- Bootstrap
- Visualization of the link network of public issues in Qt’s JIRA While in JIRA the user can only see the direct links, this tool enables the user to go more in-depth and also view indirect links between JIRA items.
- Quick info for selected issue Essential information of an issue is displayed on the right-hand side.
- Navigating the link network The user can drag items and add or remove layers.
- Consistency Checker Checking if the issues in the link map do not have conflicting link type and priority and displaying the result.
- Filtering the issue link map for specified properties To support the user in navigating this link network filters should be in place to hide issues depending on their status, the link type between them.
- Accepting & rejecting proposed links The results of a link detection are also visualized, this view should can be toggled on and off for a specific issue. While the link detection is enabled the user is given a list where he can decide what type of link should be used or if this proposed link should not be a link.
- Full Integration into Jira as a Jira plug-in Currently, accepted and rejected links are not written into the Jira database, just back to mallikas.
- Add more filter options Adding more filter options to also filter f.e. egdes
- Editing links By right-clicking an edge, the user can change the link type, switch direction or remove the link
The application is accessible here
!This is currently broken! Additionally, a connection to the tool is in https://bugreports-test.qt.io/secure/Dashboard.jspa. This connection is created by installing the "jira-redirction" plugin.
You first need to deploy the following OpenReq microservices:
Mallikas is a database that Qthulhu accesses over milla, so it needs to contain the issues you want to visualize.
In src/main/java/eu.openreq.qt.qthulhu change the URLs in the class Property to the corresponding endpoints of your deployment of milla.
You might need to adapt the colorPaletteStatus and arrowPaletteType in Qthulhus issueid.jsp to the words used in your Jira.
This is a maven project, so use
mvn clean package
in your IDE and then run
java -jar qthulhu-webapp-1.0.war
You can directly search for an issue here.
for example Issue: QTWB-30 and layer 2.
which will then give you the LinkMap for issue QTWB-30 with layer 2.
Alternatively, you can access the test instance of Qt's jira https://bugreports-test.qt.io/secure/Dashboard.jspa and search for an issue. On the view page you can scroll down Issue Links, underneath this you will find OpenReq Dependency Browser (old name, needs to be updated to OpenReq Link Map)
You then can use the node filter, to filter the link map for the status, type or priority. Per default, issues with status done are not shown.
To check a release plan for inconsistencies in the issues and links, you can use the consistency checker. It searches the link map up to depth 5 for inconsistencies. It also lists all releases and the found inconsistencies.
The link detection searches for an issue potentially linked issues which are not linked in Jira. These missing links are then recommended and can be accepted or rejected by the users. Currently these changes are not written to the Jira database.
Visualising the link network, recommending missing links and checking the consistency of your release plans.
- Editing links on the fly
- Transform this from a web-application to a jira plugin
Only the public issues are available. If a person has a Qt account, they should be able to see all the issues In the link map that they would be able to see in JIRA. Additionally, the ability to accept, reject and edit links need to be tied to the permisisons the user has in Jira.
The service sends a request (JIRA keys, e.g. “QTWB-30”) for data to milla and receives a JSON with the issue data. This data is then visualized.
I tried to comment most of the code to make it understandable. The Java part just gets the data in a vis.js friendlier format. The javascript & HTML/CSS will get some more functionality in the next iterations.
See OpenReq project contribution guidelines.
Free use of this software is granted under the terms of the EPL version 2 (EPL2.0).