T-Shirt Sizing in Jira for Agile Estimation (2024)

1.Create a custom field for T-Shirt Sizes

Begin by creating a Select List (single choice) customfield for the T-Shirt sizes. If you need assistance creating a custom field and associating it with your projects screens, check out the Atlassian documentation:Adding a Custom Field andConfiguring a Custom Field.

Your custom field should look something like this

2. Create The Execution Plan

We need to create an execution plan to trigger our desired field translation. Begin by setting the Issue Event triggers - in this example, we want to trigger the translation immediately when the issue is created and any time the issue is updated thereafter. Next, selectAdd Action, setAction Type toMap Field Values.Map your Feature Size values to story point values (in the example, we're using Fibonacci numbers starting from 2).

Finally, we need to store the result of the mapping to the Story Points field. Click the Options(...) button and select Store Value in Field. SelectStory Pointswith the dropdown selector, and then selectDone.

The execution plan

3. Get to work!

As your team begins filling your backlog with issues, Abacus watches for issue creation and springs into action, dutifully setting the Story Points field according to the mapping we set up in the previous step. If your team decides to change the Feature Size of an issue at a later date, no sweat - we've told Abacus to watch for updates too!

Estimation on your termsAbacus doing the heavy lifting

4. Sweet rewards

Because your Story Points field is automatically populated by Abacus, your team can benefit from all of the native Story Point integrations Jira offers. Use them to set Estimation Statistics on Boards, or in the creation of Reports and/or Dashboards.

A Sprint Report