[Feature Request]: show full event dependency-tree

[michabbb]

Is there an existing feature request for this?

• I have searched the existing issues

What is your feature request?

I have a big problem with managing tons of events that are called by other events. Some of my events are three levels deep, and currently there is no overview at all. Because of that, debugging takes a lot of time, since I have to find out which job is called by which event. 😏

For example, if Event A calls Event B, Event B calls Event C, and so on, I currently have to click through all events to understand how the chain works.

It would be a killer feature and much more convenient if the full tree were visible on every event that is part of a chain.

So I would love to have something like this inside every event view:

The event I am currently viewing should be highlighted in the tree, so the user immediately knows where this event is located inside the chain.

That would be amazing. 😏

If you implement that, the next donation is safe 😊

Code of Conduct

• I agree to follow this project's Code of Conduct

[jhuckaby]

Well, the thing is, what you are describing here is exactly what Workflows already provide. And I mean, like, to a tee. They give you this exact view of your events, and you can connect them visually so they all chain to one another:

Also, with xyOps workflows, you don't have to "recreate" any of your events. You can use your EXISTING events as workflow nodes, and design any flow direction you want, with fan-out, fan-in, and everything.

Basically, workflows can replace the "Run Event" action for chaining events together. Just remove those actions, and then add your events into a workflow instead.

When clicking "Add Node" button, simply select "Event" instead of "Job", and you can select a pre-existing configured event from your event list to use in the workflow.

I hope this makes sense.

[michabbb]

hi, thanks for the quick feedback. i get it, okay. but to be honest, i really like the simplicity of just creating events and chaining them via "on success" 😏 but i will try the workflows 🙈 i just avoided them to keep it simple 😁 thanks !

.... but anyway.... such a dependency tree would be extremely cool in my opinion 🙃

[jhuckaby]

such a dependency tree would be extremely cool in my opinion

I'm not against doing it. I just wanted to make sure you knew about workflows, as they were designed to replace the "old way" of chaining events.

I'll keep this feature request open, and see what I can do when I have some time.

[michabbb]

don´t worry, i fully understand you! it makes sense. i know the workflow since day one i am using xyops. but to be honest, i just tried to keep it simple. but since my chains get longer and longer, i finally have to admit, that i should use them - as i said: i will try 😏 👍