Using pretty much default everything, all I did was added a custom field. Then configured it's context it to only be applicable for the Bug issue type, globally. Here's what I see (or don't see):
So I adjust the screens for this field and include the Default screen that's being used. Great, it now is available for the Bug issues only when creating/editing/viewing. It seems to work perfectly EXCEPT
Is this a bug?
I could maybe live with seeing "None" at the bottom (since that's where I order it to be) of other issues like a Story, just once. I'd know that it's the field for a Bug so it's not applicable, no worries. Ignore it. However, when I have a few custom fields, it just keeps saying "None" "None" "None" over and over.
How do I hide this if context doesn't work?
Hi Tom,
If you added the context correctly, it should only appear in the issues that you configured. Maybe you could share some screencaps? Are you on cloud or server?
I am on cloud. Here's some screenshots for the custom field configuration:
This one here has no screen associated with it. So the custom field is not seen anywhere. Not in "Issue Layout" for a board, not in the edit/view areas of course, and so on.
The next here is assigning it to the Default Screen, which will allow it to appear.
Though it appears on any issue, without a field title. It just shows "None"
Of course for the Bug issue type, it works as expected:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry Tom,
Are you sure that None belongs to that customfield? It might be a cloud bug, there have been trouble with some customfields in some screens. That view that you are showing me is not the normal screen.
The screen you are showing is the screen configuration of the board, you can reach in in the board administration "View Issue Pannel" maybe in this view it shows up wrong since it is only in some issues.
Sadly this view is shared for all screen so you canno take the customfield out, I might report this as a bug to oatlassian.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the reply. I did confirm it was for that field by toggling it on and off as well as adding a second custom field. For each custom field added, another "None" will appear. That's the real issue. I could probably just live with ignoring one, but when there's a bunch it'll be annoying and confusing.
Feels like a bug to me given the field heading isn't displayed. The intent is clearly to hide it given that. I suspect someone defaulted null values in the JavaScript or "None" string or something like that. Though it shouldn't even be shown in the first place if the heading isn't.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.