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

As a Confluence user, I want to specify an Epic link when creating a new JIRA issue of the type "Story" with the Insert JIRA Issue macro of Confluence

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • We are using the web-environment of Confluence version 5.3 (Chrome) on a Windows 7 machine
    • 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.

      Currently I'm unable to immediately specify an Epic link when I'm create a new JIRA issue of the type "Story" when using the JIRA macro on confluence.

      There is no field shown to optionally specify this.
      When I want to create an epic link, I have to go to the newly created JIRA issue and specify it there.

            [CONFSERVER-32262] As a Confluence user, I want to specify an Epic link when creating a new JIRA issue of the type "Story" with the Insert JIRA Issue macro of Confluence

            Sen Geronimo made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3570389 ] New: JAC Suggestion Workflow 3 [ 4333929 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3173922 ] New: JAC Suggestion Workflow 4 [ 3570389 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3029855 ] New: JAC Suggestion Workflow 2 [ 3173922 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2530305 ] New: JAC Suggestion Workflow [ 3029855 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2284897 ] New: Confluence Workflow - Public Facing v4 [ 2530305 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 - TEMP [ 2178901 ] New: Confluence Workflow - Public Facing v3 [ 2284897 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 1944864 ] New: Confluence Workflow - Public Facing v3 - TEMP [ 2178901 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v2 [ 1761779 ] New: Confluence Workflow - Public Facing v3 [ 1944864 ]
            jonah (Inactive) made changes -
            Description Original: Currently I'm unable to immediately specify an Epic link when I'm create a new JIRA issue of the type "Story" when using the JIRA macro on confluence.

            There is no field shown to optionally specify this.
            When I want to create an epic link, I have to go to the newly created JIRA issue and specify it there.
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-32262].
              {panel}

            Currently I'm unable to immediately specify an Epic link when I'm create a new JIRA issue of the type "Story" when using the JIRA macro on confluence.

            There is no field shown to optionally specify this.
            When I want to create an epic link, I have to go to the newly created JIRA issue and specify it there.
            jonah (Inactive) made changes -
            Link New: This issue relates to CONFCLOUD-32262 [ CONFCLOUD-32262 ]

              Unassigned Unassigned
              9dcccecd0dd9 Ben Hermans
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: