Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to use Automation to set "Start date"

Scott Robertson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 18, 2023

I am working in a Company-managed business project (Work Management).  I am attempting to use Automation to set the "Start date" when an issue is moved to "In Progress".  When attempting to do this using conditional to evaluate if the "Start date" is empty, I get the following error in the Automation Audit Log:

---

Edit issue
Found multiple fields with the same name and type: .
Start date (com.atlassian.jira.plugin.system.customfieldtypes:datepicker)
No fields or field values to edit for issues (could be due to some field values not existing in a given project):

 

---

There are no other fields in this project called "Start date".  In addition, the field is not custom, it is the "out of box" start date that is used in this project for setting start dates and is used in the List view (gantt).

1 answer

1 accepted

0 votes
Answer accepted
Harry Chan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
January 14, 2013

Hi, I assume you are running this on Linux. Can you post the whole setenv.sh file where you've made the modifications? Also do you have any custom startup scripts?

Serge Dukic
January 14, 2013

After double checking the configuration, realised that I was modifying the wrong setenv.sh file. The file I was modifying belongs to a previous install of Jira and is not used by the startup script.

Suggest an answer

Log in or Sign up to answer