For a single issue, look at the history.
For many issues, you'll need to write code that can pull the data out of an issue history. I suggested fields initially because they would come out on the issue navigator and hence be exposed to excel downloads, and you'd be able to search/sort on them. If you're now wanting to write a report, that's different, you have the option of reading the history for each issue in your report, so you wouldn't need fields.
The fields I suggested are fields you would have to write - there are no real "fields" in the history - it's a long list of changes that have been made, not a list of fields.
That's what I'd use, but you can do it with your own add-ons too (before Script Runner, I wrote a couple of fields that extracted the history and put them into the navigator, and I had a timeline of changes report for issues as well),
There could be other add-ons out there that might help too, but I'm rusty on them because I use SR so much now.
Hi @Viktar Bachkouski
Please see the below link where I have written a complete solution to View and Download Status History.
I have submitted it to Atlassian , if approved you can download the source code for free.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Atlas Camp is our developer event which will take place in Barcelona, Spain from the 6th -7th of September . This is a great opportunity to meet other developers and get n...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs