Only able to add a fix version to bugs

[Saul Melendez]

I want to tag any item (bug, story, task etc) to a fix version. But I'm only able to do do it for bugs. I see the field but its inactive. Is there a setting I should enable?

[Saul Melendez]

Thanks every one. I'm able to add fix versions now. I had to add the 'Fix Version/s' field in the Default Issue Screen

[Randy]

can you post screenshots of your issue type screen scheme for Stories and of the edit screen that shows the field being greyed out?

[Randy]

If you click "Edit" when viewing the issue and edit the issue can you add a fixversion? 

I would try that first. 

Agree with Nic that something might be breaking the javascript on the page.

[Saul Melendez]

Thanks. But that was the first thing I tried but it did not work.

[Nic Brough -Adaptavist-]

My best guess is that "inactive" really means "on the view screen, I can not enter a value".  This happens when the field is not on the "edit" screen so it cannot be edited.  Check what you get when clicking "edit" to pull up all the editable fields.

[Saul Melendez]

Thanks. I checked in Edit screen but no luck. It's only allowing me to do it for bugs. But when I try a story it does not allow me to add a fix version. 

[Nic Brough -Adaptavist-]

What does "not allow me to add" mean?  No field?  Greyed field?  You change it, but nothing takes?

[Saul Melendez]

I see the field but when I click on it it does not activate to give me the option to select a version. It's not greyed out just doesn't do anything. When I hover-over the same field within a bug I immediately get the pencil icon and the cursor changes indicating that I can click in that area

[Nic Brough -Adaptavist-]

That suggests you have something breaking the way the field works, a javascript hack or a broken behaviour.

[Saul Melendez]

That really sure what you mean by "Javascript hack" or "broken behavior". I use the online version of JIRA I imagine if I'm having issues everybody else would. I use another instance of JIRA for a different client and I'm able to add fix version on that account.  So it seems to be directly tied to the account I'm using. 

[Nic Brough -Adaptavist-]

By "online", do you mean Atlassian Cloud, or just a server version someone runs in the Cloud?

If you have other similar systems that are behaving, then yes, it's something to do with your account, but the only way to get the field behaviour you describe is to inject javascript that breaks the field in your browser.

[Saul Melendez]

Ok. Not really sure I understand. Pretty sure it's not a browser issue since it follows me from computer to computer (office and home). I'll keep poking around or google something...

Also, it happens with all project members. None of us are able to add fix version to anything else besides bugs.

[Nic Brough -Adaptavist-]

Are the bugs in the same project?

Some of this behaviour could be being caused by you not having "resolve issue" permission, but that's a project level thing, so it would affect bugs in the same project.