[JSWSERVER-7104] Opinion - epic query parameter should use issue key instead of issue ID - Create and track feature requests for Atlassian products.

This issue is archived. You can view it, but you can't modify it. Learn more

Type: Bug
Resolution: Not a bug
Priority: Low (View bug fix roadmap)
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Bug Fix Policy:
View Atlassian Server bug fix policy

Obviously we can't use name because it is not unique, but we don't tend to use issue IDs any where else in semi-user facing situations.

is detailed by

JSWSERVER-6616 Show table at bottom of single Epic report that shows the estimate (current) for Done, Undone - Estimated, and Undone - Not Estimated stories

Closed

is superseded by

JSWSERVER-7106 Opinion - "View in Issue Navigator" links could be generated differently

Closed

Assignee:: Unassigned

Reporter:: Michael Tokar

Archiver:: Michael Andreacchio

Created:: 09/Jan/2013 10:56 PM

Updated:: 12/Sep/2019 6:24 AM

Resolved:: 10/Jan/2013 5:32 AM

Archived:: 12/Sep/2019 6:31 AM

Jira Software Data Center

Details

Description

Attachments

Issue Links

Forms

Activity

[JSWSERVER-7104] Opinion - epic query parameter should use issue key instead of issue ID

People

Dates

Backbone Issue Sync