Hello,
Does anyone know the best way to run sprints in Asana so that you have separate data for each sprint? I’m looking for the best methodology to do this feature in order to have separate data for each sprint (reports and so on). I don’t see a feature that allows me to start and finish a sprint in Asana. Can anyone help me? I will be very grateful. Thank you in advance 
Simplest way is to create a custom field with the sprint number.
A bit more convoluted, but you could achieve this by setting up a sprint project template.
You could then add the backlog and the per-sprint projects to a team portfolio, and setup the template so that new projects pulled from this are automatically added.
Benefit is that you are able to add start and end dates to each sprint/project, and complete them upon finishing them.
It does make it a bit more of a hassle multi-homing tasks from the backlog to the right sprint.
More guidance on using project templates here: Leveraging project templates - a deep dive
It might also be worth looking at determining wheter you’d want to use a milestone for a sprint goal or utilising the Goals feature. (Goals being available is tied to your plan tier)
I am curious though what data you’d want to seperate, and hoping you don’t have to calculate velocity… But that’s more about my vision about improvement, not on how to use Asana. But feel free to DM me if you want to dive into that. 
Thanks! It is us what I have done so far. I have created a custom field with “sprint nb”. So I can put a label to each task: Sprint 1 / Sprint 2 and so on:
But I am still wondering how to have a bigger insight into separate sprints, so that I can always go back to data connected with specific sprint number…
And actually I don’t know how to use this sprint template you mentioned inside the project created? I tried to put a template base on my project but… I don’t see any difference now.
I’m talking about using a project template so that new sprints aren’t inside your existing project, but every sprint is a separate project.
Thinking about it, you’d need portfolio functionality to get a better overview (that contains the sprint projects), and this requires a certain plan tier.
I think if you read the project template article I mentioned you’ll get a better understanding of what I mean.
Ah, ok. Understood. Thanks!
Piggybacking on @Jan-Rienk’s great suggestions, we’re experimenting (WIP) with having a portfolio represent a “project” (e.g., product) with individual projects representing sprints. There is one backlog project where all work originates and a rule that moves tasks to the correct sprint project based on a custom field (basically exactly what J-R mentions, with a small added automation). This allows you to leverage reporting on tasks in sprints and also the various native project objects (briefs, status updates, etc.).