story points not visible in create/edit issue after following GreenHopper 101 instructions

[David Rees]

I still don't see the Story Points field when creating/editing stories.

I followed the GreenHopper 101 instructions and set it to use the scrum template. According to GreenHopper 101 this shoulld cause the project to be "automatically configured to use Stories, Epics, Story Points, Ranking and Flagging."

I do see Story Points in the field configuration list under Administration. I guess I could play around there to add the field to the screens, but want to make sure I didn't somehow miss a step in setup.

[nletendre]

Your product is ridiculously hard to use.

[Félix Réginent]

I couldn't more agree... 

[Arbi Baghoomian]

Go to:

project settings > select Screen> on your screen, select configure link> Add new field as story point or what ever you want.

After that story point will be appear in story detail page.

[Alex Rosenthal]

but that's not the "right" story point field that would show up in backlog view, or in reporting etc. Also, this can cause a lot of confusion, because there will be 2 fields with the same name. Don't think there is a real solution to this.

[Shanton Anderson]

I fought through this for a couple of hours, but finally found it here.

[Kiril Nikolaev]

I've done this, but I am still not seeing Story Points in my stories. Been looking at all setting, configurations, etc. What needs to be turned on for this to work? All other fields show up when I add them in issue screen, except for Story Points. Any idea why?

[Deleted user]

Kiril, I have the same issue at the moment. It seems like there is a bug, all the other fields display for me except Story Points

[Kiril Nikolaev]

I figured it out yesterday here: https://community.atlassian.com/t5/Jira-questions/Why-is-there-no-story-points-field-option-during-issue-creation/qaq-p/313094#U1487204. Took a while to dig up, but this helped and I see Story Points now: 

Custom fields in JIRA (story points is a custom field) can be configured with a context that restricts it's usage to certain projects and/or issue types. To check this, please go to Administration >> Custom Fields. Look out for the Available Context(s) column.

[Deleted user]

What a guy, thanks Kiril!

[Daniel]

Kiril, THANK YOU.

[Jeffrey Bismayer]

Why is this like this? Why is every other essential field global and not this? Thank you for the solution, but this was ridiculous-- spent almost the entire work day trying to figure this out. 

[Jem]

thanks @Kiril Nikolaev , saved me the trouble there

It's like layer after layer of setting up

[David Rees]

I think maybe this is answered here - https://answers.atlassian.com/questions/8094/where-do-we-enter-story-points, but I am not 100% sure since that question doesn't talk about the GreenHopper 101 doc.

[David Rees]

As follow up, Story Points are visible in the Planning Board. Maybe that is all that is supposed to happen when I choose a Scrum config?

[Adway Lele]

Same experience with me too.