How to label/categorize issues that turn out to be "rejected requirements"?

[Jim Johnson]

There are some tasks (issues) in my project that are what you might call "rejected requirements".  I have marked them as "done".  Is there some other way to mark them so that they will be excluded from search, or in some way less visible, or separately categorized, short of deleting them?  

Motivation:  I'd like to leave them in the project to provide evidence that they were considered and rejected.  If I delete them, I would need to store that information elsewhere.

[Nic Brough _Adaptavist_ · Accepted solution]

Change your searches to exclude "done" issues, or add a "rejected" status to your workflow and exclude that (probably a better option) or maybe tag them with a label like "ignored" or a new custom field and exclude that from your searches.

[Jim Johnson]

Works slick!   (I decided to go with "Declined".)  Search filter is easy too.  Thanks!

[Randy Ho]

Update your workflow and add a Rejected status.