Using v4.3, I have a workflow used to manage our support queue that pulls issues from multiple projects. One user needs to receive email notifications when a specific event occurs for issues in one and only one of those projects. I created an event and a listener that was specific to that project but he still is receiving notifications any time any issue from any project goes through that workflow step. What's the best way to achieve this end result? The event/listener combo has always worked for me in the past but this is the first time I needed to limit it to a specific project. I can't use the issue type in a workflow scheme because all of the projects share issue types.
What's the best way to achieve the desired end result here? I'm out of ideas.
There's several ways to do it, but all of them mean making the project an exception.
First, you've got an event being fired by the workflow - that's the most important thing to focus on. The reason your user is getting emails is because that event is
So, you can either
Note that the second is a lot easier to create and maintain.
(I'm not actually sure why you have a listener here - JIRA does notifications without any need for a listener, it's built in)
Thanks! I was halfway through implementing the "2 different workflows" solution when I realized that the projects are using the same issue types so I can't throw them all into the same workflow scheme. Different notification schemes makes sense, I was just trying to avoid creating a duplicate scheme that would have to be updated if I updated the first one. But I think you are right that it's the best solution here. I added a listener because of the ability to specify a project key. I was hoping that would tell JIRA, "I only care about this event when it happens in this project." but it didn't. I am curious what the Project Key field in the listener settings is supposed to do.
I don't know what listener functionality you're using there, so I'm not sure what to ask... I'd also take a look at what Joe said - it's a third option. Because you could set up a new role like "Special events", put your user into it (only on that one project) and change your notification scheme so that it only notifies that role for the event. That might not be the best solution for you - it depends on where you want to shift the complexity. I'm pretty sure Joe would agree that the workflow is the worst place for the complexity. His method shifts it into the Project user stuff, and mine into the notification schemes. I can't judge which is better (but I'd probably say his!)
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
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