Thomas and myself discussed last week briefly about how to manage JIRA for the modules, my initial idea was to create one JIRA per module but it has drawbacks (mainly to create redundancy).

Thomas suggested we could try to use the same JIRA but create versions per module x release, so we are going to try that for a while and see how it works. It has the benefit of being doable easily. I think the main cost we will pay in the increase of the complexity but it can be manageable somehow.

So I have created the following versions:

Common-1.0
Web-1.0
Identity-1.0
Portlet-1.0

and marked them as "released", they are just used as identifier for the "affect" version field.

and I have also created:

Common-1.0.1
Web-1.0.1
Identity-1.0.1
Portlet-1.0.1
Common-1.1
Web-1.1
Identity-1.1
Portlet-1.1

That can be used for "Affect" and "Fix" version fields.

Any issue that matches a module version could also match a 2.6.x versions. For instance if there is a bug in common that it is fixed in 1.0.1 and 2.6.3.