Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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,560,637
Community Members
 
Community Events
185
Community Groups

Behaviour not hiding field on first trigger on Dashboard

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: image.png

First time after reloading:

image.png

Subsequent calls:

image.png

Comment field is hidden correctly.

1 answer

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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events