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; } } }

How to create "issueFunction" custom field(JQL Functions Customfield Type) in jira??

Raju Anumula_f62rpc

Hi Team,

Unfortunately, I deleted the issueFunction custom field in Jira, after deleting when I search query(project = "abc" AND issueFunction in linkedIssuesOf("") AND status not in (Resolved)) in search issues I will get error "Field 'issueFunction' does not exist or you do not have permission to view it". same query working in the stage. I strongly believe this error because of issueFunction delete.

Is there any way to revert back?? or How to create issueFunction Custome field ??

Thanks in Advance.

Regards,

Raju Anumula.

Accepted answers

Alexey Matveev

You can try to disable and enable the ScriptRunner plugin and see if the field is created. But try it first on a staging environement.

Manon Soubies-Camy

Hi @Raju Anumula,

I agree with @Alexey Matveev, I once ran into this issue and disabling/re-enabling ScriptRunner did the trick.

What ScriptRunner version are you running though? IssueFunction should now be locked so you shouldn't be able to delete it: Lock the issueFunction custom field.

- Manon

All comments

Alexey Matveev

You can try to disable and enable the ScriptRunner plugin and see if the field is created. But try it first on a staging environement.

Raju Anumula_f62rpc

Hi Alexey,

In stage, there is no problem and issueFuncton custom field Available. In production, Unfortunately, the issueFuncton custom field is deleted so that's way I am getting an error?

Alexey Matveev

You should delete the field in the staging environement and try to return it back. Or you can make another stagin environement. Just you can not do such kind of things in production without testing.

Nic Brough -Adaptavist-

Yes, ScriptRunner hangs a good chunk of code off that field, so you do need it.

You should add a replacement field of that type, make it global, and re-index the whole system (background index will do, you don't need the locking one)

Manon Soubies-Camy

Hi @Raju Anumula,

I agree with @Alexey Matveev, I once ran into this issue and disabling/re-enabling ScriptRunner did the trick.

What ScriptRunner version are you running though? IssueFunction should now be locked so you shouldn't be able to delete it: Lock the issueFunction custom field.

- Manon

Raju Anumula_f62rpc

Thanks @Manon Soubies-Camy

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server