Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,364,932
Community Members
 
Community Events
168
Community Groups

Hide and set Summary in the portal for customers

Hi,

I'm not sure what's wrong here. I've added a behaviour which hides summary and sets the request type name of the chosen request type:

getFieldById('summary').setHidden(true)
getFieldById('summary').setFormValue(requestTypeName)

 The thing is that this works for agents with a jira license, but not for customers without a jira license.

 

Regards

Brian

2 answers

Hi Brian,

Not sure which Scriptrunner version you're using but it could be related to this bug here: https://productsupport.adaptavist.com/browse/SRJIRA-4876

It was fixed in Scriptrunner version 6.15.0.

Hi Brian,

Setting the Summary can be performed by JSM native functionality and copying field values can be performed by a post function. This raises the question of why you are using a Behaviour.

To use native functionality:

  1. Set the field as hidden in the request and provide any value.
  2. Create a post function on the create transition to copy the Request type to the Summary. This may have to be after the 'creates issue' or 'save to database' post functions.
    • Note: This devalues the Summary as it introduces duplicate information to the issue and deviates from best practice.

Cheers!

Hi,

Thank you for the reply.

I'm using Email This Issue for incoming mail, and this will not accept summary as a hidden field in any of the request types, which it uses to create tickets in. So I have to hide this without using native methods, it would seem.

Welcome Brian,

It seems to me that you are going against Atlassian's intentions for the Summary field. Please consider why it is the only field that is always required and how that is playing into your problem. The best solution is likely not technical, but changing a real world process or behavior.

You can investigate the portal section of your script (referenced in https://scriptrunner.adaptavist.com/5.5.9/jira/CustomisingUI.html) if you would like to continue with the technical solution. Cheers!

Thank again.

 

I agree, but the owner of the process insists, and will not have in other ways.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events