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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Keeping ScriptRunner postfunction from updating history/Dashboard feed


In our Jira workflow, especially on creation of one of our types, there are several group "Review Inputs" fields that depending on the required groups selected in another field, we either put <not yet submitted> or an empty string so the field will be "hidden" until a user selects to provide input for that group (at which point the "GroupA Review Input" field is displayed, for example).

The problem (and I use that term loosely) is that all the changes we do in our postfunction scripts show up in the issue history and in the system dashboard activity stream.  And since we have several fields that we do stuff to, the history and stream can get very verbose.

Is there a way to do all these updates without having them displayed in the history/stream?  Jira records all changes and that's good, but can you be selective so that postfunction updates aren't displayed as a change?



0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events