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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

History of Values in a Custom Field


I need to add a custom field that would store the history of values in another custom field.


Whenever a user transitions an issue to "Pending" they will update a custom field "Pending Reason" with the reason.
An issue can be transitioned to "Pending" multiple times, so I need to have a scripted field that would show all of the values that were ever entered in "Pending Reason" and the dates they were entered.


Is there any way I could accomplish this?

1 answer

0 votes
John Funk Community Leader Jan 12, 2021

Hi Krzysztof - I do not not of a way to do it other than creating multiple custom fields for each time it happens. Pending Reason, Pending Reason 2, etc. to the number 10 or whatever the max is that you think will happen. 

Same with a custom date field - Pending Date, Pending Date 2, etc. 

Or you can create a multiline text custom field and append to the values in that field every time it happens. 

I thought that since the changes are saved in history, there would be a way to pull them all out to a custom field.

As for the append approach, any ideas on how I could accomplish this?
I am guessing that using a groovy script would be an option, but I am not that familiar with scripting.

John Funk Community Leader Jan 12, 2021

You might be able to pull them out using the API somehow, but that is beyond me. 

For the append approach, create a multiline text custom field type. 

The create an Automation For Jira rule that when the status moves to Pending that the value of the Reason field and the current timestamp (Now) will but added to the field. 

So it is a rule with an Issue transitioned trigger

Condition for transitioned to Pending

New action - Edit issue

Select the new custom field

Then in the box for the update, use this code:

{{issue.custom field}} 

{{issue.pending reason}}   {{now.jiraDate}}


Use the actual names of the fields. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,142 views 8 28
Join discussion

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