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

Show related Epic on 'Work' tab and create links to Epic or show Epic label on Details

XMLWordPrintable

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

      Apparently when dragging tickets to Epics on new Boards, no native-style JIRA links are created. The linkage between a ticket and it's Epic is only shown through (colored) labels on Board Plan-tab's listing or in Details when a ticket is clicked open and shown on the right.

      It would be nice to:

      1) Also show the colored label on Work-tab
      2) Have JIRA create actual links to Epics (so they would show as any other links)

      If (2) is not possible (and why), then we'd want the colored Epic label to be shown under ticket Details at least, when a ticket is clicked open in a new browser tab. Currently, when opening a ticket like this, there is no indication of to which Epic the ticket might belong.

            [JSWSERVER-6920] Show related Epic on 'Work' tab and create links to Epic or show Epic label on Details

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3066264 ] New: JAC Suggestion Workflow 3 [ 3659564 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2625608 ] New: JAC Suggestion Workflow [ 3066264 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2327250 ] New: Confluence Workflow - Public Facing v4 [ 2625608 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2044078 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2327250 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2032250 ] New: JIRA PM Feature Request Workflow v2 [ 2044078 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 736969 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2032250 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Martin (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 452918 ] New: JIRA PM Feature Request Workflow v2 [ 736969 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Minor [ 4 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Michael Tokar made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Michael Tokar added a comment -

            Resolving this as answered, since #2 is already addressed and #1 is in the related issue.

            Regards,
            JIRA Agile Team

            Michael Tokar added a comment - Resolving this as answered, since #2 is already addressed and #1 is in the related issue. Regards, JIRA Agile Team

              Unassigned Unassigned
              a5b9aaca9d83 Tuukka Mustonen
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: