I agree, the fix version right now isn't clear enough for tracking issues.

Right now 'Fix Version' and 'Affects Version' reflects the version of ejb3-core which we are using.

So at least for the three distributed artifacts I think we should have versions:
1. as-int
2. embedded
3. plugin

We now also have the option on using 'Component Fix Version(s)'.

Component/s: interceptors
Affects Version/s: None (what do we use here? the version of component or the distribution)
Fix Version/s: 1.a.b, 1.p.q (Again how do we distinguish 1.a.b corresponds to as-int and 1.p.q to plugin)

Component Fix Version(s): 1.x.y (this corresponds to interceptors version)

Thinking a bit more, how about something like this:

* Affects version will refer to distribution versions (like as-int, plugin, embedded) [1]
* Fix version will refer to distribution versions (like as-int, plugin, embedded)
* Component Affects Version - If some field like this could be made available, then we could use this to refer to each component's version. This field would in most of the cases be set by us and not usually by end users reporting the issue
* Component Fix version - Refers to the component version

[1] Still how do we distinguish 1.a.b version of as-int from 1.p.q version of plugin. Unless the versioning in JIRA is something like as-int-1.a.b and plugin-1.p.q