Some of my users like to transition their issues directly from a dashboard. The transition screens have scriptrunner behaviours that hide the comment field from them as part of the initializer. What I've noticed is that the first time a particular transition screen is displayed - regardless of issue, the other parts of the initializer are run successfully, but hiding the Comment field does not work. Without reloading the page, subsequent calls to the transition screen - again, regardless of issue - produce the desired behaviour. Reloading the page seems to reset the screens and the comment field is not hidden.
Transitioning from dashboard actions:
First time after reloading:
Subsequent calls:
Comment field is hidden correctly.
Hi Brian, could you share the script you used to hide the Comment field? I set it in my Behaviours as a server-side script for the Comment field and mine was hidden successfully even when transitioning issues from the Dashboard.
Hi Tye,
I'm using this in my behaviour initializer:
import com.atlassian.jira.component.ComponentAccessor;
def triggerActions = ["Add RCPE Notes"]
log.info("MCR - RCPE Notes Behaviour will${triggerActions.contains(getActionName()) ? " " : " not "}execute for ${getActionName()}")
if( ! triggerActions.contains(getActionName())) return;
def comments = getFieldByName("Comments");
comments.setHidden(true);
Again, it works on the second access of the transition, but not on the first. So it seems like it's not loading the behaviour in time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.