
Introduction If you're using Jira Software's classic project setup, you're likely enjoying the features like managing your backlog, creating sprints, estimating issues, and ranking tasks. But what happens when you want to use a custom issue type and estimate it with story points?
This exact question was raised in the community recently: "How do I get story points to show in the backlog on a custom issue type?" If you've added a new issue type—for example, Test2 or Improvement—and the story points field is missing in your backlog view, don't worry. Here's a step-by-step guide to resolving this issue.
Step 1: Understand the Problem The issue arises when Jira doesn't automatically associate the Story Points field with a new custom issue type. By default, story points work with standard issue types like Story or Task, but custom issue types require manual configuration.
For example, if you add an issue type called Improvement, you might notice:
- Other issue types show story points in the backlog.
- The new Improvement issue type does not have the story points field.
Step 2: Go to the Custom Fields Section To fix this issue, you need to ensure the Story Points field is configured to work with your custom issue type. Follow these steps:
- Navigate to Custom Fields in Jira:
- Go to Jira Settings (gear icon) > Issues > Custom Fields.
- Search for the Story Points field.
- Type "Story Points" in the search bar to locate the correct field.
- Adjust the Context for the Story Points field:
- Select the field and look for the Context configuration. The context determines which issue types the field will appear for.
Step 3: Update the Context for Your Custom Issue Type
- Access the field's configuration context.
- You'll see one or more configuration schemes listed, such as "Scrum" or "Global Default".
Modify the issue types:
- Click on the Edit (cog icon) next to the configuration.
- In the issue types selection list, add your new custom issue type (e.g., Improvement).
Pro Tip: When selecting issue types, hold down the Ctrl (or Command on Mac) key to ensure you don't accidentally deselect existing types.
- Save your changes.
Step 4: Refresh and Verify Once the context is updated:
- Go back to your project board or backlog.
- Refresh the page.
- Check your custom issue type (e.g., Improvement) to see if the Story Points field is now visible.
Now, you should be able to:
- Add story points to your custom issue type.
- See the estimated story points reflected in the backlog.
For example, if you estimate the Improvement issue type at 3 story points, you will see the total estimation update accordingly in the backlog or epic.
Common Pitfall: Selecting the Wrong Issue Type If it doesn't work on your first attempt, double-check that you selected the correct issue type during configuration. For instance, you might have accidentally selected New Feature instead of Improvement. Mistakes can happen—just repeat the steps and ensure you're editing the correct type.
Conclusion Adding story points to custom issue types in Jira classic projects is straightforward once you understand the context configuration process. By modifying the custom field settings, you can enable estimation for any custom issue type you create.
This simple fix allows you to:
- Use story points with your custom issue types.
- Manage and estimate your backlog efficiently.
- Ensure your project reflects accurate estimates for all tasks.
If you found this guide helpful, let us know! Start exploring the possibilities with custom issue types in your Jira projects today.
Video Link : https://www.ravisagar.in/videos/jira-cloud-add-story-points-estimation-field-custom-issue-type