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

Looking a Query - Records with all history like status, severity etc before its 1st update date

I want to get the records , what was its status, severity etc when it created after its several update.

what is happening now - when we are creating tickets after triage or 1st resposne people are changing its status, severity, high  / low etc and others details, after somedays want to know when it create it came to us with what all details. 

2 answers

1 vote
yuliia_b__SaaSJet_ Marketplace Partner Dec 12, 2022

Hi @anil kumar rao 

You can find those details for a single ticket in the History under the Activity section.

If you want to get all records for the list of tickets, you can try Issue History for Jira add-on. My team has developed it to track all past activities in one place. You can add any issue field (status, serenity, etc.) to the report and see all changes made to it.

The green point shows when the ticket was created.issue created in jira.png

I hope this solution can help. You can check it with the 30-day free trial.

0 votes

I think it is easier to capture the initial state and store that somewhere than trying to time-travel back by reverting the issue's change history.

Maybe you could just email the issue or export it somewhere using the built-in notifiations or the Automation for Jira App right after its creation. Then use that information as your reference.

Suggest an answer

Log in or Sign up to answer