@Viji DP you can use a 'Version updated' automation:
Just change [SUBDOMAIN] to your jira instance, and [PROJECT_KEY] to your project key in the content section.
Any other changes in the content are up to you.
Unfortunately the Version updated automation is limited to trigger on any change:
From a quick search I haven't found any way to determine which field changed, so I'm not sure you can just trigger on release date changes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As far as I can see versions don't have a history, so all we have is the 'now' information and can't capture from that what actually changed.
I actually link Jira Service Management Change Request tickets to each release and use those for tracking dates etc. as I then have access to a change calendar that is easily visible to all teams, and update the version information when the change is complete.
If you don't have JSM you could just create a Jira ticket 'Release for version x' linked to the release and track the dates etc. on that.
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.