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

JIRA Issue Macro standard column configuration

    XMLWordPrintable

Details

    • 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.

    Description

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

      Whenever I have a template / blueprint with a JIRA issue macro I want to predefine what columns should be displayed and how many issues will be shown.
      Behaviour right now:

      • In the blueprint / template a jira issue macro has been set.
      • when creating a new page and clicking on the instructional text for the jira issue macro, the create jira issue dialog opens. There standard values will be displayed. Always:
      • Maximum issues: 20
      • Columns to display: Key, Summary, Issue Type, Created, Updated, Due Date, Assignee, Reporter, Priority, Status, Resolution

      Wanted behaviour:

      • In the blueprint or template a user can choose how many issues will be returned by default and what columns should be displayed.
        • Example: Maximum issues: 100
        • Columns to display: Key, Summary, Status, Resolution

      My use case:
      I create a product requirement where a requirement has 2 EPICs. As soon as I insert two Epics - I do not want to use 2 jira issue macros - I get a table with predefined columns. However, I only really need these Columns displayed: Key, Summary, Status, Resolution. Because in the requirements document I really don't need more information...

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              ff4f8be99eea Andrea Tanzer
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: