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

Enforce unique Epic Name for each Epic

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • AgileBoard
    • 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.

      Problem Definition

      Currently, JIRA does not enforce unique Epic Name for each Epic. This could cause confusion when users try to add Epic Name to issue and JIRA could have suggest more than one Epic with same Epic Name.

      Suggested Solution

      Enforce unique Epic Name for each Epic

      Workaround

      None

            [JSWSERVER-16366] Enforce unique Epic Name for each Epic

            Gosia Kowalska made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3069782 ] New: JAC Suggestion Workflow 3 [ 3659845 ]
            Andy Nguyen (Inactive) made changes -
            Link New: This issue incorporates JSWSERVER-15878 [ JSWSERVER-15878 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2627097 ] New: JAC Suggestion Workflow [ 3069782 ]
            SET Analytics Bot made changes -
            Support reference count New: 1
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2515827 ] New: Confluence Workflow - Public Facing v4 [ 2627097 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Vicknesh Shanmugam (Inactive) created issue -

              Unassigned Unassigned
              vshanmugam Vicknesh Shanmugam (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: