Declared custom fields were unidentified by Java Script after a month

[Inayatulla Shaik]

Hi Atlassian,

I am working on one of the projects in JIRA Cloud.  As a part of this project, I have created custom fields and declared these custom fields (like customfield_10181) in behaviour. Custom fields were successfully identified by behaviours but after some days some of the custom fields which were identified were shown as unidentifiable. I have attached screen shots, please take a look. if you can see the see below attached screen shots, the custom fields named customfield_10421, customfield10181 and customfield_10442. These custom fields were identified as how customfield_10614 and customfield_10444 were identified. But now they are unidentifiable (with red underlined). If this behaviour is continues our projects become unstable. So, please take a look and let us know why JIRA Cloud behaves oddly.  

[Kristian Walker _Adaptavist_]

Hi Inuyata,

Please note that Behaviours inside of Jira cloud do not support all custom field types and only support fields that Atlassian supports in the UI modifications API, which it uses. 

You can refer to the documentation page here for a list of supported custom fields. 

I hope this answer helps,

Regards,

Kristian

[Trudy Claspill]

Hello @Inayatulla Shaik 

What is the scope of your Behaviour?

Behaviour is a feature of the Scriptrunner app from Adaptavist, not native Atlassian Jira functionality. Have you contacted support for Scriptrunner?

[Inayatulla Shaik]

Yes, you are right Behaviour is a feature. Basically java script is being used as behaviour (or script). Yes, I have opened a support ticket for Scriptrunner.

[Kristian Walker _Adaptavist_]

Hi @Inayatulla Shaik

We have checked from the ScriptRunner side and noticed an issue with the type definitions not correctly recognising some fields in the Behaviours code editor, and have just released a change to fix the issue. 

Can you please refresh the page and see if they show as expected? If not, please notify the support team so we can look into the cause of the issue further for yourself. 

Regards,

Kristian