Javascript and Behaviours scripts in Jira Service Desk Forms

Vidic Florjan

I noticed that Jira Service Desk has a new GUI and that is not possible to use javascript code added in field description. It is also not possible to use Behaviours plugin scripts in the new forms.

I would like to find out if our jira has problems or this is normal behaviour of the new forms.

If javascript in description of the field is not supported anymore:

- Are there any plans to add this functionality?

- Is possible to use some workarounds (or different approach)?

Jira version: 5.2.2
Behaviours: 0.5.3

Javascript example:

<script>
function getCurrentUserName_sr()
{
var user;
AJS.$.ajax({
url: "/rest/gadget/1.0/currentUser",
type: 'get',
dataType: 'json',
async: false,
success: function(data) {
user = data.username;
} 
});
return user;
}
var user = getCurrentUserName_sr();
AJS.$("#customfield_13421").val(user);
</script>

0.5.3

ɹǝʞɐq pɐɹq

We dont have immediate concrete plans to add "custom custom" fields in the Service Desk customer view.

At present we have a "peer" field implementation for every JIRA custom field we know about. We did this to provide a fast and light weight end user experience. Our aim was that the customer view should load fast and suporrt key concepts like "field renaming" and modern "UI representation".

If we re-used the custom custom field implementations as is, we would have rebuilt JIRA view issue and its heavy weight design aspects. This is a key differentiator between create issue in JIRA and create issue in Service Desk.

There is another security aspect as well. Currently a project admin is able to create Service Desk "customer view" fields. By allowing custom JavaScript via this mechanism, we would be lowering the security of "custom javascript" from sysadmin (plugin install) to project admin. We do not want this to happen.

It is something we have thought about however and its a non trivial problem.

Some time in the future we have though of having a "plugin point" where "custom field" implementations could inject Service Desk specific JS/CSS as an alternate rendering on the customer view. But this is not on a concrete internal roadmap at this time.

Thanks for asking and providing extra feedback.

Cheers

Brad Baker

JIRA Service Desk Architect