I am planning doing this very same thing for our instance @Kathleen Shafer. I am planning on using T-Shirt sizes as well! My thoughts are like this:
- I want to use the default Story Points field at the end of the day
I do not want any strangeness with JIRA Agile - The estimation should be a single-select list with Small (1), Medium(2), Large(4), Extra Large(8)
- I think here that it would be best to keep it simple. I don't want to code a whole bunch of logic, I just want to streamline the Story create process.
Edits and additions
Hello again @Kathleen Shafer! I have the post-function script working fine, and I think this is good enough for use. I am looking into the Scripted Field option still as well, this just isn't taking a priority. I hope you understand.
System Requirements
This post-function is only available to users of the Script Runner add-on, only available on JIRA Server. The Script Runner add-on lets us run Groovy scripts, for instance, as a post-function. We will leverage this to fulfil the software requirements.
Software Requirements
As a user, I should be able to set Story Points on issue creation using a select-list with T-Shirt estimation-sizing.
Set Up
- Get the Custom Field IDs of both the Story Points and T-Shirt Size custom fields
- Modify the below Groovy code with the Custom Field IDs that you just obtained
- Set field T-Shirt Size on your Create Screen
- Set field Story Points on your Edit and View Screens
- Add the Groovy code as an inline script, to be attached as a post-function of the Create transition
Use
- Open the Create Issue dialog
- Choose an option from T-Shirt Size
- Press Create
- Note the cooresponding value in the Story Points field
// Written by Steve Behnke, BlackPearl PDM
//
// The goal of this post-function is to simplify input of Story Points. Story Points normally, being a number field, allows people to enter any value
// However, without training or experience, these values vary wildly and may not be useful for reporting purposes until some time passes
//
// Using a 't-shirt size' select-list to populate the existing story points field let's us accomplish this in a flexible manner that really doesn't change the actual behavior of the story points field at all. We're just pre-populating it.
//
// This is as opposed to a scripted field of sorts, which could 'map' the values directly with no room for flexibility.
import com.atlassian.jira.ComponentManager;
import com.atlassian.jira.issue.CustomFieldManager;
import com.atlassian.jira.issue.fields.CustomField;
import com.atlassian.jira.issue.IssueManager;
import com.atlassian.jira.issue.Issue;
import com.atlassian.jira.issue.util.DefaultIssueChangeHolder
import com.atlassian.jira.issue.util.IssueChangeHolder
import com.atlassian.jira.issue.ModifiedValue
// set up logging
log.setLevel(org.apache.log4j.Level.INFO)
log.info "Executing T-Shirt size > Story Points conversion!"
// gets a reference to the IssueManager and CustomFieldManager manager classes
IssueManager issueManager = ComponentManager.getInstance().getIssueManager();
CustomFieldManager customFieldManager = ComponentManager.getInstance().getCustomFieldManager();
// gets a reference to the custom field objects
// note, that since I reference the fields by internal ID these will need to be modified to work correctly
CustomField tshirtsizeField = customFieldManager.getCustomFieldObject( "customfield_12214" );
CustomField storypointsField = customFieldManager.getCustomFieldObject( "customfield_10004" );
log.debug "get tshirt value"
Object tshirtValue = issue.getCustomFieldValue(tshirtsizeField);
// introduce the changeHolder element, in order to update fields
IssueChangeHolder changeHolder = new DefaultIssueChangeHolder();
// create values as doubles, appropriate for "JIRA Number Fields;" Story Points is this type of field
//
// T-Shirt size = Small
Double pSmall = 1
//
// T-Shirt size = Medium
Double pMedium = 4
//
// T-Shirt size = Large
Double pLarge = 9
//
// T-Shirt size = X-Large
Double pXLarge = 16
// retrieves the custom field value object from the issue and sets the story point value
if(tshirtValue.toString() == "Small") {
storypointsField.updateValue(null, issue, new ModifiedValue(issue.getCustomFieldValue(storypointsField), pSmall), changeHolder);
log.debug "size = Small, value =" + pSmall.toString()
}
else if(tshirtValue.toString() == "Medium") {
storypointsField.updateValue(null, issue, new ModifiedValue(issue.getCustomFieldValue(storypointsField), pMedium), changeHolder);
log.debug "size = Medium, value =" + pMedium.toString()
}
else if(tshirtValue.toString() == "Large") {
storypointsField.updateValue(null, issue, new ModifiedValue(issue.getCustomFieldValue(storypointsField), pLarge), changeHolder);
log.debug "size = Large, value =" + pLarge.toString()
}
else if(tshirtValue.toString() == "X-Large") {
storypointsField.updateValue(null, issue, new ModifiedValue(issue.getCustomFieldValue(storypointsField), pXLarge), changeHolder);
log.debug "size = X-Large, value =" + pXLarge.toString()
}
else {
// do nothing
log.debug "Size was set to null; not setting story points."
};
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.