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?
Hello @Pete Conti,
Thank you for contacting us about this. I noticed that you were able to raise the same question with Support, so I will summarize what they said for other users.
The following feature request was made on your behalf:
The ticket created should be added automatically to the table as a link, but this is not occurring due to the following bug:
Regarding Requirements Yogi, they recommended that you get in touch with the vendor to see about their plans to implement a cloud version.
Do let me know if you had any further questions!
Regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.