This is hugely frustrating, as I had this working some time ago. Now I am trying to do it again from scratch, and I am simply unable to tuck custom fields into a tab in the standard 'View Issue' screen. I can see the tab, and custom field within the 'edit' screen, but not the 'view screen' if that makes sense.
@Tom Proctor - There's the big 'Associate and issue operation with a screen' button top right corner. Do I have to 'map' each of create, edit, and view with the 'scheme' I have created with the tab?
Steve - They are not empty; they have default values. All good, I can see the TAB > custom field within EDIT, but the problem is I cannot seem to enable TAB in the standard 'view issue' screen... these custom fields appear under the default 'Details' section. I want a tab.
I can't seem to add new comments (three points?) so I'll add the screenshot here.customfield1.jpg
No, I am still not sure. Now I unfortunately need to ask, can we see the edit screen, where the default value is plainly visible, as well as see the view screen the field is misbehaving on?
Without access to your system we really can't tell unless you show us, sorry for the screenshot request.
(also I just realized I'm on a extra account, my other one can approve users [i wish i could merge accounts @atlassian!])
I opted to start from scratch again, and push the changes to my production project. I am now able to see custom fields in a 'development' tab on both the view and edit screens. I am not certain why I the above issues happened, but the fresh start seems to display the tabs in View and Edit modes. Perhaps the test project I was using was polluted.
There are default values placed into the custom fields (Developer Notes "<enter dev notes here>", and Code Review Checklist as "NOT REVIEWED" for example). This ensures new tickets, when filed, have the tabs appear.
I then bulk edited all open items that had not yet been 'code reviewed' with the defaults, so the tickets have values. Those beyond code review at this time have no defaults, and the tabs only appear in 'edit' (expected behaviour).
I am now seeing many tickets with both custom fields in the 'Details' area, with no Tab behaviour. I cannot seem to find a pattern (in a certain status, or of a certain type) for the ones that are not tabbed vs those that are.
Thanks for your help, and patience.... the naming convention of scheme, screens, and screen schemes has me all loopy! Here's a condensed screenshot of the various admin options, and what i have. If you need more, I have numbered the UIs and you can tell me what to click, and screen shot =)
I think you're doing a good job of setting this up and explaining it. The language can be crazy sometimes, I agree.
Your issue view screen makes this very plainly an issue – Task has a defined screen yet looks different in two different issues! The only way this could happen is if you had duplicated custom fields, some issues filled with one, and others with the duplicate.
I'm going to think a bit, but you really have me stumped. I have never seen anything quite like this before and I've been working with JIRA for years.
Well, one thing I can't tell in your View Issue Screen screenshots, the ones bordered by red, is if they're in the project you've assigned these screens to.
You could show me this by expanding your screenshots of the issues to show they're in the same project.
Then you could show me the Issue Type Screen Scheme assigned to the project, within that project's Project Administration section. That I think closes all loops as far as verifying that you have configured JIRA as intended.
However, I think you're encountering a weird bug or something – I can't find anything related to disappearing tabs... Usually it's just people not familiar with JIRA's behavior to hide fields that are null.
Well, I have some closure for those curious minds.
"Epic Link" is one of a few stock JIRA fields considered 'Custom'.
So, if this field contains null, the default 'Field Tab' in the View screen will be suppressed. As such, this has a fallout effect of suppressing the second 'Development tab' I showed above.
It's likely the same behaviour will erupt with 'Sprint' as well.
Not certain if there is one. I had a support ticket with them on this?
They did add some feature requests based on this.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot