nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation returning errors, unable to find cause

Akina Yoshida

I have created an automation for one of my projects using the "issue transitioned" trigger which then updates a datepicker field through the "edit issue" option. I have implemented this exact automation in 3 other projects and followed the same process for all, however solely this project returns the following error message:

Found multiple fields with the same name and type: .

Done 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):

The field exists within the project and there is only one field called "Done Date". What could be causing this?

Accepted answers

All comments

Trudy P Claspill

Hello @Akina Yoshida

Welcome to the Atlassian community.

Are the projects with which you are working Team Managed projects or Company Managed projects?

Can you show us the details of the rule?

Can you show us an example issue from the project, showing us the "Done Date" field?

Jira does not prevent the creation of multiple custom fields with identical names. On top of that in Team Managed projects each project can create its own custom fields again using the same names as other fields that already exist.

In that case you may need to identify the unique custom field identifier for that field in that project using the method described here:

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Once you have that you would then have to edit the field using JSON rather than simply picking the field from the available field list.

Dan Tombs

You may find that there is a context on the done date field stopping the issue being edited on the issue. With custom field with duplicated names. Just use the {{issue.customField_<insert field number>}}. You don’t need to edit using json

Trudy P Claspill

@Dan Tombs

In the Edit Issue action how do you specify the field you want to edit by using a smart value for that field, if not by using the JSON edit option? Please share a screen image.

I don't see an option to use a smart value for identifying the field to be edited.

Screen Shot 2023-07-26 at 3.14.21 PM.png

Mohanraj Thangamuthu

Hello, You can try using custom field ID in the automation rule action or if you could find the duplicate field with same name, you can re-name the field to different name.

Sayed Bares [ServiceRocket]

@Akina Yoshida welcome to the community!

Can you provide more information from your automation rule? perhaps a screenshot would be very helpful?

Akina Yoshida

@Trudy P Claspill I have included screenshots of how this appears within the issue and is set up.

When setting this up, I followed nearly an identical process for the "Created" and "In Progress Date" automations which have been working fine.

@Dan Tombs As said above, if you could include a screenshot of how to use the custom field without needing JSON, please provide.

Screenshot 2023-07-27 092045.png

Screenshot 2023-07-27 091252.png Screenshot 2023-07-27 091224.png

Akina Yoshida

@Sayed Bares [ServiceRocket] please see the screenshots in the reply above.

Akina Yoshida

@Mohanraj Thangamuthu could you include a screenshot of how to set up the rule in order to use the custom field ID?

Mohanraj Thangamuthu

Hi, Please refer to the examples in this link . https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud