Build split issue tree

[rexim]

This issue has been split in #21

Pieces

• Initial implementation of REST API #14 Initial implementation of REST API
• Build split forest from the actual GitHub's data #22 Build split forest from the actual GitHub's data
• Display split forest on Issuestant's web UI #23 Display split forest on Issuestant's web UI

---

Description

I should be able somehow to tell (hardcode is ok at the moment) to Issuestant to gather all of the issues from a project, analyse their split links, build a split tree and visualize it on the Issuestant's web UI. Manual request to update the tree is ok at the moment.

Split Tree

Split tree is a tree where each node is an issue. Issues that contain Split from # in there description are considered to be children of issue . It's more correct to call that "Split forest", because there is no single root. But creating artificial root is ok. Could be just the name of the project.

If issue xmppo/Jabber-Net#2 contains Split from #1 in the description, the split tree will look like:

ForNeVeR/Jabber-Net#1
|\
| ForNeVeR/Jabber-Net#2
.
.

[ForNeVeR]

What's the definition of "split tree"? Will it include issues like xmppo/Jabber-Net#1?

[rexim]

What's the definition of "split tree"?

Split tree is a tree where each node is an issue. Issues that contain Split from #<id> in there description are considered to be children of issue <id>. It's more correct to call that "Split forest", because there is no single root. I'll change the description later. Maybe.

Will it include issues like xmppo/Jabber-Net#1?

By definition, no.

[ForNeVeR]

So it will include issue like xmppo/Jabber-Net#1 if I put in description of, say, xmppo/Jabber-Net#2 the message like "Split from # 1", right?

[rexim]

It will include both of them, they will look like:

ForNeVeR/Jabber-Net#1
|\
| ForNeVeR/Jabber-Net#2
.
.

[ForNeVeR]

Thanks. That's exactly what I'd like to see!

[rexim]

I like the fact that this issue is split.