You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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
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: https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-screens/
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:
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:
Please note that would remove the Description for any issue / project using this description.
I'm afraid this is a "red herring" - this has nothing to do with field configurations.
I'm sorry, but that article is a red-herring too - it's not screens either.