We want to identify the stories that have been re-estimated from original estimation and evaluate the trend.
We agreed to a process to re-estimate the task if the initial estimation is not the actual effort spent on the task (being it lower or higher).
How I can report those tasks (including the initial estimation)? We are using story points.
Thanks!
Hi @Teodora Craciunescu ,
To identify the stories that have been re-estimated in Jira Server and evaluate the trend, you can follow these steps:
1. Create a JQL (Jira Query Language) filter to find the relevant stories:
- Go to the Issue Navigator in Jira.
- Click on "Advanced" to open the JQL search.
- Use a query like the following to filter the stories:
issuetype = Story AND "Story Points" changed
This query will retrieve all the stories where the "Story Points" field has been changed at least once.
2. Save the JQL filter:
- Click on "Save as" to save the filter with a meaningful name, such as "Re-estimated Stories".
3. Create a new Jira dashboard:
- Go to the Jira dashboard page and click on "Create dashboard".
- Add a new gadget to the dashboard by clicking on the "+" icon.
- Select the "Filter Results" gadget.
4. Configure the gadget:
- In the gadget configuration, choose the "Re-estimated Stories" filter you saved in step 2.
- Customize the gadget settings, such as the number of results to display and the columns to show.
5. Save the dashboard and view the results:
- Click on "Save" to save the dashboard with the gadget.
- The dashboard will now display a list of stories that have been re-estimated, including the initial estimation and the current estimation.
By following these steps, you can create a Jira dashboard that shows the stories that have been re-estimated, allowing you to evaluate the trend and track changes in story points over time.
I hope this helps!
/Markus
Hi @Markus Fredén, thank you very much for your prompt and complex reply.
I am getting this error when creating the JQL.. is there a workaround..? Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Teodora Craciunescu ,
My apologies, I was under a false assumption that the "Changed" operator could be used on Story Points. So I don't think you can achieve this in a way according to best practices without making a non-viable solution such as a scripted field which would in theory need to run scripts to find out if the story points have been changed EVERY time someone filters on or views a ticket with this scripted field.
Unfortunately, I'm not aware of any other viable solution. That doesn't mean there isn't one but I dont know about it.
/Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Alright. I understand. thanks for trying.
I was thinking to ask the team just to either comment or label the stories they are re-estimating. Like this I can JQL based on the label. However, I am not sure if I can see the changes in other way than manually on each task.
All the best,
Teodora
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.