I have set up an automation in JIRA that works as follows: * WHEN: Issue transitions from (in progress, resolved, reopened and/or opened) to (closed). * IF: Issue type is one of (task, sub-task, story and/or bug) * THEN: Edit issue field (Custom field date picker) using the following smart value: {{now.jiraDate}} When I tested the automation, the custom field wasn't modified. When consulting the audit log, it shows that the issue met the conditions (so steps 1 and 2 are properly programmed) but when performing the edit action (step 3), no edit was made. JIRA suggests 2 possible reasons: * No fields or field values to edit for issues (could be due to some field values not existing in a given project) - not the case, as I already checked the custom field is included within the screens of the project. * Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration - neither the case, as this custom field is configured to be available for all projects in our instance. At this point I'm stuck and I don't know how to proceed - any ideas? Thanks a lot in advance!

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; } } }

JIRA Automation: Problem with Custom Field (Date Picker) that is being ignored

Gonzalo Perez Alonso_mpxmys

I have set up an automation in JIRA that works as follows:

WHEN: Issue transitions from (in progress, resolved, reopened and/or opened) to (closed).
IF: Issue type is one of (task, sub-task, story and/or bug)
THEN: Edit issue field (Custom field date picker) using the following smart value: {{now.jiraDate}}

When I tested the automation, the custom field wasn't modified. When consulting the audit log, it shows that the issue met the conditions (so steps 1 and 2 are properly programmed) but when performing the edit action (step 3), no edit was made. JIRA suggests 2 possible reasons:

No fields or field values to edit for issues (could be due to some field values not existing in a given project) - not the case, as I already checked the custom field is included within the screens of the project.
Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration - neither the case, as this custom field is configured to be available for all projects in our instance.

At this point I'm stuck and I don't know how to proceed - any ideas? Thanks a lot in advance!

Accepted answers

Tim Kopperud

Hi @Gonzalo Perez Alonso, welcome to Atlassian Coomunity, nice to see you here.

I'm not able to reproduce this problem, as you see here.

The rule

The result in history log

As you see by the yellow markings the My date field was not visibly updated during the rule execution itself (first yellow marking), but it shows changed in the issue itself (second yellow marking).

Just so I understand the exact problem for further investigation. Is the variance mentioned above (rule update ves history update) related to your problem, or is it that the field isn't even updated in the issue history?

It might be helpfull if you are able to attach images of the rule and of the issue history (like in my example above).

TimK.

All comments

Tim Kopperud

Hi @Gonzalo Perez Alonso, welcome to Atlassian Coomunity, nice to see you here.

I'm not able to reproduce this problem, as you see here.

The rule

The result in history log

It might be helpfull if you are able to attach images of the rule and of the issue history (like in my example above).

TimK.

Gonzalo Perez Alonso_mpxmys

Hi @Tim Kopperud

Thanks for the quick response. The main problem I'm facing is that my custom field (E2E Close Date) is not being edited as I want to.

Please find attached screenshots both for the automation and the audit log.

Tim Kopperud

Hi @Gonzalo Perez Alonso

Do you see the field E2E - Close Date on the issue BET-9 itself? Are you able to set the field manually from that issue?

Though a field doesn't actually need to be included in any screens to be set, lack of seeing the field can be an indication of a context problem. Try check your custom field context

Press the Cog icon (upper right corner) and select -> Issues -> Custom fields
Find the field E2E - Close Date
Press the Ellipsis menu to the right and select Context and default value

Confirm that the project BET and the issue types Tasks, Story, Bug and Sub-tasks are included in the applicable context.

If it states Global (all issues) the project BET and the issues types are included (global context is not reccomended though so it might be a narrower scope in your setup).

The image below shows an example of the global context configuration.

You might attach an image of your context configuration if you're uncertain.

TimK.

Gonzalo Perez Alonso_mpxmys

Hi again,

Thanks for the clarifications but I had already checked that. I even run the "where is my field" diagnosis and everything seems correct (see the screenshot below)

Also, the field is being shown on the test issue. The problem is that the automation is not being done, as it doesn't get updated when I transition to Close status.