This functionality is based on a Listener, a Manager and a set of JellyTag.
The objective is to maintain an update date reserved to specific fields.
Usage is :
<JiraJelly xmlns:jira="jelly:com.atlassian.jira.jelly.MinyaaToolsTagLib"> <jira:AddNotifiableFields project-key="TST" reinit="true"> <jira:AddNotifiableField name="description" value="true" /> <jira:AddNotifiableField name="summary" value="true" /> <jira:AddNotifiableField name="myCustomfield" value="true" /> <jira:AddNotifiableField name="project.notifiable.customfield" value="NotableUpdateDate" /> </jira:AddNotifiableFields > </JiraJelly>
Script above defines 3 fields as notifiable fields. In case of update of the Summary or Description fields or the custom field - identified myCustomfield - the customfield date - identified NotableUpdateDate - has to be updated.
AddNotifiableFields Parameters :
Parameter | Description |
---|---|
project-key | Key of the concerned Project |
reinit | Boolean specifying if the listed Notifiable Field are replacing the previous configuration (true), or just extend it (false) Default value is false |
AddNotifiableField Parameters :
Parameter | Description |
---|---|
name | Field or CutomField name project.notifiable.customfield is a special key defining the Date Field name to update, when the change occurs |
value | Set to true if the value's change of the field has to be listened Or the Date Field name in case of project.notifiable.customfield key. |
This listener takes in charge the comparison of Updated Fields against fields defined as Notifiable. If at least of them is updated, then an update of norifiableDate is delegate to the NotifiableUpdateManager.
Usage is :
com.atlassian.jira.event.issue.NotifiableUpdateIssueEventListener