All issues inside the ENTESB should have "Component". The component should reflect the product to which it aims or where it should be fixed/enhanced. By having the high-overview component and better categorisation, we could have better statistics and then we couldn't have to use filter for Standalone/FoO like "Component not in ("Fuse Online, Data Integration, Apicurito)". It would help Standalone and FoO QE to not go through all the issues that are missing component.

In Fuse 7.x stream, we ship following products/subproducts/deliverables:

• Fuse Standalone
• Fuse On Openshift
• Fuse Online
• Data Integration (DV)

For Integration.Next, we will ship:

• Camel-K -> already exists
• Camel Quarkus -> already exists
• Fuse Online -> already exists
• Data Integration
• Camel 3 -> it is still not product
• Camel Kafka Connect -> currently the name Kafka Connect is part of Kafka Ecosystem

That means for Fuse 7.7 mandatory options should be:

• Fuse Standalone -> missing (Viliam added it and started to using it)
• Fuse On Openshift -> exists
• Fuse Online -> exists
• Data Integration (DV) -> exists

For Integration

All other options that already exists should be categorised under these main components.

Fuse Standalone:

• Camel
• Karaf
• Fuse EAP
• CXF
• Hawtio
• Build
• Quickstarts -> Fuse Standalone and quickstarts distribution

Fuse On Openshift:

• quickstarts
• Fuse Console

Fuse Online:

• Atlas Map
• Apicurito

Data Integration:

• DV - UI
• DV - backend

All main components could have QE component. By this, QE could onboard to ENTESB and track all QE task relevant to product here.