Hi,
How can I get a list using JQL with all projects sprints, start date and end date of each sprint?
Example:
| Sprint | Start Date | End Date |
| Sprint 1 | 31/07/2019 | 20/08/2019 |
| Sprint 2 | 21/08/2019 | 17/09/2019 |
| Sprint 3 | 18/09/2019 | 20/09/2019 |
Thanks.
Hi @Rubia Valiati
I will use an answer from @[deleted] :
"JQL is for finding issues, not reporting on them. You'll need a JQL query to get the list of issues you want to report on (So something like "Product in (DEF, GHI)") and then use that in a gadget or report.
The most simple and intuitive report is the issue navigator, where you get the results of a search by default. Run your JQL, save it as a filter, then (optionally) set the columns to include at least issue type and product. That will show you the raw data you want to aggregate.
Then go to your dashboard (or add a new one) and add a gadget. For the case you've got, I would suggest the "2 dimensional filter" gadget, as you can tell that to use your saved filter, and report on maybe an X axis of "issue type" and a Y axis of "product" to get a grid telling you the things in your question."
Hope it helps !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you have any luck @Rubia Valiati ? I was only able to create a grid using Issues data and not Sprint data like below:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
how were you able to generate this? was it in jira or custom?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@LaTisha Jenkins this was created from by using 2 things
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
While interesting....this doesn't address the root question.
The only way I've been able to get to this is using the Jira Add-in for Excel,
This belies a fundamental flaw in Jira's data model. ANY element that serves as a a way to GROUP something, should be a top-level item that should be QUERYABLE discreetly, just like Work Items.
The statement that "JQL is for finding issues, not reporting on them." is ridiculous on the face of it. Reporting things you're searching for is an implicit use case of ANY Data Store. Whomever thinks otherwise should go back and study database systems.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Rubia ValiatiJQL is for issues only, you can not get Sprint,project,version extra using this.
But you can view list of sprint in Sprint Report - https://confluence.atlassian.com/jirasoftwarecloud/sprint-report-777002722.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.