Hi all,

Although we appreciate that this bug is not great in terms of User Experience, unfortunately, it is unlikely that we will address it in the near future.

We are working on a new Importer for Jira (JWM, JSW, JSM, JPD) to solve many of the existing JIM bugs and provide a better experience while importing data. 

We have already shipped it in JWM with more features to come soon: Import data from other tools into Jira Work Management 

As a result, we decided to close this bug as Won't fix.

Follow the updates on our public roadmap Cloud Roadmap

Thank you again for providing valuable feedback to our team!
Jira Cloud team

To say that you are continuing your culture of honesty, while at the same time choosing to let a known bug go ignored is hard for me to reconcile.  How is that a culture of honesty?  Your motiviation is not in your customer's interest if you are choosing to sweep this under the rug.  If you were a culture of honesty, you would have some big disclamer to those who are taking their valuable time to submit issues, troubleshoot them, and provide feedback.  Something like: "Hey everyone, just to be honest here, even if this is in fact a bug, there's a chance we will just decide we don't feel like fixing it, so be aware you could just be wasting your time even bothering to submit it"  Why would the community continue donating their time to improve your product when your company behaves in this manner?  And why would you want to close the bugs that are not resolved?  You can't focus on your upcomming roadmap because your system has too many bugs?  That statement doesn't even make sense, but even if so, the soution is to make some of the bugs go away???   Wow, just wow.  What harm is there in keeping them open, and having a full inventory of what is wrong with your product?  Please explain that to me?  Why not just keep bugs open until you are capable and have the resources of fixing them?  Do you have any idea how much difficulty i went through trying to migrate to your system because of this bug?  Wasted countless hours trying to get it to work properly for us.  Complete BS, that's what this is.  Even though this issue is no longer impacting me, witnessing this behaviour, and your lack of commitment to improving your product, makes me question a lot of earlier assumptions about your company in a not good way.   Possibly the first thing many new customers will have is to experience how broken and/or poorly designed your importer is, and then to find this bug, and see that it was closed on purpose without resolving?  That's not a good look.  Good luck to your organization with that kind of company culture.  

If you are importing just ticket id, summary, and comments, then the issue is even worse.  All comments are imported as the user performing the import.  Its as if the importer first builds a list of users associated with the import, and if not found in that list, defaults to the user performing the import.  So frustrating.