Hi,
I am looking for advice about the best way to manage traceability from business (aka marketing) requirements to development tasks (aka product requirements). Currently, our business requirements are in Confluence, and our development requirements are in Jira in the form of epics, stories, and subtasks. The relationship between the business requirements and the dev requirements is many-to-many. (One epic can support multiple business requirements, and one business requirement may require multiple epics to be implemented.)
At one point we considered putting the business requirements themselves in Jira, but we were concerned that it would be more difficult to review - both because you need to open each issue to see the details instead of reading through a single page; and because we don't currently have an add-on that would allow us to easily see issues in a hierarchy view if we wanted to nest requirements. We briefly considered having the requirements duplicated in Confluence and Jira, but rejected that option as too likely for things to become out of sync and it undermines the idea of having single-source-of-truth.
Our best idea so far is to add Jira links to the relevant epics in-line next to each business requirement in Confluence. A requirement being edited in Confluence would prompt a review of the linked epics to determine if any changes are needed on the development side. This process requires a large time commitment - both for creating the initial linkages and later reviewing them - so before going down this road, I wanted to ask the community for your thoughts and insights:
How does your company successfully manage both marketing and development requirements and the traceability between them?
Keeping in mind that in our case the relationship is many-to-many so we can't just add the requirements as a layer above epics in Jira, is there a way to make this process less manual/require less bureaucracy?
