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

Hi, Why you would move a feature into rejected closed without any additional information on fix . Edited

I used Jira a few years back (not very frequently) so please be patient with this one :) 

In my new role I've noticed a lot of the features are in a rejected closed status , without going into each one on the board why would this be. . as the information is very limited as to why .

Also any recommendations for good jira practice .


2 answers

2 accepted

0 votes
Answer accepted
Tessa Tuteleers Community Leader Jan 12, 2021

Hi @Angela Joy Waters , 

Welcome (back) to the community! 

The information in your question is pretty limited too, and the why can be very very different.

A Feature request in the Closed status with resolution "Rejected":
we could assume that new features can be requested by any number of users, and development does not have time to implement all the requested features, especially if some are not in line with the vision of the product owner and envisioned roadmap. 

Thus certain requested features can be closed with resolution Rejected, although one might hope a - small - comment is added with explanation.

Should you have any more questions or I misunderstood, let me know! 

- Tessa

0 votes
Answer accepted

I'd say you need to do some work with your product owners and development team - just remind them that if they reject something, there should be a (brief) explanation of why it's closed as rejected.

Worst case - take the passive-aggressive route of re-opening the issues and with "no explanation for closure" type comments.  Or raising duplicates over and over until they get the message.  I strongly recommend not doing this, talk to them first.

Thanks I’ll do this.

From what I can gather and with it being a new role.  The explanations are very brief , such as duplicate, or this has been resolved under another feature, is this work worth doing considering this isn’t planned until cuz etc.. it’s more behind why they would use this .

I will definitively work closer with the PO and dev teams to understand their reasoning .

thanks so much 

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