nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

system field

Muzaffar Abbasov_tu2ngr

Hello

I have Jira on-premise version Jira v9.12.9

It has system field 'Тема' (Topic), and it is required.

I have configured several screens without the field. I have configured fields scheme. But there is no permission to set the field unrequired.

And now I can't create issues, because the field is required, even though it is not on the interface. How can I turn off required system field?

Accepted answers

All comments

Tomislav Tobijas

Hi @Muzaffar Abbasov ,

I'm not sure if 'Topic' is a system field (at least I've never seen it on systems that we configured).

So, you've checked the field configuration scheme and field configuration that is assigned to this project where you're experiencing this issue?

Can you share (screenshot) which specific message is being displayed when you try to perform a status transition?

Additionally, I would recommend checking workflow and workflow validators to see if, potentially, this field has been set as required there as well.

Cheers,
Tobi

Muzaffar Abbasov_tu2ngr

@Tomislav Tobijas , thank you for your reaction.

It got clear after I switched interface to English, instead of Russian. Obviously, translation was wrong, and differs from the cloud version. It was Summary field, which is required.

So I got another question:

Why Summary and Epic Name fields are required at one time?

Tomislav Tobijas

@Muzaffar Abbasov Summary is definitely required as you would get 'broken issue' if the one didn't have it.

I'm guessing the question is why are both fields required if they represent the same thing? 👀

As for Epic Name, I know that on the cloud this was actually replaced with Summary field, but, potentially, on the older DC version this is still required (for Epic issue types). I could ask around with my colleagues who work with DC to see if they got any additional insights if you like.

Maybe, on newer DC versions, Epic Name is not a required field anymore.

Muzaffar Abbasov_tu2ngr

@Tomislav Tobijas , yeah, you got it right. The question is the one you've stated:

Why both 'Epic Name' and 'Summary' are required for Epic issue type, if ther represent one thing?

Currently we have on-premise version Jira v9.12.9.

And my automation for copying to Epic Name field when Summary field change - isn't working

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-on-premise