# When promoting an issue to user story, the issue should have the status updated too

**URL:** <https://community.taiga.io/t/when-promoting-an-issue-to-user-story-the-issue-should-have-the-status-updated-too/570>\
**Category:** Feature requests\
**Created:** [January 13, 2023, 12:46pm UTC](https://community.taiga.io/t/when-promoting-an-issue-to-user-story-the-issue-should-have-the-status-updated-too/570 "2023-01-13T12:46:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![achvaicer](https://avatars.discourse-cdn.com/v4/letter/a/ebca7d/32.png) [@achvaicer](https://community.taiga.io/u/achvaicer)\
**Post date:** [January 13, 2023, 12:46pm UTC](https://community.taiga.io/t/when-promoting-an-issue-to-user-story-the-issue-should-have-the-status-updated-too/570/1 "2023-01-13T12:46:33Z")

</div>

Hi,

when an issue is promoted to user story, taiga keeps both with different status, and the user have to maintain both.

I believe that issue status should change as the user story is changed too.

I probably will create an api that change the status using a webhook.  
I’d like to know how other people deal with these two entities when the issue is promoted.

---

<div class="post-metadata">

**Author:** ![tdelatorre](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/tdelatorre/32/519_2.png) [@tdelatorre](https://community.taiga.io/u/tdelatorre)\
**Post date:** [January 16, 2023, 10:59am UTC](https://community.taiga.io/t/when-promoting-an-issue-to-user-story-the-issue-should-have-the-status-updated-too/570/3 "2023-01-16T10:59:05Z")

</div>

Hi @achvaicer.

Thanks for your suggestion! We’ll keep that in mind for future features.