-
Suggestion
-
Resolution: Tracked Elsewhere
-
None
-
6
-
We are tracking this request in our new Importer Plugin here: https://ecosystem.atlassian.net/browse/JIM-257
You may also like to read the latest CSV import documentation.
We use the CSV importer to regularly import new issues from the bug tracking system of a customer.
With the wizard it was very easy to initially define a mapping between the 2 systems.
The problem is, the CSV importer of Jira can do only INSERT, no UPDATE.
So we have to manually update Jira to keep it in sync with the customers bug tracker.
Our customers do not change very often the issues after we get them, but sometimes they do
and as projects are getting bigger this is becoming too much to handle manually.
Are there any plans to add to the CSV importer the capability to update already imported issues?
Or are there any other solutions to this problem?
Are there any "standard" Jira solutions?
As I see the Jira CSV importer was created as a tool to import data from another system once,
not to keep data in sync between two systems. But with a small
extension it could be made into one.
I just could not find this issue anywhere here in Jira's Jira. We need a solution quite urgently.
Regards
Bettina Zucker
- is duplicated by
-
- Closed
- is related to
-
- Closed
[JRASERVER-9994] Extend CSV import to update already imported issues
| Workflow | Original: JAC Suggestion Workflow [ 3043132 ] | New: JAC Suggestion Workflow 3 [ 3671337 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2603060 ] | New: JAC Suggestion Workflow [ 3043132 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2552041 ] | New: Confluence Workflow - Public Facing v4 [ 2603060 ] |
| Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2339148 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2552041 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2113911 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2339148 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2091899 ] | New: JIRA Bug Workflow w Kanban v6 [ 2113911 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 889062 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2091899 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 [ 709485 ] | New: JIRA Bug Workflow w Kanban v6 [ 889062 ] |
| Backlog Order (Obsolete) | Original: 111930000000 | |
| Bugmaster Rank (Obsolete) | Original: 2950000000 | |
| JIRA Support Rank (Obsolete) | Original: 59890000000 | |
| Studio Rank (Obsolete) | Original: 3370000000 | |
| Support Rank (Obsolete) | Original: 3370000000 | |
| Workflow | Original: PM Feature Request Workflow [ 228447 ] | New: JIRA PM Feature Request Workflow v2 [ 709485 ] |
| Issue Type | Original: New Feature [ 2 ] | New: Suggestion [ 10000 ] |
| Priority | Original: Critical [ 2 ] | |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Description |
Original:
{panel:borderStyle=solid}We are tracking this request in our new Importer Plugin here: https://studio.atlassian.com/browse/JIM-257
You may also like to read the latest [CSV import|http://confluence.atlassian.com/display/JIRA/Importing+Data+From+CSV] documentation. {panel} \\ We use the CSV importer to regularly import new issues from the bug tracking system of a customer. With the wizard it was very easy to initially define a mapping between the 2 systems. The problem is, the CSV importer of Jira can do only INSERT, no UPDATE. So we have to manually update Jira to keep it in sync with the customers bug tracker. Our customers do not change very often the issues after we get them, but sometimes they do and as projects are getting bigger this is becoming too much to handle manually. Are there any plans to add to the CSV importer the capability to update already imported issues? Or are there any other solutions to this problem? Are there any "standard" Jira solutions? As I see the Jira CSV importer was created as a tool to import data from another system once, not to keep data in sync between two systems. But with a small(?) extension it could be made into one. I just could not find this issue anywhere here in Jira's Jira. We need a solution quite urgently. Regards Bettina Zucker |
New:
{panel:borderStyle=solid}We are tracking this request in our new Importer Plugin here: https://ecosystem.atlassian.net/browse/JIM-257
You may also like to read the latest [CSV import|http://confluence.atlassian.com/display/JIRA/Importing+Data+From+CSV] documentation. {panel} \\ We use the CSV importer to regularly import new issues from the bug tracking system of a customer. With the wizard it was very easy to initially define a mapping between the 2 systems. The problem is, the CSV importer of Jira can do only INSERT, no UPDATE. So we have to manually update Jira to keep it in sync with the customers bug tracker. Our customers do not change very often the issues after we get them, but sometimes they do and as projects are getting bigger this is becoming too much to handle manually. Are there any plans to add to the CSV importer the capability to update already imported issues? Or are there any other solutions to this problem? Are there any "standard" Jira solutions? As I see the Jira CSV importer was created as a tool to import data from another system once, not to keep data in sync between two systems. But with a small(?) extension it could be made into one. I just could not find this issue anywhere here in Jira's Jira. We need a solution quite urgently. Regards Bettina Zucker |