We are in the process of deciding how to manage a requirements database, and are considering implementing through a cloud instance of Confluence. Currently, we use a cloud instance of JIRA to manage work and tests, and want our requirements to live there and link to those items as well.
I looked into defining requirements in a table through the provided requirements document template and creating them as issues in JIRA. This works for ticket creation, but after the issues are created, there's no active updating between the table of requirements statements in the confluence document and the issues now existing in JIRA.
This makes the feature minimally useful -- it allows for the requirements document and the requirements issues off which work will be based to drift and deviate from each other.
It appears that 'Requirements Yogi" solves this problem, but that is only for a server implementation. Is there a way to get this functionality with cloud versions?
