Loading...

XML

Word

Printable

UIS:
14
Support reference count:
6
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.

NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

So I've got a long list of components and issue types, e.g:

In https://jira.bepress.com/secure/project/DeleteComponent!default.jspa?cid=XXXX ,
If these issue types or components are in use, Jira makes me reassign them before deleting them.

Instead I'd like to deprecate them, so they can't be assigned to new tickets, but history is not changed.

My goal is to reduce clutter, when issue types are no longer relevant for new tickets.

The same comment applies to several areas in the administrative GUI. I want to "ghost out" old stuff, without changing history.

is duplicated by

JRASERVER-26016 Retire Issue type

JRASERVER-32915 Provide ability to disable an issue type in an issue scheme

relates to

JRASERVER-10507 Archive project components

JRACLOUD-16683 Ability to archive (deprecate) issue types (Issue Type Scheme) while keeping them on existing issues

(2 mentioned in)

Estimated:

40h

Remaining:

40h

Logged:

Not Specified