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

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.

 

2 answers

1 accepted

2 votes
Accepted answer

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.

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

Update your workflow and add a Rejected status.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Featured Groups

Want to know how Atlassians monitor their enterprise deployments?

At Atlassian, we believe in our own products – that's why we use them, even at the enterprise level. Doing so gives us first-hand experience of how they perform at scale; to do this, we monitor each ...

94 views 3 9
View post

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you