Mailing-List: contact dev-help@syncope.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@syncope.apache.org
Date: Mon, 11 Apr 2016 15:49:25 +0000 (UTC)
From: =?utf-8?Q?Francesco_Chicchiricc=C3=B2_=28JIRA=29?= <jira@apache.org>
To: dev@syncope.apache.org
Message-ID: <JIRA.12957742.1460389732000.193814.1460389765609@Atlassian.JIRA>
In-Reply-To: <JIRA.12957742.1460389732000@Atlassian.JIRA>
References: <JIRA.12957742.1460389732000@Atlassian.JIRA>
 <JIRA.12957742.1460389732548@arcas>
Subject: [jira] [Created] (SYNCOPE-830) Associate notification tasks to
 related notifications
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Francesco Chicchiricc=C3=B2 created SYNCOPE-830:
----------------------------------------------

             Summary: Associate notification tasks to related notifications
                 Key: SYNCOPE-830
                 URL: https://issues.apache.org/jira/browse/SYNCOPE-830
             Project: Syncope
          Issue Type: Improvement
            Reporter: Francesco Chicchiricc=C3=B2
             Fix For: 2.0.0


Currently the {{NotificationManager}} generates {{NotificationTask}} instan=
ces for all defined {{Notification}} instance, under the given conditions.

Once generated, however, there is no link any more between {{Notification}}=
 and {{NotificationTask}}: such connection can be useful to trace from task=
 to notification, to see when a given {{Notification}} became effective, an=
d so on.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)