I want to use the t-shirt size template to estimate story points in stories and tasks. I would like to have a field in the story/task so that the user sees the size of the shirt and when he selects it, assign a story point
You could add a single-select, custom field for your t-shirt sizes and use an automation rule, triggered on a change to the t-shirt size, to set your Story Points field based on the size.
Kind regards,
Bill
Yes and to add to this I wonder why Story Points itself doesn't work...
5 = S
10 = M
15 = L
20 = XL
25 = 2XL
....
my only point here is that story points really is a variation of T-shirt sizing. Yes it would mean re-training the team but it is one less custom field to deal with.
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.
hello @Bill Sheboy Thank you for the answer. but I have one point regarding the automation rule, triggered on a change to the t-shirt size, to set the sory points field based on the size. how we do it? I searched ALOT to be able to do it but I get zero usuful answer. so if you tried it before and you have experince in that I will be very greatful for your help.
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is the home page for information on creating Automation Rules (for Jira Cloud).
You would use a Trigger of Field value changed.
You would follow this with a series of if/else blocks to
- use an Issue Fields Condition to compare the value of the t-shirt field to one of the values you defined for that field
- use an Action to Edit Issue and set the Story points field to the corresponding number value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Followed this advice and works a treat, thanks so much!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
An alternative method that could work also is to use a Lookup Table. You can find details about that in the Actions documentation.
https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you working with a Company Managed project or a Team Managed project?
Creating a custom field for a Team Managed project is detailed here:
Creating a custom field for a Company Managed project is detailed here:
https://support.atlassian.com/jira-cloud-administration/docs/create-a-custom-field/
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.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.