system field

[Muzaffar Abbasov]

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?

[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]

@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]

@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

[Tomislav Tobijas]

@Muzaffar Abbasov my colleague just tested this and you can make Epic Name field as optional in field configuration scheme BUT, as you've stated, it's recommended to use Epic Name as well, as this value is represented in some integrations. 
The easiest solution would be to copy Summary to Epic Name value.

Regarded to this:

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

Can you share your automation rule (screenshot) and audit log and maybe I can help out with that?

[Muzaffar Abbasov]

@Tomislav Tobijas , here is the situation. When I type Summary and go on - the 'Epic Name' is still empty. When I click 'Save' - system validation stops me with the error - 'Epic Name' must be filled. 

Audit log is empty - the automation rule doesn't react at all.

BUT! When issue is created - rule works perfectly. When I change Summary - it automatically and almost instantly changes Epic Name.

Screenshot 1 shows the error.

Successfully run automation when editing existing epic

[Muzaffar Abbasov]

@Tomislav Tobijas , by the way, in field configuration I cannot disable Epic Name:

it is locked. 

Is it possible to unlock it?

[Tomislav Tobijas]

Hi @Muzaffar Abbasov ,

I've just checked w. my colleague and he said that on newer Jira versions there's this toggle to set field required/optional (you cannot and don't need to unlock Epic Name).

Once you have that, you can set this field as optional and remove it from the screen (e.g. create screen) and leave automation to do the rest.

I guess you'll still have to fill it out manually until you do the system upgrade, and once you do, just implement this 'workaround'.

Cheers,
Tobi

[Muzaffar Abbasov]

@Tomislav Tobijas , ok. so it is all clear with epic name and summary fields. we have to deal with them till we update our solution.
what about the automation - do you have any thoughts - why it doesn't work?

[Tomislav Tobijas]

@Muzaffar Abbasov , you would like for automation to automatically fill out the Epic Name field on the issue create screen? 👀

If so, that's not possible as automation is only triggered once an issue (in this case Epic) is created, or once Summary is changed on the already created issue. 👈

Potentially, something like ScriptRunner Behaviours could help out here, but this would require some additional testing.