Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

T-shirt sizing and velocity


Can you please assist with the below questions?

1. Is there a field in Jira in which I can add/input T-shirt sizing estimation?
2. If yes, does Jira calculate velocity based on these estimates?

Thank you.

1 answer

1 accepted

7 votes
Answer accepted

Hello @diana.georgieva,

1. Jira has the possibility to create Custom fields with a wide variety of options (radiobuttons, checkbuttons, lists etc). Through this functionality one can absolutely set up a field for t-shirt estimation. 

2. No, the custom field has no built in functionality like velocity-reporting. 

My opinion and suggested solution: I would use the built in story point system (that has velocity reports etc built in from the start). The ideal use of story point is to limit the possible values according to Fibonacci sequence (1, 2, 3, 5, 8, 13) to make it easier to manage. This system is the exact same as t-shirt sizing, but with numbers. If your team find it easier to talk about t-shirt sizes, then talk about tshirts during estimation and estimate in that way, but relate each t-shirt size with a story point number in Jira.

Hope this helps!

The t-shirt to story point mapping then could look something like:

Story point: 1    2    3    5    8     13

T-shirt size: XS  S   M    L    XL    XXL

Like # people like this

Hi Gustav,

That was my understanding as well. 
Thank you fir confirming!

Like # people like this

I agree with Gustav's suggestion, and would emphasize that going with a custom field works against the grain in JIRA. It's extra work and fewer features to go with a custom field.

I'd also argue that XS-XXL gives too many options. I'd narrow that down to S, M, L, and XL, where XL really means it needs to be broken down. Fewer buckets leads to less bickering.

Like # people like this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

178 views 2 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you