- "Our developers don't want to estimate hours, they prefer to work in story points"
- "Our developers don't want to log work, and we don't want to force them to. We have a process allergy"
- "...but we still want to see roughly how much time is being spent on an issue"
- "Oh, and also, we want to enforce Story Points as a Fibonacci sequence"
We'll show you how to do all of this using Power Scripts™ for Jira - a powerful scripting tool to help automate your Jira.
What These Scripts Do
- Restrict the Story Points values to 1, 2, 3, 5, 8, 13 or <NULL> and returns error messaging and disables the submit button if an invalid value is present
- When Story Points field is populated with a valid value, checks the map to hours and sets the Original Estimate and Estimate fields to the associated number of hours. Provides confirmation messaging and enables the submit button.
- When an issue workflow transitions to a "resolved" status, the value in the Estimate field is "taken as credit" via worklog entry by the user who invoked the transition. Remaining estimate is then depleted.
Mapping Story Points to hours isn't technically "agile", but we see this request often enough to offer this solution.
- You have Jira Software installed
- You have Power Scripts™ for Jira installed
- You have mapped the Story Points custom field to its customfield ID in the "sil.aliases" file.
Configure Live Field Listener
You should configure this script as a Live Field script for the relevant project.
Listener References Live Field Executor
Configure "Resolved" Workflow Transition Post Function
In the relevant workflow, you should configure this script as a SIL™ Post Function when the issue is complete.