[#JRA-9616] Add option to make CSV Import cause notifications to be sent

JIRA

Add option to make CSV Import cause notifications to be sent

Created: 09/Mar/06 02:07 PM Updated: 10/Mar/06 12:34 AM

Component/s:

Import / Export

Affects Version/s:

3.5.2

Fix Version/s:

None

Time Tracking:

Not Specified

Participants:	Chris Mountford [Atlassian] and Sulka Haro
Since last comment:	123 weeks, 1 day ago
Labels:

Description

« Hide

Importing issues from a CSV file doesn't cause Issue Created notifications to be sent. Please allow users to configure the behavior.

Just imported 105 issues and now have to go to ten people asking them to recheck their issues in Jira as they got no email.

Import operations are an effective way to perform some bulk changes and may, especially in these cases, justify a notification.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Chris Mountford [Atlassian] - 09/Mar/06 10:37 PM

Hi Sulka,

Yes this is intentional.

As we do not currently provide an option to make notifications be sent automatically, a workaround may be, after an import, select all issues created as a part of the import (by date for example) and perform a bulk change -> edit -> change comment. Adding a comment to these issues would cause all assignees to be notified. In many cases this may do.

You indicate you're using 3.5.2 which includes a fix to ~~JRA-9415~~ which may have otherwise stopped this method from working.

I've modified the emphasis on this issue and reclassified it as an improvement.

Regards,

Chris.

[ Permlink | « Hide ]

Sulka Haro - 10/Mar/06 12:34 AM

Cool thanks. We're planning Scrum Sprints using Excel as the tool to gather the issues and then import the issues when the planning is done (in addition to moving issues already in Jira). Having the notifications on would be valid in this use-case.