Story / Requirements tracing in JIRA

[Rana Senojak]

On a large project how do you track / trace / report that the original story is delivered / not delivered or was changed during the development. Is there an auto function that links issues from the first version to the last version so any changes or problems can be communicated with the Product Owner / wider Stakeholder Group.

For example: Auditor needs to track a financial approval process.

The Dev Team may reword this, split it or merge with another story - this is where it gets hard to track the original story.

Note: I have read related links / answers and still not convinced I can confidently search to get accurate trace

[G subramanyam]

Hi @Rana Senojak you may try this Atlassian market place plugin bigpicture that's widely used in projects and gives a holistic view.