Atlassian Team members are employees working across the company in a wide variety of roles.
February 5, 2025 edited
Hello all! Thank you for sharing your feedback on importing issues into existing projects!
The old CSV import tool continues to be available for use and you can leverage it to update issues in an existing projects
This iteration of the importer is primarily designed to help move issues and users from other tools into Jira Service Management which is why we prioritised new projects. However, we do recognise the need to make it available for existing projects as well. We are working on this as well and hope to make it available soon.
As my fellow veteran Jira/JSM admins will attest to though, it is a curious decision to encourage users import issues and users into new projects without giving them more tools/guidance on things like project security, workflows, etc.
I mean, sure, your user research might have a lot of people saying "We want to import from Monday.com, Clickup, Notion! Let me do that in the smallest number of steps!"
But IMHO you're doing a disservice to those users by dumping all those users and issues into a project that they will have to fix AFTERWARDS.
"Oh crap, everybody in the company can see our tickets from Asana? No, they're just for our team!"
"Huh, in Monday.com we had an additional Review step between In Progress and Done. What happened to that step? Oh no - what happened to all the issues that were in Review? Wait, you just made them all In Progress?"
I'm sure my fellow admins will have other thoughts of what can go wrong, but those are just a few thoughts off the top of my head.
YES YES, I understand Atlassian wants to make project creation and adoption easier. And for a brand new project, I think that makes some sense.
But an Import is not just issues and users. A properly done import needs to consider process, and permissions, among other things. (Folks, what am I forgetting?)
Your new tool, as nice as it is, doesn't address those last two elements.
27 comments