Agile requirements in Enterprise SW development

Hi all,

I am new here,...so hope you can help me with ideas :-)

I am working in an enterprise SW dev company, practicing Agile around 3 years.

Our requirements include few levels: Project-->Feature-->Epic-->Sub Epic-->Story.

Lately we have come to project where one User Story is answering few requirements (Features/Epics) as per being an infrustructure or a common mechanism.

Have any of you got similar issue? do you have an idea how it can be modeled in Agile requirement, where specific dev tasks serves a specific biz requirement?

We want to be able to keep traceability as this project is very complex and big.

Thx in advance!

Shirly