Purpose
My company is looking at migrating to JIRA from our current story tracker Taiga.
Minimal Goal
At a minimum we are looking to migrate the following items:
Issues
User Stories
Epics
Sub Tasks
We are not interested in migrating the project name, settings user's etc, all of this is easy to set up in JIRA.
Looking For
We have looked for hours trying to find a migration tool or plugin to no avail. We ideally are looking for something, even a script that would make moving all of the above easy as there is a large data set.
Looking over the JIRA documentation around importing, they do not have native support for Taiga and the data that is export is difficult to get into the format (CSV or JSON) that they require.
Hoping to find a hidden gem that this community is aware of for the migration.
Both Tiaga and JIRA have a REST API that allows you to script this. If you're familiar with REST APIs this should be reasonably simple.
Taiga's REST API documentation is available here.
For JIRA you could use one of these REST resources:
Create issue: POST /rest/api/2/issue
Create issues in bulk: POST /rest/api/2/issue/bulk
Related
I used Firebase before. It was super simple, but It works only with non-relational database. I want to find something similar for MySQL but open source.
I found this two:
https://directus.io/
https://strapi.io/
I can't connect both to my old database or it seems complicated. I also can't find AngularJS integration. I found JavaScript integration for Strapi, but is unmaintained (https://github.com/strapi/strapi-sdk-javascript). If you recommend Strapi or Directus, is there any easy way to connect it to old database and JavaScript sdk?
If you install Directus clean, you can then just import your existing SQL tables/content and it will let you manage it. Should be very quick and easy to setup! There's a whole community on Slack that can help you out on that too:
https://directus.chat
By using Strapi you will not be able to import a database structure and generate automatically the API from it.
After that, in few clicks you will be able to map your Strapi content types (models) on your database table structure.
Let me know if you have any questions.
Goal: Export all SonarQube issues for a project to JSON/CSV.
Approach 1: Mine the sonar mysql database
Approach 2: Use the SonarQube WS API
First I was motivated to go for approach-1, but having discussion with the SonarQube core developer community I got the impression not to touch the database at any situation.
Thus I proceed with approach-2 and developed scripts to get issues. However, later I found that through WS-API, I can get upto 10000 issues which does not meet my goal.
Now I am convinced that the approach-1 i.e., mining the database is best for me. When looking at the "issues" table in sonar db, I have the following question.
Question. What is the format/encoding of the "location" field and how can I decode it from python/java?
Extracting data from database is not recommended at all. Schema and content frequently changes. Each upgrade may break your SQL request. Moreover it contains binary data (issue location) which can't be parsed as-is.
The only way to get data is through web services. If api/issues/search faces a limitation that you consider as critical, then you should explain your functional need to the SonarQube google group.
I am working on a project with a large CSV file that containes the location and movement of users. I would like to place this on a custom map in Google Maps via bluemix and use Bluemix Services to explore the data.
The primary goals are:
Getting the CSV data on the custom Google map. When running, the data should progress in time and show the movement of users.
Making the CSV points cluster for UX. (so that points that are near each other would stack together)
My primary question is how to get started on this. Do you reccommend i work on this locally and then connect Bluemix to my project or can i create all of this in Bluemix. I would much prefer the last option if possible.
If you have any suggestions to Watson Services or other Bluemix Features that may improve the app this is also greatly appreciated
Thank you for your time.
Ps. I realize Google Maps integrates best with Java Script. Do you recommend converting the CSV to Json when working with Bluemix?
This is a quite broad question and maybe not well suited for stackoverflow (stackoverflow is not a discussion forum, it is a competition of what answer is the most accurate one for a very strict question) so maybe this is a question for https://developer.ibm.com/answers/ instead.
That said, bluemix works well with js, java, ruby, python, go, php, etc (probably js and java better than the others) so I'd go in this direction. Also, I think you should investigate bluemix geospatial analytics (https://console.ng.bluemix.net/catalog/services/geospatial-analytics/) for your application.
For data storage, I suggest you to take a look on cloudant (https://console.ng.bluemix.net/catalog/services/cloudant-nosql-db/) which is a very popular option in bluemix and suits well for most cloud apps. If you want to take a more traditional approach, you can also consider a relational db such as DB2 (https://console.ng.bluemix.net/catalog/services/ibm-db2-on-cloud/)
At first, this question appeared to be too trivial to me to actually require a Stackoverflow post. However, after executing many Google searches for the information, I am at a lost when trying to figure this out about Couchbase.
In Couchbase (I am using the 2.2 Community version), how do I share views among developers? Is there some sort if import/export functionality available? If not, then how does Couchbase intend for developers to share the views that they are using without needing to do manual copying/pasting? It is obvious that the code that a development team would write for querying Couchbase will require accurate view names. Without having a way to send a developer a view file, to accurately setup a Couchbase DB, how can it even be possible to develop with Couchbase locally as a team?
I'm sorry if I sound a little desperate or harsh here, but if it isn't possible to share views among multiple developers, then I don't see how Couchbase can be a viable DB solution for a team of developers trying to share database configuration, similar to how a team using an SQL DB would share schema files to set up the DB.
Several ways you can approach this:
1) Create views programmatically as demonstrated here in java:
http://tugdualgrall.blogspot.com.es/2012/12/couchbase-101-create-views-mapreduce.html
or here in node.js:
http://www.tuicool.com/articles/RvYbQn
2) Store all your views in your version control system (This is the option I use). If you are developing locally then only you need your personal view code, once they are working and your tests are all passing then you can check them in.
I assume you'd then be developing on an testing environment so yes sadly here you'd have to update the views either by hand or by using option 1.
You could also take a look at perhaps using this tool but only for views: http://www.couchbase.com/communities/q-and-a/how-bulk-import-design-docs-and-views-couchbase-server
This functionality currently is not available in the admin UI.
There is a defect/enhancement open Ability to import/export views MB-8436. You can leave there your feedback and vote for it so it will be included in the next release.
In the meantime you can use Design Document REST API
Also there is a workaround blog
I am thinking about using the github issue tracker as an experiment, but leaving open the option to migrate to a more powerful issue tracker if our developer community finds the github tracker lacking. However, I can't find any information about such migration except this blog post
and this github article
which tells me how to export, but not how to get the resulting JSON into another issue tracker.
Is there specific information available on how to
accomplish this?
Specific import information will be specific to the tracking system you are importing into.
In general however like the JIRA example you linked to, you will probably need to switch the Github provided JSON to a CSV or XML file. Some of the keys may also need to be renamed. All of this should be manageable by writing or finding a short script for the task.