@davvd, thank you, I begin working on it.

@yegor256, I have some questions:

1. How do you want me to connect them? By mentioning UCXX in their names?
2. What columns will there be in the summary table? This is what came to my mind:

   • Name (as a link to the issue)
   • UC #
   • Status. Could be:
     • In progress,
     • Closed.
3. Where should I put the table, just in this issue?

I think that we should create a new "facet" (configurable with Github OAuth key). This facet will read all Github issues and check which of them start with UCnn. If such an issue is found, it will add this information to the XML, like all other facets are doing. Then, in requs.xsl we should render this data, next to use cases. It's a big ticket to implement, so don't rush. Let's discuss first and make sure we're on the same page. Also, don't forget about PDD: http://www.xdsd.org/2009/03/04/pdd.html

@yegor256, thank you, I think now I understand enough for the start. I will begin with building requs and analyzing how it works.

Then I will make a dummy facet and put puzzles in it and in XSLTs. I think many questions will arise at this stage. Now I see only one question: where to store github repository URL and OAuth key, in pom.xml in /project/build/plugins/plugin/githubConnection?

good question. requs is not configurable now at all. we can't pass any parameters to it, but we should have this feature. it's also a good candidate for a new issue