I am developing a software for e-commerce on jira software which I need to closely monitor. It’s a agile method of team managed project.
Typically Agile projects put stories into individual "story" issues with one story in an issue all tied together using epics to larger "features".
The missing piece here is a document or collection of documents that outlines the broader goals that all this fits into. Confluence can fulfill this role.
Imagine that you create a Confluence page with the business goals of your project, the competitive market, including the specific features that you need. Then for each feature you link to a sub-page that has more information and the implementation details. Possibly including the stories.
You could then use these pages to create stories in Jira. In each page (corresponding to a feature) you can list the actual Jira issues that were created. This would allow someone looking at the Jira issue to easily find the pages (as Jira automatically puts a link on every ticket to the page where that ticket is "mentioned", that is, linked).
Now people can add detailed information about specific features and stories to Confluence and anyone looking at a specific story can link back to find how this relates to the broader picture.
Of course each one of these pages is part of a larger Product section so by following the the parent links one can see how this feature relates to the product as a whole and to other features in the product.
This is all now a living document which can be kept up to date by the Business Owner and the Stakeholders and used as a guide to evaluating the Sprint Review.
And, of course, the Sprint Planning and Retrospective can also be documented on Confluence AND tied to the Feature pages AND to the specific tickets.
Properly organized, Confluence can form a network of information and links to information that ties everything together and makes every piece of information easy to find.