I am trying to update issues using import CSV given below:
Issue key,Summary,Progress,Date Modified
IPC-11,Task 1,30,20/Jan/2018 01:00
IPC-11,Task 1,40,20/Feb/2018 01:00
IPC-11,Task 1,50,20/Mar/2018 01:00
IPC-11,Task 1,60,20/Apr/2018 01:00
So Issue with key IPC-11 is supposed to get updated with "Progress" mentioned above. Progress is a field provided by BigPicture.
After importing, Issue gets updated 4 times and I can see all 4 Progress values too. But when I see them in "History" tab of the "view issue" screen, It shows everything is updated today. So the modified date is not getting captured or set during the import.
Yes, I have mapped "Date Modified" above to the JIRA "Date Modified" field during the import, still it doesn't gets updated.
I changed the CSV to JSON and was able to migrate/update Progress field as well as Modified Date.
I think, JIRA should remove "Modified Date" from mapping section if it;s not going to update because that's confusing and ends up with hours of debugging on the user side.
it is possible that the order of the field updates on the jira record is causing the modified date to get set to something else, after it is set to what you imported.
maybe try importing twice: the first time to update all the other fields, and the second time to just update the 'date modified' field.
just an idea....
also, are you getting any validation errors? maybe the date format is incorrect?
Thanks for the answer, Ericka.
I can't run import second time as I need to update the 'Modified Date' field of each version. As you can see in my question, the issue is getting updated 4 times with 4 different "Progress" values and of course each time it would have different "Modified Date". How do I run this import 2 times?
And I am not getting any errors or incorrect date format issues. In fact, it shows a success screen with a log of the imported issues.
But when I run an import for first time, it would save "Progress" with "Modified Date" as current time. Now, even if I run an import second time with only "Modified Date", it would be of use.
There is a mapping of "Progress" to "Modified Date", if you see in my example. And based on this modifications or history, there would a report/timeline of "Progress" over months.
@milanchheda Hello, I am in a similar situation where I would like to update the "Modified Date." However, CSV import using the "External System Import" just won't update it. It works fine with resolution date though.
This is what my CSV file looks like:
ABC-123, "This is a test",17/Jul/2018 18:26:14.000
I am using the "dd/MMM/yyyy HH:mm:ss" format.
JIRA Server Version: 8.2.x
Question for you: Did you create JSON for ALL of your fields, or just the modified date? Wondering if you could share an example.
@Kamran Ansari, Take a look at "https://confluence.atlassian.com/adminjiracloud/importing-data-from-json-776636779.html", I think is pretty complete.
Now, @milanchheda , I've imported a JSON updating some fields of existing issues. That's worked OK, but updated date is set to current date. Then I've imported only updated date with its original value, but again updated date is set to current date.
Did you get to import existing issues without modifying updated date?
Remember that time you realized it was possible to refresh your Jira data in Google sheets with just one click? What if we told you that you can now get the latest data with no clicks at all?! Zero! ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events