Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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
Community showcase
Published in Apps & Integrations

Send an Email or Publish to Confluence - What should you do with your release notes?

Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...

92 views 0 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you