Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-10115

Improve the XML view of the Epic Link and Sprint custom fields so that the Confluence Issues Macro can present better information

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 1
    • We collect Jira 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

      Today we export the value of these fields as simply:

      • issue key of Epic linked to an issue
      • ID of the sprint

      We can supplement this information with the "display name" of those values, so that consumers of XML views of issues can better render the values. An example of this is Confluence's Issues Macro.

      Attachments

        Issue Links

          blocks

          Suggestion - CONFSERVER-31534 When Epic Link is chosen as a display field in the JIRA macro, it should show Epic Name.

          • Closed

          Activity

            People

              Unassigned Unassigned
              mtokar Michael Tokar
              Votes:
              14 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: