Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Remove a status from "Epic Status" field

I am trying to add the "Epic Status" filed in the close screen, and it had 4 options 

  • To Do
  • In Progress
  • Done
  • Collaboration Vision

Is there any way to remove "Collaboration Vision" option so that it will be easy for the users to select Done as a status and mark the epic as done.

2 answers

0 votes

Hello Praveen,

Thank you for reaching out.

I understand that you would like to make sure the users in Jira will select Done in the "epic status" when marking the Epic as done. Is it correct?

Unfortunately, there is no way to remove the status of your "Epic Status" field since it is a locked field (see JRACLOUD-64188 ), however, you can configure a post function to automatically select the status as done when closing the Epic.

Both applications below provide you with the post function:

Scriptrunner - Use the post function to set issue attributes

JIRA Suite Utilities - Use the post function Update issue custom field

Let me know if this information helps.

This is a pretty old post, but I wanted to comment on it as it impacts me as well... To the OP's point, "Collaboration Vision" looks to be a value that was added to the Epic Status custom field during a system/project import (at least that's how it happened for us when we had a custom value in Epic status called "READY FOR WORK" (yes it's obnoxiously all caps) added to the available values in our system. 

Because of that, I don't believe that setting an post-function automation is an acceptable solution here (I'll comment on the JRACLOUD-64188 ticket as well, but that sometimes doesn't yield results). The OP I believe is requesting to have NON-DEFAULT OPTIONS to be editable to be removed. Does anyone know if this is set just by what values exist in Epic Status on Epic tickets? So if we try to do a bulk change to get rid of it, will it remove it from being an option? I might look to see if that's something that Automation for Jira can handle. But to figure out how Epics even get into that Epic Status also remains to be seen to me.

Suggest an answer

Log in or Sign up to answer
TAGS

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