The easiest (but not very flexible) way to do it is change the notification scheme and include the group you want to mail in the "issue created" notification.
I'd prefer to do it with a role though, then you can reuse the method for other projects and groups without having to have a different scheme for every group.
The easiest way is to log in as an admin and, as a one-off set up:
Now, every time you want a new group (or user) to be notified of new issues in a project, go to the project admin and add the group (or user) to the new role
Ah, there's a setting in your profile which is probably set to "do NOT email me for my own changes". If you (temporarily) set that to "email me about stuff I've just done", and try another "create", you will get an email if the setup is correct.
@Nic Brough [Adaptavist] i have a question in uploading an Workflow to an existing project, which shares a common workflow scheme among 5 projects.
I want my new workflow to be uploaded to all 5 projects. Its only for Bugs and Defects,
the problem i am facing , we already have Defect workflow all the 5 projects what will happen to it,
And how to associate new issues types, when we move to an new workflow.
Need your help on htis
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs