Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Set Date with Automation

AB November 6, 2023

Background:

I am trying to set up an automation so that when a ticket is transitioned from a todo state to an in progress state the current date is set in a custom date picker field called Start date.

When setting this up I have the trigger as a transition and the action set up as an edit issue. I have set the Start date field to be set as {{now}} but it keeps getting errors when triggered. The error says that there is multiple fields with the same name. The other field is called "Start Date" and has a capital D. It is also not assigned to my field schema. 

Additionally the automation i use to set the due date when a ticket is transitioned from in progress to done is set up the same way and works.

How can I set this up so it can set the date when transitioned?

Edit Issue Config:

Screenshot 2023-11-06 at 4.42.49 PM.png

Error from audit log:

Screenshot 2023-11-06 at 4.39.51 PM.png

3 answers

1 accepted

0 votes
Answer accepted
Marc - Devoteam
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 Leaders.
November 7, 2023

Hi @AB 

This is an issue that I have experienced manier times.

Field names are stored with lower and upper case in the backend. So the error thrown is that Jira automation sees all field and doesn't look at the field schemes.

Having multiple fields with the samen name should also be avoided, as this causes strange issues, like the current one.

If you don't want to change the other Start Date field, you could use advanced options to set the start date.

Use the more options setting and add, you will need to find the custom field Id of your start date field, as the one mentioned below is an example

{
   "fields": {
        "customfield_10407": "{{now}}"
                  }
}

AB November 9, 2023

Thanks for your help on this this worked to call out the specific field.

Like Marc - Devoteam likes this
0 votes
Muhammad Moazzam Hassan
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 Leaders.
November 6, 2023

Due to the same name fields, I think you are editing the field which is not associated with the issuetype, Do verify the field you are editing is added on the screen?

0 votes
Jens Schumacher - Released_so
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 6, 2023

It's hard to give advise without knowing what the schema and project configuration looks like, but all symptoms point at a problem with the field configuration. 

Take a look at this knowledge base article that might help you to debug the issue: https://confluence.atlassian.com/automationkb/automation-for-jira-reporting-unknown-fields-set-during-edit-they-may-be-unavailable-for-the-project-type-1130727699.html

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events