I’m testing a CSV import for epics and stories in Jira. The problem is Jira keeps emailing users when they’re assigned to items. This is just for testing data accuracy, so I don’t want to bother people with emails.
I looked through the settings and FAQs but couldn’t find a way to turn this off. Does anyone know if there’s a temporary way to stop these emails during imports? I want to finish my tests without flooding everyone’s inboxes.
I’ve already checked all the system settings I could find, but there doesn’t seem to be an option specifically for disabling emails during imports. Any help would be great. Thanks!
hey, i’ve run into this too. what worked for me was using the ‘bulk change’ feature after import. first import everything without assignees, then use bulk change to assign later. no notifications that way. also, check if ur jira has a ‘quiet period’ setting. some versions have it, lets u pause notifications temporarily. worth a look!
I’ve dealt with this exact issue before, and it can be quite frustrating. One workaround I found effective is creating a dummy user account specifically for imports. Assign all the items to this account during the CSV import process, then bulk reassign them to the correct users once you’ve verified the data accuracy.
Another option is to temporarily disable notifications at the project level. Go to Project Settings > Notifications and turn off all notification schemes for the duration of your import. Just remember to turn them back on when you’re done.
If you’re comfortable with scripting, you could also look into using the Jira REST API to perform the imports. This method gives you more control over the import process and can bypass the usual notification triggers.
These approaches have saved me countless headaches during large-scale imports. Hope this helps!
Having faced similar challenges, I can suggest a less conventional but effective approach. Consider setting up a staging environment that mirrors your production Jira instance. This allows you to perform imports and tests without affecting the live system or triggering notifications.
If that’s not feasible, you might explore Jira’s automation rules. Create a temporary rule that intercepts and blocks notification events during your specific import timeframe. Just ensure you disable or delete this rule after testing.
For a quick fix, you could also temporarily modify email addresses of affected users to invalid ones (e.g., append .invalid to each). This prevents emails from being sent while maintaining user associations. Remember to revert these changes post-import.
Always backup your data before attempting any of these methods. They’ve proven useful in my experience, but choose the one that best fits your specific Jira setup and organizational policies.