Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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
Answer accepted

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 Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you