Age of Issue after moving it to new project

Bernard Horowitz February 20, 2024

Hi all,

I have a issue that was created a few months ago. It stayed in a project backlog until it was ready to be assigned to the proper team.  Now I am building some custom dashboards and the created date is showing the age to be my original created date. What I really need to see is the date it was transitioned to the new project. Like doing a count from the time it was assigned to a project to see how long it took for the task to be completed by the team in question.

Thoughts on JQL?

3 answers

1 accepted

0 votes
Answer accepted
Fabian Lim
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 20, 2024

Hi @Bernard Horowitz

Unfortunately JQL will not be able to calculate for you or any out of the box gadgets. You will need to look into 3rd party reporting plugins in the marketplace.  Instead of counting when it was moved to the new project, I would consider when it was transitioned to a specific status.  



0 votes
Amay Purohit_RVS
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 21, 2024

Hi @Bernard Horowitz 

Not sure if this can be achieved through JQL. You can use Jira Rest API's to get this data. Or as an alternate if you are fine to use a mktplace plugin you can try out


Time in Status Reports 

One of the many reports which the app provides is Time in Status in hours/days to determine , how much time the issue spent in each status in the complete lifecycle of the issue. The app has 20+ reports to track your bottleneck Issues & Processes.

Disclaimer : I work for the vendor who built this app


0 votes
Emre Toptancı _OBSS_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
February 20, 2024

Hello @Bernard Horowitz ,

Doesn't that contradict with "moving" the issue to a new project? I mean, if you are moving an existing issue, obviously you want to keep that issue so the original create date stays as it is. 

If you want a new create date, you can either create a new issue in the new project or (if you don't want to enter all the issue data from scratch) you can clone the existing one and move it to the new project.


Having said this, for your current case, Time in Status app built my team at OBSS might help.

Time in Status mainly allows you to see how much time each issue spent on each status, each assignee.

tisCloud_StatusDuration_LeadTime_with Estimates.png    tisCloud_AssigneeDuration.png

The app also has Any Field Duration report. This report shows how long each field help each value. The screenshot below shows this report based on an imaginary "Assigned Team" field but you can get the same report based on the "Project" field and see how long each issue stayed in each project. 


You can also use more than one field for this report. For example you can select both Project and Status fields for this report and see how long each issue spent in each status of each project.

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well. It supports both Company Managed and Team Managed projects for Jira Cloud.

Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.

Gadget_AverageStatusDurationByComponent.png  tisCloud_StatusDuration_LeadTime_Chart.png

Hope this helps.


Suggest an answer

Log in or Sign up to answer