Hi Igor, I realize it's a big ask indeed..
we happily use structure to provide a functional classification view (domain-area-case-scenario) on our JIRA issues. This same classification applies to other artifacts indeed, e.g. requirements (Confluence), helpdesk issues (diff JIRA instance), test management (JIRA), release notes/knowledge base (Confluence), ..
We are currently evaluating to replace some older propriety systems to Confluence & JIRA only, hence this the missing link in the picture.
Probably a separate structure plugin for Confluence would make most sense here, where option exists to link it to a JIRA structure, or use it irrespectively of JIRA (e.g. via hierarchical labels)
Hi Igor, I realize it's a big ask indeed..
we happily use structure to provide a functional classification view (domain-area-case-scenario) on our JIRA issues. This same classification applies to other artifacts indeed, e.g. requirements (Confluence), helpdesk issues (diff JIRA instance), test management (JIRA), release notes/knowledge base (Confluence), ..
We are currently evaluating to replace some older propriety systems to Confluence & JIRA only, hence this the missing link in the picture.
Probably a separate structure plugin for Confluence would make most sense here, where option exists to link it to a JIRA structure, or use it irrespectively of JIRA (e.g. via hierarchical labels)