And to note we also do have an internal JIRA instance and are struggling on how to best capture requests for new development work with associated metadata, like stakeholders, and the content of the requirements without having to duplicate information both on our internal instance as well as in the outside instance. Would love to know how others approach this.
we are having the same issue. We're starting to capture software requirements in confluence, but also have a separate instance for JIRA that our outside development team owns. We need to document requirements and metadata internally as well as in the JIRA instance our dev partner manages. And copying and pasting and re-formatting from wiki–>JIRA is a huge pain
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Why copy and paste? Why not just link the JIRA issue with the Confluence page or text?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.