Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to assign points to bugs - stories default to Original Estimation despite configured settings

Ruslan Ardashev
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 19, 2020

Hi Support,

 

I have configured board, project, and screen settings, as well as fields for new stories. Stories are not defaulting correctly to Story Points when creating stories in my current Sprint, instead showing Original Estimation (but I'm using a workaround and adding new stories directly to the backlog and then pulling them into this Sprint and that is working).

Original Estimation default to time, even though Estimation is configured through settings to not use this.

 

With this workaround in the new interface, the fields are changing back to use Original Estimation instead of Story Points when I pull a story from the Backlog into the Sprint and change its classification to a Bug.

 

We have the board, project, and screens, and fields seemingly properly configured. I have double checked screen field settings for bugs as well and they seem fine.

 

Please advise.

 

Best,

Ruslan

1 answer

1 vote
Ste Wright
Community Champion
August 19, 2020

Hi @Ruslan Ardashev 

Just to confirm are the issues showing hours in the estimation field...

  • On the Backlog or...
  • On the Active Sprint Board or...
  • Both!

If it's just on the Active Sprint Board - it would depend if you have Time Tracking activated on the board.

If via Board Settings > Estimation you have Time Tracking set to "Remaining Estimate and Time Spent" - then on the Active Sprint Board the estimation field will show "Remaining Estimate" as hours, and only show "Story Points" on the Backlog.

If you turned that off, "Story Points" would be on both.

Ste

Ruslan Ardashev
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 19, 2020

Hi @Ste Wright ,

 

Wow! Thanks for the quick response!

 

"

  • On the Backlog or...
  • On the Active Sprint Board or...
  • Both!

"

haha!

 

I have navigated to the board settings using the "..." button at the top right on the board --> board settings and here are my settings for estimation. I am still seeing Time Estimation for my active sprint and story points for the Backlog.

 

Screen Shot 2020-08-19 at 11.57.41 AM.png

Ste Wright
Community Champion
August 19, 2020

Hi @Ruslan Ardashev 

Strange! That isn't something I've seen before.

Next I would check:

  • Card Layout: Is the "Original Estimate" field set to appear on the Sprint Board?
  • Field Context: Ensure Bugs are set as included via the Story Points' field context.
  • Field Configuration: Ensure there isn't a custom Field Configuration for Bugs, with Story Points hidden

You'll need to be a Jira Admin to check Field Context and Field Configuration.

-----------------

To get to Field Context:

  1. Go to Jira Settings > Issues
  2. Select Custom Fields from the left-hand menu
  3. Locate "Story Points" and press the 3-dots icon on the far-right of the field's row
  4. Select "Contexts and Default Value"
  5. Select "Edit Configuration"
  6. Under "Choose Applicable Issue Types" make sure Bugs is selected (if "Any Issue Type" is not)
  7. If not - select it (Ctrl+Click / Cmd+Click) and press "Modify"

-----------------

To get to Field Configuration:

  1. Go to Jira Settings > Issues
  2. Select Field Configuration Schemes from the left-hand menu
  3. Check if your project has a custom scheme - if it's not on this screen, check in Field Configurations (left-hand menu) to see if it's using the Default.
  4. Enter the Scheme if it's custom and check if there is a Field Configuration Bugs is listed against.
  5. If there is, go into the Field Configuration and check "Story Points" hasn't got a hyperlink "Show" next to it, which would mean it is hidden.

-----------------

I'm not sure on the exact answer here - but these are the things I'd check next to locate what it might be!

Ste

Like Ruslan Ardashev likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events