JQL and Page variables

Like any wiki the usefulness of the content is equal to the time and enthusiasm to put data into the portal. As a company we have had numerous false starts at creating an environment that is embraced by the employees (share point, Wiki's of various types, smb shares etc). All technologies we have tried have failed due to them being unstructured across product lines and teams, and have eventually been abandoned or become messy black holes, from which we can never mine information.

In moving to the Atlasssian suite of tools/products we have decided to take a proactive effort in templating spaces for the product lines, to provide common look and feel and familiarity to the users. In creating these spaces we have seen many challenges some of which we have in part solved with 3rd party plugins and macros (not ideal but workable). however there is one feature that was not solvable and create's significant work when using the space template to create new spaces and maintain ongoing.

Many of our pages contain JQL queries tying JIRA to CONFLUENCE Pages. Though the queries are 90% the same across product/project (s) fields such as 'project' and 'fix version' are not for example. In an ideal world it should be possible to create variables in a confluence space or in-tree parent page which is available to all child pages. The variables could then be usable in JQL queries. or Label definitions and ultimately plugin and macros etc.

This feature would save our company alone a world of hurt and time.