why don't show the Bug Import Id custom field in the page where i added it on the screen.
How to use this custom field?
Have you got any data for the field? It will only appear on screen if there is valid data for it on the issue (and the bug-import ID only gets populated when you do an import from an external system, and it's read-only)
When i edit an issue, the bug-import ID can not to be seen alse. Can you tell me why?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Because it is read-only.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Huang,
The fact is that the custom fields "Import Id" and "Bug Import Id" are not supported by JIRA importer (csv import) at the moment. These fields are used to store the issue id while performing import from Bugjilla or Mantis.
The improvement request for this is here : https://jira.atlassian.com/browse/JRA-32002.
As for now, I would recommend you to create a 'Text field' type of custom field and use it to store the id from the old application. You can then use a javascript on this custom field to make it read-only. This is the best workaround I can think for now.
Ruchi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have the same problem with @huang isabel, i want to use this field but i can't seem to be able to select it when performing External Systems Import with CSV.
I have created 2 custom fields, 1 with Bug-Import ID and another with just Import ID. But these 2 custom fields are not selectable from the drop down box when choosing which fields to import. I have to just use a text field to hold this data, which i would like it to be read only.
That's my workaround and I only show this field with View action.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
you need check:
1) field visibility scope. in custom fields - configuration for your field - applied context ( project, issue type )
2) in field configuration - field not hided for your project
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.