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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Can some will help me out how to remove the Status "All subtasks are not Ready for Approval"


Can some will help me out how to remove the Status "All subtasks are not Ready for Approval"

Please find the below screenshot.


where can i check this extra status i want to remove this one from the form.

3 answers

0 votes

The field you have highlighted is not a status.  The status is "under review".

It is the resolution of the issue, set when "this issue needs no further attention".  You should only ever resolve an issue when it is going into a "closed" status.

Your screenshot is of what I call a "quantum issue" - it is both open and closed at the same time.  Jira can't report accurately on these because they are in two states simultaneously.

An inexperienced admin has made a right mess of your system from what I can tell.  This is not the first time you have asked about resolutions that should not be there.

Your admins need to

  • Go through all your screens, looking for "Resolution" and remove it from any screen that is an edit or create screen.  It should only ever be placed on transition screens.
  • Go through all your workflows to make sure that 
    • Resolution is set by a post function when moving into a closed status
    • Resolution is on the transition screen when moving into a closed status (note - if you're going to use a screen to ask the users, do not use a post-function as well)
    • Resolution is cleared when transitioning into an open status from a closed one
  • Go into the list of resolutions and change all the broken ones like the one you have got here to be named "do not use me"
  • Identify all the issues using a broken resolution and clear it - not set it to something, but clear it so that the field has no value.  This could be a mammoth task for which you should be looking to tools to script or automate it
0 votes

Hi @Sreenadh :

if this is field you are using then you have to check in the Create, edit and View screens for that particular issue type in project settings.

Please, refer this document:



Mahesh Shinde

0 votes

Hi @Sreenadh 

If it is done via the Field Configuration Scheme - to remove this you'll need to be a Site Admin and then follow the below steps:

  • Select the Jira Settings cog icon (on navigation bar in top-right)
  • Select Issues
  • Go to Field Configurations Schemes
  • Locate the Scheme in use for this project and select it
  • Locate the Field Configuration in use for this issue type and press Configure
  • Locate this field and press Edit
  • Remove the Description and update

Please note that this will remove the text for all issues / projects using that Field Configuration.

If this doesn't work - then it could be the default description as part of the Custom Field. To remove it from there:

  • On Issues in the Admin Settings, select Custom Fields
  • Search for the field and under the cog options, press Edit
  • Remove the Description and update

Please note that would remove the Description for any issue / project using this description.

Sushant Verma

Hi @Sushant Verma 

Sorry it is not working please let me know if there are any possible ways for the same.


Hi @Sreenadh 

Please follow below once. Hope it will work :

Sushant Verma

I'm afraid this is a "red herring" - this has nothing to do with field configurations.

@Nic Brough -Adaptavist- Yes Nic my bad, that is why I have provided above article. Might be that will help him out.

Sushant Verma

I'm sorry, but that article is a red-herring too - it's not screens either.

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events