Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Remove required option from a field

Vasilis Gennaris
Contributor
March 23, 2018

How can i make a remove the default option required from a field when there is not available button for it?

 

Screen Shot 2018-03-23 at 14.19.47.png

3 answers

1 vote
Josh Steckler
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 23, 2018

You can't remove the Required from epic name. Why do you want to? This is an essential function of Epic, and this field will only ever be visible on the Epic issue type. Even if a screen you're using has the field, if you put it on another issue type such as story, it will not be visible.

Alex Christensen
Community Champion
March 23, 2018

To build on this - if you don't want your users to have to set the Epic Name field on Epics, you could technically hide the Epic Name field from the create screen, then use a post-function to set the Epic Name field automatically based on whatever the user entered in the Summary field (you may need an add-on to do this, though).

Federico Zivolo
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 19, 2022

This doesn't seem to be possible anymore, it won't allow you to create the epic even though I have an automation that would set the Epic Name to the Summary content (I also tried the opposite)

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 19, 2022

It's never been possible, you have to give the Epic name AND Summary on the create issue screen for an Epic.

The closest you can get is to choose which one you want to keep and write a post function that replaces what the user enters with the content you want to keep.

1 vote
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 23, 2018

You don't.  The "locked" next to the field means you cannot change them.

There are ways to unlock fields in the database.  But don't.  There's a good reason they are locked.  In the case of Epic Name, chunks of Jira Software stop working if the field is left empty, so it's a spectacularly bad thing to do.

0 votes
Deleted user March 23, 2018

Hi @Vasilis Gennaris,

 

The best practice is not to unlock the locked fields. The fields are locked to prevent accidental changes which can subsequently break the operation of JIRA Software. But if you still would like to unlock the fields you can check the Kb article 

How to unlock a Locked field

 

Regards,

Vijay Ramamurthy

Vasilis Gennaris
Contributor
March 23, 2018

@Nic Brough -Adaptavist- @[deleted] Actually i am not trying to unlock it, i just want to remove the required..

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 23, 2018

The lock is there to stop you breaking your system by removing the required flag.

Please, don't do it.  If you do, you will break Software in interesting ways.

Joe Pitt
Community Champion
March 23, 2018

Interesting usually means very hard to debug and issues aren't obviously related to what you did. 

Suggest an answer

Log in or Sign up to answer