# Report for sprint history for an issue

**URL:** <https://community.eazybi.com/t/report-for-sprint-history-for-an-issue/5561>\
**Category:** Questions & Answers\
**Tags:** history, sprint\
**Created:** [November 4, 2020, 2:32pm UTC](https://community.eazybi.com/t/report-for-sprint-history-for-an-issue/5561 "2020-11-04T14:32:18Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ran.lavi](https://community.eazybi.com/user_avatar/community.eazybi.com/ran.lavi/32/85_2.png) [@ran.lavi](https://community.eazybi.com/u/ran.lavi)\
**Post date:** [November 10, 2020, 1:52am UTC](https://community.eazybi.com/t/report-for-sprint-history-for-an-issue/5561/2 "2020-11-10T01:52:12Z")

</div>

See here:

> [@Can we find out which issues were moved from one sprint to another?](https://community.eazybi.com/t/can-we-find-out-which-issues-were-moved-from-one-sprint-to-another/525/7):
>
> Here is one general solution that can be used as a basis for several scenarios analyzing previous sprints of an issue. The suggested solution includes importing previous sprints as a property for an issue. Then you can use this information in several scenarios. Here is a custom field definition with JavaScript code for custom field Previous sprints ID: [jira.customfield\_shistory] name = "Previous sprints ID" data\_type = "string" json\_fields = ["customfield\_NNNNN"] javascript\_code = ''' sprintH…

---

_[View the full topic](https://community.eazybi.com/t/report-for-sprint-history-for-an-issue/5561)._