How can I configure Actual End field defaulted to Resolution date field?

[Sucharitha Revanuru]

As of now we are entering Actual End date manually, but I wanted that to be defaulted to Resolution date. Please can you help me creating rule for it or any other way to do it? Thanks 

[Sucharitha Revanuru · Accepted solution]

@Trudy Claspill Your suggestions helped, and they worked. Thanks so much. 

[Trudy Claspill · Accepted solution]

Hello @Sucharitha Revanuru 

Please show us the rule you have developed so far and point out the portion where you are having difficulty.

You should be able to use the Issue Transitioned trigger to trigger the rule when an issue is transitioned to a Status where the resolution is also set.

Then you could use an Edit Issue action to copy the information from the Resolved date/time field to your Actual End field.

You will have to find the right smart value for referencing the Resolved date field.

You may have to add a date/time formatting function to get the information into the right format for the Actual End field.

[Sucharitha Revanuru]

Thanks for your reply. 

Unfortunately I have nothing to show you, as I didn't how to create the rule in the first place, appreciate your help in guiding me accordingly. Thanks 

[Sucharitha Revanuru]

no, it didn't answer my question 

[Trudy Claspill]

Have you tried constructing the rule based on the guidance I provided?

The home page for documentation on Automation Rules is here:

https://support.atlassian.com/jira-software-cloud/docs/automate-your-jira-cloud-processes-and-workflows/

If you have tried creating the rule following my guidance and it is not working then please 

- show us your entire rule

- tell us in what way it is not working. Is the rule not being triggered? Is the field not getting set? Is there an error in the Audit Log?

- show us the Audit Log for an execution of the rule

The Audit Log for a rule can be found when you are viewing the rule.

When you click on that you will get a list of each time you changed the rule (Config Change) and each time the rule executed with a status (i.e. Success, Some Errors). You can click on the Show More link on the right to get more information about the specific event.

[Sucharitha Revanuru]

[Sucharitha Revanuru]

See the Screenshot above: 

Rule: Green Highlighted - When the status of an issues transitioned from In Progress to Done and condition being the Resolution of the issue is done, then the Active End date should be defaulted to Resolved date. 

But here I'm stuck at Edit Issue fields option where Actual End is not found in the drop down (see red highlighted), as it seems not supported at this time. 

Please help me at Edit Issue fields if you can! 

Thanks 

[Trudy Claspill]

Please show us a screen image of an issue that uses the "Active End" field, showing that field on the screen.

What type of field is "Active End"? Is it a Date Picker field?

Is this field used in a Company Managed project or a Team Managed project? When viewing the project you will see which type it is at the bottom of the navigation pane on the left. Example.

[Sucharitha Revanuru]

Sorry Typo error - it is "Actual End" (Actual end date field) - Red Highlighted in the screenshot below. 

Just to give you some context I have two custom fields in my project - Actual Start and Actual End date fields. Over here I'm looking for getting the Resolution Date field value in to Actual End date field value. And in edit issue dropdown the custom field "Actual End" isn't there. 

And it is a Company Managed Project. 

Hope this Helps

[Sucharitha Revanuru]

[Sucharitha Revanuru]

In the image above, a search for Actual End field returns no matches. 

[Trudy Claspill]

Based on your screen image it appears that you are trying to construct this rule on the Atlassian site for the Automation Playground.

https://www.atlassian.com/software/jira/automation-template-library

The only fields available there are the ones that Atlassian has made available in the Playground. That is not constructing a rule on your own Atlassian Jira site with access to your projects and fields.

You need to be creating the rule on your own Jira site.

In the project where you want this rule navigate to Project Settings > Automation. Then click Create Rule. That will allow you to construct a rule within your site, with access to the fields you have defined for your site.

[Sucharitha Revanuru]

Thanks, Got it! 

Now, I'm on my project Site, found the Custom field - Actual End. But ResolutionDate (Resolved) isn't there in the Drop Down. See the JSON Referencing for the ResolutionDate field (which is Resolved). See the JSON below.

Also see the screenshot below where Resolved (ResolutionDate) isn't there in the drop down. 

For your information see below the JSON referencing for Actual End 

How can I copy the ResolutionDate (Resolved) field value into Actual End field? or is it something that because we don't see Resolved date field in JIRA, we can't find it in the Choose fields drop down? Am I missing something here?

[Trudy Claspill]

Hello @Sucharitha Revanuru 

First, in the Edit Issue action you need to choose the field you want to set. In that case you need to specify your Actual End field. In my example I have chosen the my field named "Custom Date Picker".

After check-marking the field, click somewhere outside of the Available Fields list to make that pop-up go away. You will then see the field you selected on the screen, like below.

Next, you fill in the entry field below that to specify what value to insert into the field you picked.

You can choose the type in a smart value to get the value from another field. Or you can click on the ... button to the right and select COPY to use the built in functionality for copying data from one field to another.

When you select that, Jira will automatically fill in copy instructions.

You can click in the X text in that field to pop up a dialog to let you change those instructions.

Here you can change which field you are copying data from, and the Resolved field is one you can choose.

[Sucharitha Revanuru]

@Trudy Claspill - Thank you so much, it worked fine. I have executed the rule with Success. See the Audit log below. Thank you so much for your patience, help and support. 

Thank you! :-)

[Sucharitha Revanuru]

Sorry just another question: 

> If I wanted to change the issue status back to IN Progress, how can I remove the Actual end date (means I would want to cancel the rule above)? 

For which I wrote another rule (see below), but it seems to be not working. 

[Trudy Claspill]

Hello @Sucharitha Revanuru 

If you want the field to be blank then you need to not put any value in the field where you have specified {{now.jiraDate}}.

Another way to clear a field during a change of Status is to modify the Workflow Transition for that status change, and add a Post Function for Clear field value.

https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/#Post-functions

[Sucharitha Revanuru]

Thank you So much :-), it worked. You're a star :-) 

[Trudy Claspill]

I'm glad I could help!

If your questions have been answered, please consider marking this Answer thread as Accepted to help other users find the posts that have working solutions.

[Sucharitha Revanuru]

Hi @Trudy Claspill I'm back again with another rule: 

I created a rule to add two fields Start Date (customfield_10015) and Original Estimate field (timeoriginalestimate), and to get the value in to third field which is End date field (customfield_10042), although rule executed successfully, the end field is still empty. I followed exactly step by step, however for a different field which is End Date from this help Automate Due date of an issue from Original Estimate | Atlassian Cloud | Atlassian Documentation

- the End field remains blank despite the rule is success. See the screenshot below: 

First Rule: Create variable to store the time tracking estimate in business days when issue is created using the below query:

{{#=}}{{issue.timetracking.originalEstimateSeconds}} / (60 * 60 * 8){{/}}

Second Rule: When the issue is transitioned from Backlog to Selected for developement, with the Edit issue action as follows: 

Formula: {{issue.Start date.plusBusinessDays(TimeTrackingDays.asNumber).jiraDate}}

After execution (See the Audit log below); 

End date is still blank (see below): 

Would you please let me know what could have gone wrong? 

Thanks

[Trudy Claspill]

Hello @Sucharitha Revanuru 

You are now asking a different question about a different automation need than your original post. Please start a new Question thread.

[Sucharitha Revanuru]

As advised I have started another thread, see below - Automate End date of an issue from Original Estima... (atlassian.com), pls can you help on that.