Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Export the projects timelines

ilker isler
Contributor
January 19, 2020

Hi all;

I need the timeline of the projects which means, the data of start and end date the projects and who works on that project as asignee. Is it possible to reach that data from past to today? And how could i export the data on the timeline.

1 answer

0 votes
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 21, 2020

Hello @ilker isler ,

Jira does not have a concept for start and end of a project, but rather allows for setting goals within the projects issues, or releases.  The project itself starts when created and ends when you remove access to the project so that no users can create or edit issues within that project.

You can however pull all data of the issues within the project, including the desired field data, as an exe your looking for assignees of issue within a specific project, and also looking for lifespan values of the issues for your export, so set your columns in the issue navigator to include the Assignee field, the created field, and the resolved field, and run the following JQL to get all issues sorted by creation date:

project = exe ORDER BY created

This will in effect give you a list of issues that can be exported to show the assignee, and the start and completion dates of all the issues within the project that can be used in external reporting tools like open office or Excel.

There is however a hangup here as Jira will only return the current value of a field and does not have the ability to return historical values, so if the assignee has ever been updated it will only display the current assignee and no indication of the user that was previously in that field.

You can use historical search search modifiers like "assignee was speciffic_user_name" for this, on a user by user basis but this as well has the drawback of requiring a filter per user, and a manual review process to collect the user.

Another approach for historical items is that you could look into the REST API to expand the changelog of the issues returned by various filtered result sets which would require some custom scripting to isolate the events you are looking for in the output, but the following post gives an example of how to do this, and also offers up some alternatives in the form of app-ons as a workaround:

Another point to consider and an API exe that might be leveraged to your use case if your users are utilizing the worklog feature on issues to indicate working on issues rather than just basing the value on the assignee is there is a a really good exe on how to pull worklogs on a per user basis from a project from the API with an example scripts linked via github repos in the following community post:

Regards,
Earl

Suggest an answer

Log in or Sign up to answer