Here is my JQl
project = TEST AND issuetype = Story AND parent in (TEST-101, TEST-102, TEST-103) order by created DESC
TEST101,102,103 are Epics
It shows as below result, only story/features that are linked to each other appears under "Links" columns, How can I also show bugs that are linked to story/features
For example, Test1100 is a story/feature from one of the epic and under Links column it shows that it is linked to story/feature Test1101 and Test1102 but not the bugs which are also linked to Test1100
Hi William,
as allways with email notifications your main entry point is your notification scheme. You can define all actions that are used to send emails and also to whom they are sent. You should think about the following setup:
I know, this is kind of a general suggestion but that is at least hwo I would approach this.
Hope this helps kind of. Cheers, David
Hey David, thanks for your answer!
I've been looking in this scheme. What I really need is the ability to have a "General Manage Notification Scheme", and an "Everyone Else" one. Otherwise I have to edit every single line item of the notification scheme to add in this logic. Is that really what I will have to do? Is it even possible to add this logic in that way?
Say I use that approach is it possible to add an "Email the General Manager but only when they are the Asignee" type?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry to say this, but in JIRA there is one (notification) scheme attached to one project. So basically yes, that's the way to do this.
Unfortunately notificatins are based on events, rather than on conditions. SO you can say "email when issue is created" and only notify the assignee but not the whole group. Further grouping of conditions is not possible.
What you also could do is to create notification-specific project roles, say like "new issue reciever" who recieves emails whenever a new issue is created. This would give the project lead more flexibility and controll over notifications.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
OK, thanks for the info.
I think I'll do something like what you suggest. Maybe I'll setup the notifications to be by default a small set of notifications that *everyone* (even the General Manager) wants, basic things like "someone commented on your issue", and then add a group of people who are notification-hungry, and just send them everything.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.