How (or which parameter to use) to capture the start date and end date of the current week the way we can capture them while using the parameter "sprint" in our JQL as mentioned below.
It could automatically capture the start date and end date because we mention these dates while we start our sprint. But in Kanban board, we don't have any sprint to start. Hence, we don't create any time box where we mention the start date or the end date.
Hi @shantanu behera,
"Basically, I want to get the report from a filter which will help me understand how many of the issues (tickets) were in "In progress" or any later status in the workflow on a week on week basis."
Looking at your requirement, an option would be to try using the Cumulative Flow Diagram report of Jira.
If this report is not good enough for you (unfortunately it is not so configurable), then I recommend searching for an app on Atlassian Marketplace that provides such report or gadget.
If you consider the idea of using a plugin, our Great Gadgets app offers a powerful Cumulative Flow Diagram Chart gadget that can display this info for you with just a few clicks.
Danut.
Hello @shantanu behera
Welcome to the Atlassian community.
How (or which parameter to use) to capture the start date and end date of the current week
If you are recording dates in your Jira issues you can use JQL such as this:
yourDateField => startOfWeek() and yourDateField =< endOfWeek()
Refer to
https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#endOfWeek--
https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#startOfWeek--
If that doesn't address your question, please provide more information about what problem you are trying to solve.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Trudy Claspill for the response.
Basically, I want to get the report from a filter which will help me understand how many of the issues (tickets) were in "In progress" or any later status in the workflow on a week on week basis.
My problem is, when I have to use any date related parameter available (like statuschangeddate, updateddate etc), we can't exactly say if the status of the issue (ticket) was changed/updated on Monday or before that.
Hence, the report I am trying to pull is not going to give me right data of the issues which was considered in the week.
I hope I was able to share more details which will be helpful to assist me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you want to get the information for just the current week you can use a filter like this:
status WAS IN (comma separated list of your statuses) AFTER startOfWeek() BEFORE endOfWeek()
https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#WAS-IN
That will tell you all the issues in one of the specified statuses during the week. It does not reflect whether or not the issue was moved into that status during or before the week, nor does it reflect if the issue moved out of that status during the week.
This does not inherently give you the ability to report on previous weeks, but you could use the same query and replace startOfWeek() and endOfWeek() with actual dates for the weeks you want to review.
If you need to review based on the status having changed into one of the specified statuses during the week then you would use the CHANGED operator.
https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#CHANGED
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Awesome, yes looks somewhat promising for me to fetch the details. Let me try this tomorrow morning IST and see if it works. Thanks once again Trudy Claspill.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, the approach helps. It just how we need to tweak with the status we are using in our workflow. However, I was finding some anomalies. Will try to resolve and highlight if facing any issues.
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.