Phill Fox Community Champion

Great news that this worked for you and you now have a working approach which confirms imports to JIRA are working. So what we need to do now is work through your export from Excel to CSV to understand what format (or possibly formats) are being exported from Excel. So if you now go into your Excel spreadsheet and save it…

I am not familiar with Editor so this may be your text editor but Wordpad will allow you to see the file content without changing any of the display format. I would avoid Excel as it changes your display (as you have seen) and if you save from Excel it will alter your base file as well.

here is a version of your test file but saved with the extension .txt rather than .csv. The JIRA Import does not worry about the extension. This file has the format yyyy-MM-dd.

What text editor are you using to look at your csv files? Notepad in windows? TextEdit on a Mac? None of these should alter the underpinning format. Note you may need to override the default editor for csv files when you open the file. Try changing the .csv to .txt on your filename to help pick a text rather than csv…

Your test file that you attached looks like this.Parent ID,Issue ID,Summary,Issue Type,Component,Reporter,Priority,Due Date,FixVersion,Doors Feature List Name,AssigneeDAIENTRY-643,,Automatic Driver Recommendation (ADR),Feature Dependency,NavCtrl,cfuehring,,2015-05-06,E21.0,FL TTS,,DAIENTRY-643,,Automatic Driver…

I am beginning to think that your issue is related to the display method of your different tools not matching the underpinning data. So if you can confirm that the format in the csv file you are using is 5/6/2015 then MM/dd/yyyy is the correct format.

The file you supplied showed up as 2015-05-06 in my text editor. Did you open in Excel or a text editor? Excel has a habit of reformatting dates to your "Preferred" format but it does not alter the underpinning date format.

Ok in this example you have 2015-05-06 representing 6th may 2015 and so the date pattern for this is yyyy-MM-dd

Corinna, Could you please attach the first 5 lines of the file you are trying to import, so that I can confirm the format I have given you matches. As I am now confused as to what date format you are trying to import.Also please indicate which part of the date is month and day.

Ok so your format is not 2015-05-06 but is 10:11 AM 1/6/2016 so the date format you need to use on the mapping is hh:mm a MM/dd/yyyy assuming that the date in your example is 6th January and not 1st June

@Corinna Führing Ok lets step back and work through this one step at a time. From your comment above you have a layout as follows. DAIENTRY-643,,Automatic Driver Recommendation (ADR),Feature Dependency,Traffic Information,cfuehring,,2015-05-06,E21.0,FL TTS,, So if you run the csv importer and set the date format to be…

So if we work on the challenges you face.1. The correct format for your JIRA configuration.2. The export from Excel.If we focus with 1 to start with. As I suggested earlier take one of your existing CSV files and edit the top 5 or so entries with different date formats and remove all the other records and then import to…

Hi @Corinna FühringIn principle this is the same date/time stamp but without knowing what configuration settings are on your JIRA instance it is difficult to be able to say it will be treated the same.I would personally create a short import file with a variety of different date formats until I find the one that works for…

That is strange. I can not spot an obvious correlation between those two dates 28-12-2014 and 05-05-2015. I have just tried an import on my local development instance and that wanted dates in the format YYYY/MM/DD which is year then month then date. This might be worth a try with a single record to see what you get.

Hi Corinna Führing Dates are frequently challenging as there are so many configuration choices you can make. So from your example you were expecting this to be imported as 6th May 2015 or 5th June 2015? And what date did you actually get? Once you work out the format that is correct for your configuration it will then be…

Here are a few JQL examples that may help you. Issue created between 1st January 2016 and 1st February 2016. createdDate > "2016/01/01" and createdDate < "2016/02/01" to add a set of issuetypes use AND issuetype in (list) to add the resolved use AND resolution = "Resolved" I hope this helps.

Changing domains is a restricted activity in Cloud solutions see the documentation at https://confluence.atlassian.com/cloud/restricted-functions-in-atlassian-cloud-apps-744721664.html. As @Nic Brough [Adaptavist] suggests raise a request with https://support.atlassian.com 

D

I hope you identified this in your test instance first so you should be fine to go ahead and make your proposed change to see if it resolves this issue. If this change does not resolve your issue you can postpone your plans for production upgrade and raise a support request to Atlassian. If however, you have already run…

Could you rephrase your question so that we might be able to help.

I will pull up a development copy of 6.4 tomorrow and try and reproduce your scenario. I do not have one to hand at the moment and it is nearly midnight here. Hopefully someone else may be able to step in and help before then. If you solve it on your own please let us all know how.

I assume you have already followed the steps at https://confluence.atlassian.com/jira/configuring-the-default-dashboard-185729539.html to set a default dashboard for your users? You should then look at the instructions on https://confluence.atlassian.com/jira/changing-your-jira-home-page-295309733.html to see the options…

Hi Gi Choi You can only import between matching versions. You should follow the upgrade process from your current version. Note that as your version is quite old you will need to do a couple of steps on the upgrade path. Make sure you read and understand all the changes along the upgrade path.

As @Nic Brough [Adaptavist] states this would be a really easy way to break lots of functionality. If the presence of resolutions is causing you pain a simpler option may be to change your workflow to allocate the appropriate (Completed perhaps?) resolution when users transition the final step in the workflow. You could…

I can understand both sides of the argument here. For many users removing the resolution on issues that have been closed will lead to challenges with their reports. Although for others it may be a valid resolution. Personally before removing any resolution I would always want to manually confirm the resolution each issue…

They already do... @Nic Brough [Adaptavist] is a legend in his own lifetime.

Who was this comment aimed at? @Phill Fox or @Chander Inguva ?

If you require the field to be changed only on the transition then you should add the field to a screen that is only used for the transition. It should not be included on any other screen especially the edit screen as that will allow inline editing. You then need to set a validator on the transition to ensure that the…

For JIRA on-premises there are a number of options available from marketplace.atlassian.com. Unfortunately for JIRA on-demand you are restricted to the internal user directory only. This is one of the differences between on-premises and on-demand.

You are welcome. Good luck with your changes.Phill