issue timeline notification

[Alok kumar Singh]

how to to setup mail notification to some specific people when an issue has crossed it's timeline.

[Renjith Pillai · Accepted solution]

Do this:

• Create a filter with your criteria for due date and assignee = currentUser()
• Create a subscription for jira-users group as per your required interval (daily I guess)

Every user will will receive their issues alone when the due date is nearing/crossed (as per the filter criteria set). No individual subscriptions needed and this will appear as a builtin feature of JIRA :)

[Alok kumar Singh]

thnks Renjith I will try to do this.

[Nic Brough -Adaptavist-]

As well as the subscription method Tecken Yew mentioned, you can use https://confluence.atlassian.com/display/JIRA/Jelly+Escalation to do things that will send emails after a certain time has elapsed.

[Teck-En]

You can create a filter to search overdue issues and subscribe the filter for daily/weekly notification. You may want to have a look on the FAQ of this page : https://confluence.atlassian.com/display/JIRA/Receiving+Daily+Due+Date+Subscription

[Alok kumar Singh]

i want it as a generic feature not restricted to filter.

[Alok kumar Singh]

No, the idea is to when an issue crosses it's due date. It should be able to automatically trigger mails to people related to the particular issue(I have already mentioned "specific people").

[Nic Brough -Adaptavist-]

Then how do you choose what issues to send the mail about?

Sorry, but that's nonsense - if you can't identify what issues you want to tell people about, then how else do you know what to send?

[Nic Brough -Adaptavist-]

You're not understanding the point. I understand the target of the emails should be a list of "specific people" (Which you'll need to define somehow, but I assume you already have a way to do that)

The point is how do you identify which issues cross the line and hence need to send email for?

In other words, what do you mean "generic feature"? It sounds to me like "has passed it's due date" is, um, a filter...

[Nic Brough -Adaptavist-]

Um, no, I don't have any doubts. What I'm struggling with is your "generic feature" rather than "filter" and then describing a filter.

Could you explain what you want and how it should work *without* using a filter to find them? Because you've posted something that is a filter three times, without explaining why it's not a filter.

[Alok kumar Singh]

thnx Nic, for making things clear. If any issue has not been addressed within it's timeline and it was associated with some specific project A. Then the people related to that issue should automatically be notified that the issue has already crossed the due date and it is still unresolved.

I think this will clear your doubt "which issues cross the line and hence need to send email for".

[Alok kumar Singh]

Well creating a filter and subscribing it a kind of manual process.

The idea I am having is creating a event listener plugin where whenever a issue crosses it's timeline a event should be fired which will send e-mails to specific people. It's just a vague idea I am having right now.

In this way I can avoid creating filters for projects though i will have to add subcriptions.

I hope you are able to draw the conclusion what I am trying to achieve.

[Nic Brough -Adaptavist-]

Yes, subscribing to a filter is a manual process.

Your event listener idea will not work. Nothing happens when an issue goes past it's due date - there's no change to an issue, all that's happened is a normal flow of time.

In other words, the USER needs to actively look for issues that match the question "has this gone past it's due date". Which is a filter.

Could you explain how you think this might work without a filter? I'm still not seeing how "find an issue with certain data on it" is not a filter.

One thing that might help here - in your mind, separate the problem into two parts -

The first part is "finding issues to talk about" (and this is where we're a bit stuck because filters are the only real way to do it and you seem to want to rule them out without specifying another method) and the second is "telling people we need to talk about it".

I think you've specified the second part quite well already - you want to send them emails. Subscriptions is one way to get those emails sent, but not ideal for you because you don't want to have to do it manually. Jelly scripting (my other answer) will send the emails as well, without your manualy subscriptions, but you'll need to think through how to do it carefully.

[Alok kumar Singh]

Awesome Nic....thanks a lot for the way you explained, Is it possible to automatically issue shoud get assigned to the Concerned People.