Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Won't Fix
Fix Version/s: None
Component/s: AgileBoard
Labels:
None

Support reference count:
1
Feedback Policy:

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

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.

Workaround

None

Attachments

Issue Links

incorporates

JSWSERVER-15878 Better handle Epic Name, Epic Link, and issue exports to HTML/CSV

Gathering Interest

Activity

People

Assignee:: Unassigned

Reporter:: Vicknesh Shanmugam (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 25/Jan/2018 12:53 PM

Updated:: 07/Feb/2022 12:50 PM

Resolved:: 27/Sep/2019 11:41 AM

Enforce unique Epic Name for each Epic