# Conditional Buttons to transition entities through states

**URL:** <https://community.fibery.io/t/conditional-buttons-to-transition-entities-through-states/451>\
**Category:** Get Help\
**Created:** [December 5, 2019, 6:11am UTC](https://community.fibery.io/t/conditional-buttons-to-transition-entities-through-states/451 "2019-12-05T06:11:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [December 5, 2019, 6:11am UTC](https://community.fibery.io/t/conditional-buttons-to-transition-entities-through-states/451/1 "2019-12-05T06:11:25Z")

</div>

I wasn’t sure if this is should be a question to the community about use of buttons, or a feature request, but what I wanted to talk about was using buttons as a means to easily transition through States. This is a great feature of Jira, and some other tools.

What I’d really like to see is to be able to set up workflows so that you are only allowed to move to a certain state if conditions of the current state are met, such as a field that requires a result of a software test, is filled.

Also, a button that takes an entity straight to “completed” or “closed” from somewhere in the middle of the workflow is very useful, too.

Thanks guys!

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [September 7, 2022, 8:17am UTC](https://community.fibery.io/t/conditional-buttons-to-transition-entities-through-states/451/2 "2022-09-07T08:17:02Z")

</div>

> [@Invitation to users wanting improved workflows](https://community.fibery.io/t/invitation-to-users-wanting-improved-workflows/3259):
>
> We know that the current workflow implementation is simplistic, and given that there are quite a few topics here that relate to workflows, e.g. …it seems like there are plenty users who would like more sophistication. Without making any promises, I would like to invite users to get in touch if they have specific use cases in mind that cannot currently be achieved in Fibery. This may allow us to develop templates that might be useful, as well as helping us understand what functions/features…

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [October 3, 2022, 7:14pm UTC](https://community.fibery.io/t/conditional-buttons-to-transition-entities-through-states/451/3 "2022-10-03T19:14:26Z")

</div>

Chris, just to respond to this one, the workflow I described here would be very useful to me. It’s relevant to software development. Thanks!

---

<div class="post-metadata">

**Author:** ![njyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/njyo/32/923_2.png) [@njyo](https://community.fibery.io/u/njyo)\
**Post date:** [July 17, 2023, 8:27am UTC](https://community.fibery.io/t/conditional-buttons-to-transition-entities-through-states/451/4 "2023-07-17T08:27:12Z")

</div>

+1 on the conditional buttons 🙂