We want to add our new issue tracker system to JIRA built-in importers. Is it possible? If yes, please let us know how to achieve it?
Here we found that JIRA no longer supports third party importers.
But again we have a tutorial for writing a custom importer. Is this different from adding a new issue tracker system to built-in importers? If it is different, what is it for?
We are totally confused with these.
Can anyone please clarify my question and about these tutorials.
An importer is a block of code that can read and understand a data source (file, database connection, etc) and convert the incoming data into JIRA data.
These data sources are almost always other issue trackers of some form.
To add a new importer, a new add-on is required to implement the read-source-write-JIRA process. So "a new issue tracker importer" is just "an importer"
On Cloud, you cannot add add-ons of this type. You could write a Connect add-on that runs elsewhere to read your data and poke it into JIRA over REST though.
For Server JIRA, your tutorial link is the starting point.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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