# Elastic Watcher: Cannot set correctly fields.assignee.name in Jira action

**URL:** <https://discuss.elastic.co/t/elastic-watcher-cannot-set-correctly-fields-assignee-name-in-jira-action/228054>\
**Category:** Elasticsearch\
**Created:** [April 15, 2020, 8:06am UTC](https://discuss.elastic.co/t/elastic-watcher-cannot-set-correctly-fields-assignee-name-in-jira-action/228054 "2020-04-15T08:06:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jack\_Phan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_phan/32/44738_2.png) [@Jack\_Phan](https://discuss.elastic.co/u/Jack_Phan)\
**Post date:** [April 15, 2020, 8:06am UTC](https://discuss.elastic.co/t/elastic-watcher-cannot-set-correctly-fields-assignee-name-in-jira-action/228054/1 "2020-04-15T08:06:42Z")

</div>

In the [document](https://www.elastic.co/guide/en/elasticsearch/reference/current/actions-jira.html) for creating Jira action, we can set the **fields.assignee.name** to assign an issue to a particular Jira user. The value I set here is the name displayed when I go to my profile in Jira.

However, after the issue is created, it is still unassigned.

I wonder whether it is a good idea to use the name since it's not likely to be an identity.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 13, 2020, 8:06am UTC](https://discuss.elastic.co/t/elastic-watcher-cannot-set-correctly-fields-assignee-name-in-jira-action/228054/2 "2020-05-13T08:06:43Z")

</div>

Closed on May 13, 2020, 8:06am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.