Hi When app building on a large screen there’s a large space between the trigger edit buttons and the trigger title. It is difficult to tell which trigger i’m about to open with all the white space. Solution: when i hover over a trigger’s buttons the title is highlighted or emphasized so i feel confident i’m opening the right trigger.
Also if i have a page with lots of triggers i would like to be able to go to previous/next trigger with out closing the trigger editor then opening another trigger to edit (granted you haven’t made any changes to the trigger). Sometimes i need to just look through the content of the triggers quickly without making edits. See example with arrows 
1st suggestion:
Why don’t you resize your sidebar to a proper width? I simply made mine more narrow and I’m good with that.
2nd: Awesome idea. there could even be a dropdown to jump to a specific one next to that arrow buttons!
How do I only vote for the second one?
Thank you all for the great discussion.
We’re in early discovery on Trigger UX improvements, and really appreciate all the ideas and feedback. I’m flagging this thread to a few other product managers in case we have follow up questions.
Quick question from my end- it looks like many of the folks on this thread are hoping to open a previously written trigger, or even quickly jump through triggers.
What’s your primary use case - are you hoping to review previously written logic to understand what it does, or are you debugging an app step while building it?
Thank you!
- Olga
Review previously written logic. As someone who took over Tulip instance with no familiarity with the apps, I spent most of my time just looking through triggers to understand what the app did.
So just thinking of the next person down the road who inherits the platform.
2 Likes
to me it’s actually both.
I often have similar triggers (e.g. for handling inputs the same, but allowing them to be optional (seperate “if check”)).
When I have changes, I need to change these triggers the same.
So it would help to jumping from one of them to the next one, so you don’t loose track from where you are coming.
- check measurement Longitudinal
- process measurement Longitudinal
- check measurement transversal
- process measurement transversal
- check measurement cross
- process measurement cross
- …
- call connector
- …
then update the “processing” triggers would be easier with direct navigation.
But understanding the flow is also a crucial benefit!
2 Likes
This has been resolved in Release 288 - September 2024 ! Thansk @jjj for the great suggestion 
2 Likes