I am usig JIRA 5.1 with the latest bugzilla import plugin.
I found a hint here that the custom fields are now explicitly not created with global context:
Now I have found out how to change them to global context, and further imports of other bugzilla projects use the global custom fields rather than creating duplicates. That partially solves my problem, in that I'll be able to import more projects without creating new custom fields for each project.
However, before knowing about the global context, I imported two projects separately, and each got their own custom field. For example, there were two 'External issue URL' fields: one in use by project A and one in use by project B. I wanted a way to combine those two fields into a single custom field with global context, since it did not seem necessary to have several instances of a custom field with the same name. I have not found a way to do that.
Should there be a way to broaden a custom field to global context so that it gets combined with an existing global custom field with the same name? Or should I just accept that after importing several projects I will end up with several custom fields all named 'External issue ID'? Knowing what I know now, maybe that would have been best.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs