Use JIRA Structure as navigation tree on linked Confluence content
JIRA & Confluence are often used hand-in-hand... e.g. new ideas are formulated on CFL, leading to linked tasks in JIRA & followed by documentation etc.. on Confluence again..
The need to reorder issues in JIRA, & use structure to navigate them, can be projected to linked confluence contents as well.
The way i see it, structure widget could replace the space navigation panel.
JIRA issues & corresponding Confluence pages could be linked via labeling (value == structure item ID)
This is the idea in a nutshell, I'd be happy to discuss in more detail if helpful.
Here is a slight variation with a different use case. I'd like to see a column in my structure that shows a list of confluence pages linked to the JIRA issue. Folks still like to start navigation in JIRA then get into supporting content in Confluence.
Ben De Pauw commented
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)
Thanks for your idea. This is quite ambitious and somewhat outside our current scope, but we might get to it later. One of the possible directions where Structure may evolve is organizing/structuring all kinds of artifacts, including Confluence pages.