need of bridge table

we have issues logged at

1. asset level
2. applicaiton level
3. process level
4. line of business level
5. combination of each of the above entities.

We planned to have dimension table for each entity (asset, application, process and line of business)
and a fact table which would have keys of all these dimensions and measures as ratings, score and status

As per the current requirement an issue can have multiple assets\applications\line of business.

So for this kind of scenarion can i have bridge table between the fact table and the respective dimension table?

You need to think about this differently.

The grain of the fact table determines the requirement for a bridge.

A bridge is required when a single fact record needs to join with multiple dimension records.

As I responded to your previous post of the same question, I do not think a bridge table is appropriate unless this is a strict hierarchy. From the descriptions of the dimensions, it does not look like it. In such cases a fact with all the dimensions as independent foreign keys is the appropriate way to handle it.