Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-38067

Variables in the JIRA Issues Macro

XMLWordPrintable

    • 1
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      It would be very powerful to allow the JIRA Issues macro to use variables.

      Another way to phrase this would be allowing end users who don't have permission to edit a page configure the results of the macro.

      Another use case would be the curator of a page providing a JIRA Issues Macro that could be used to track the results across a few different projects, allowing the user to select one.

      A third use case would be automatically passing in the user accessing the page as a variable, and returning results relevant to them.

            [CONFSERVER-38067] Variables in the JIRA Issues Macro

            Adam Barnes (Inactive) added a comment -

            Thank you for raising this suggestion.
            We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.
            For more context, check out our Community blog on our updated workflow for Suggestions
            Cheers,

            Confluence Product Management

            Adam Barnes (Inactive) added a comment - Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our updated workflow for Suggestions Cheers, Confluence Product Management

            Catherine Lee added a comment - - edited

            This was actually allowed when we used 3.5.4. Now we are trying to upgrade to 5.7.1 except we are losing the ability to enter a label and bring back a query. Below is the wiki markup we were using: 

            || Label | {text-data:label|type=area|width=15%|height=20px} ||
{report-on:injected=true}{jira:labels="%data:label%"  ORDER BY key ASC, fixVersion ASC, summary ASC|server=Pragma Securities JIRA|columns=type;key;fixVersion;priority;summary;assignee;reporter;Dev Estimate;status;resolution}{report-on}

            Catherine Lee added a comment - - edited This was actually allowed when we used 3.5.4. Now we are trying to upgrade to 5.7.1 except we are losing the ability to enter a label and bring back a query. Below is the wiki markup we were using: || Label | {text-data:label|type=area|width=15%|height=20px} || {report-on:injected= true }{jira:labels= "%data:label%" ORDER BY key ASC, fixVersion ASC, summary ASC|server=Pragma Securities JIRA|columns=type;key;fixVersion;priority;summary;assignee;reporter;Dev Estimate;status;resolution}{report-on}

              Unassigned Unassigned
              ldally lachland (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: