Automation rule for Target start and target end date of Jira issue based on Versions added

[satyanarayana_singamsetti]

Hi All,

Need help to create automation rule on below topics

1. Bulk create first time Target start and Target end date based on fixVersion

2. Target start and Target end date based on fixVersion

Is it recommended to do so? 

Regards,

Satya

[Trudy Claspill]

Hello @satyanarayana_singamsetti 

Let us back up. Can you explain to us the problem you are trying to solve , and why you think this is the right solution.

Target start and Target end generally are used to indicate when you are expecting work to begin for an issue, and when you are expecting the work to end.

The Fix Version field is generally used to indicate the versions in which the changes related to the completed issue are released. The Fix Version field may contain multiple values, associating the completed work with multiple versions.

How do you see Target dates relating to Fix Versions in this scenario?

[satyanarayana_singamsetti]

Hi,

Thanks for the reply.

I will try to explain in detail.

When we create Versions(releases) in JIRA Project, we will add start date and end date for it.

Our requirement is, when we add FixVersion value in Jira ticket, then Target start date and Target end date of that Jira ticket should be updated automatically as per Version dates. We are expecting the same behavior while creating an Issue or editing an issue.

Hope you got my query.

[Trudy Claspill]

What problem are you trying to solve by implementing this?

What would you expect to have happen when there is more than on Fix Version associated with the issue, that the Fix Versions have different dates?