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

Want to capture first and later reassignments to a group in a scripted field.


This field was created to count the no of time the ticket was assigned to a group AA Service Desk. first assignment on creation is not getting captured, later changes are getting captured. What changes will be required here?

Whenever it is first assigned to this group on creation through automation or being preset as a value. It is not captured as a count. It is showing 0. It should count that as 1 and later routing to that group also.

This is the script written for a number field template scripted field but what changes will be required here to achieve the objective.

import com.atlassian.jira.component.ComponentAccessor
def data = 0

for(def his : ComponentAccessor.getChangeHistoryManager().getChangeItemsForField(issue, "Group Assignee")){
if (his.toString == "[AA Service Desk]"){
data = data +1

return data


Kindly advise.



Muddassir Quazi

1 answer

1 accepted

1 vote
Answer accepted

You can make a logical assumption here - the creation of an issue is not recorded as a change, but the data is (would be) that all fields changed from "not there" to "their initial state".  Humans infer that logic instinctively and so Jira wasn't really built to store or provide that data directly.

You'll need to code to make the assumption, but it's not hard, you can make the assumption that "if no changes are found in the history, the current value of the field is what was set at the beginning".

However, your code is simply counting the number of changes.  Logically, you could just add 1 to "data" to count the change from "not there" to "initial value".

The question there is whether you want to count that differently depending on the initial value.  I suspect you've got two cases to count differently:

  • If the initial value was <anything> count "not there" to "<anything>" as a change
  • If the initial value was not set, do NOT count "not there" to "not set"

You'll need to amend your code so that it looks at the initial value set, either as it iterates through the changes (look at the initial value in the very first change found), or if no changes have happened since the creation, what the current value of the field is.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

Improving the Create Issue Experience in Jira Service Management Cloud

Hello everyone!  We are very excited to announce some much needed changes to the issue create experience in JSM (the blue "create" button) at the top of the screen.  We have just starte...

224 views 8 7
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