# Mark current step in step list

**URL:** <https://community.tulip.co/t/mark-current-step-in-step-list/5547>\
**Category:** Product Suggestions\
**Created:** [June 13, 2022, 1:03pm UTC](https://community.tulip.co/t/mark-current-step-in-step-list/5547 "2022-06-13T13:03:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Amit](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/amit/32/968_2.png) [@Amit](https://community.tulip.co/u/Amit)\
**Post date:** [June 13, 2022, 1:03pm UTC](https://community.tulip.co/t/mark-current-step-in-step-list/5547/1 "2022-06-13T13:03:19Z")

</div>

Hi,  
When you want to enter a step from step list, you mark it as following picture :  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/6/63b06ecbbf18a71f8f8a597b8155d11b584a829c.png)

If you press anywhere in the step window you get this kind of mark :  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/6/60b59a44bb4d78631bed727132054b51d088e6ea.png)

The blue square becomes gray, that’s great BUT, try to click on a button on step, marking of the step disappears and you can’t know where have you been, especially if you have a long list of steps:  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/f/f5271b40a5bb6d96053a32b2f3b30ae05ba80ee1.png)

Please consider fixing this issue, it is very annoying.

Regards,  
Amit Berku

---

<div class="post-metadata">

**Author:** ![Pete\_Hartnett](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/pete_hartnett/32/3678_2.png) [@Pete\_Hartnett](https://community.tulip.co/u/Pete_Hartnett)\
**Post date:** [June 13, 2022, 1:36pm UTC](https://community.tulip.co/t/mark-current-step-in-step-list/5547/2 "2022-06-13T13:36:22Z")

</div>

Hey @Amit -

Good call - This is absolutely a UI _miss_ with the new “widgets in step tree” feature. The engineering team is already talking about how to address this. Expect to see this resolved ASAP. r231 is already locked, but it wouldn’t surprise me if we have a fix in r232 or r233.

Pete
