It's all about the answers!

Ask a question

Is there plan for integrating github issues with RTC?

Mojgan Samifanni (11) | asked Jul 12 '18, 11:44 a.m.

Is there any plan for linking the github issues with RTC stories or tasks?

3 answers

permanent link
Lakshmi Narasimhan T V (4415) | answered Jul 18 '18, 11:44 a.m.

You can add GitHub issues as "Related Artifact" links to a RTC task or story. Is that what you are looking for? Could you elaborate on your use case?

Mojgan Samifanni commented Jul 19 '18, 11:23 p.m.

Thank you Lakshmi for your response.

We have backlog in both RTC and Github and we would like to have one place for tracking the backlog.

permanent link
Guido Schneider (3.4k1385115) | answered Jul 19 '18, 5:07 p.m.
edited Jul 20 '18, 2:51 a.m.

 Hello Mojgan,

Please have a look into our Opensource Project "RTC-Git-Connector" on

The RTC-Git-Connector is supporting GitLab as well as GitHub. Below I will use the common term Git for both variants. It's complementary to the Git Integration package from IBM, which is Git -> RTC communication based.

It allows you to link existing commits, issues or merge requests to an existing Work Item.
Additionally you can create out of a Work Item, a linked and pre-filled Git-Issue. 
It supports also Git-Issue templates to build the Git-Issue description by using values of any attribute of the Work Item. Markdown is supported, to convert RTC Rich text to Git Markedown.
Our Rich Hover service supports live data from Git. Login is done by personal access tokens to a registered Git repo. Git repos are registered the standard way from RTC.

Next version, coming soon, will support two new Link Types on RTC. Git Issue and Git Merge Request. With this you can better write queries in RTC to find e.g. all stories with linked Git Issues. We are also developing a new Work Item Editor presentation, which allows you to show the linked Git artifacts in a table with actual state etc. information.

Together with the Webhook Receiver from the IBM Git Integration (RTC V.6.0.5), on the linked Work Item, you can receive also Discussions done on Git.

Main use cases we fulfill with this is
-  the integration of Git Developers (internal and externals) into the SAFe Agile Release Trains (ART). So projects can plan their Epic's, Features, Stories according the process (e.g. PI Planning Meetings) but the developer in the team get the work order as an Git Issue in the Git repository. So he can develop against a Git Issue. But the Scrum master and RTE is able to trace the progress out of RTC.
- when a product defect comes out of the field or out of system testing (e.g. RQM), it ends as a defect in the ART backlog. The Change Control Manager (CCM, e.g. Scrum Master) can now assign the Defect to a developer as an Git Issue and the developer can solve it on Git. The CCM or test manager sees the progress and can initiate retesting when the Git Issue is solved. The retesting can then be done on RQM.
Have fun
Guido Schneider

Mojgan Samifanni commented Jul 19 '18, 11:25 p.m.

Thank you Guido for your response,
Is gitlab one of the requirement for RTC-Git-Connector?

Guido Schneider commented Jul 20 '18, 2:52 a.m.

I updated the description above. 

permanent link
Geoffrey Clemm (30.1k33035) | answered Jul 20 '18, 12:29 p.m.

If the question is whether there is an integration that allows Git issues to appear in RTC plans or RTC queries, the answer is "no", and that answer is unlikely to change.   If the question is whether you can use RTC reporting against both RTC work items and Git issues, then that is something you could add yourself by creating a TRS feed for Git issues.   I know there are some teams working on this (or at least, considering doing so), but I'm not aware of any having been released yet (please post, if you know of one).

Guido Schneider commented Jul 20 '18, 12:49 p.m.

Hello Geoffrey,

note, in addition to my answer above, about the OSS project for a RTC-GIT-Connector, we are working currently on an ETL/DCC Job which writes the required information of a linked GIT Artifact (Issue/Merge Request/Commit) into the DataWareHouse, so we can build traceability reports with Report Builder.

We have not yet decided if we also want to feed the data into LQE. Currently only our rich hover and Work Item presentation implementation has a an OSLC gateway service between RTC and GIT. All the rest is direct GIT API.

If you know other companies working on such integration's, or are building a full OSLC gateway, please motivate them to work with us on the Jazz-Community OSS projects.

Btw. The Git Commit information is already in LQE as well as in RTC-Query available, but in a bad format (a gzipped JSON). This is a Defect I wrote, but it was changed to an enhancement. I think it would be quite simple at least having this information available in a usable format within LQE.


Geoffrey Clemm commented Jul 20 '18, 3:36 p.m. | edited Jul 20 '18, 3:39 p.m.
Good point that ETL/DCC support also would make the non-versioned GIT data available for reporting with RTC work items (but the data warehouse does not support versioned data, so I tend to focus on LQE reporting, which handles both versioned and non-versioned data). 
Could you expand on what you mean by "RTC-Query available"?   When I referred to RTC query in my answer above, I was referring to the RTC work item query mechanism, which to my knowledge, is not extensible to access information from other repositories.  Perhaps you mean "queryable via LQE"?   If so, I would call that LQE-Query available (:-). 

Guido Schneider commented Jul 20 '18, 4:43 p.m.

Sorry my wording was not exact.

I mean within RTC query it's possible to query for existence of links to a Git Commit. The display value shows some minimal information. This is OOTB functionality of 605.

With our extension by introducing two new link types for Git Issues and Git Merge Requests, we can query for existence of links to this artifacts. Unfortunately we are not able yet display values of the Git artifacts.

E.g. give me all defects with a linked Git Issue. 

If you have a hint how to expand the display values in RTC query system we may expand this to get e.g. status/owner/milestones etc from it. (Of course totally unsupported)

An absolut hot feature would be to show linked Git Issues similar to tasks on a task board as execution items. This would be Switzerland of Git integration.

Geoffrey Clemm commented Jul 20 '18, 5:31 p.m.

Yes, in RTC query you can query for the existence of links that are stored in RTC but point to artifacts in another repository (I consider those to be "RTC links" since RTC owns the link).   My understanding is that RTC queries can only reference data that is in the RTC repository. 

Your answer

Register or to post your answer.