I am considering a Tree Nav layout on webpage for ticket approvals. What could be some alternatives?

Question

I'm trying to make a layout design for a process.
I have 3 types of users one is x , b and c.
x does some work, then b approves it, then c confirms it.
But b can disapprove and open a ticket for x on that same task and c can also do the same. It's confusing but I want to see them all in a single page which shows x did "work1" then  b approved it but c declined it but created a ticket called "work2". then x again did "work2" b approved it and then c confirmed it and the task ended.
It required some sort of a tree view according to my perspective what do you think what sort of tree view would be better?

harshikerfuffle · Answer

I think what you are trying to do is have the ticket history upfront for the team to see. Github does this really well on pull requests. Multiple people can review pull requests, leave comments etc. Different actions are signified with different symbols on the timeline. Reddit is also a good example to refer to.
Github pull request review:

Piotr Żak · Answer

So, we have 3 roles with specified permissions:

X - make work
B - confirm work or reject work(return to X)
C - verify work or reject work(return to X)

Ok, as i see it:

at the moment when role B or C rejects work, it makes no sense to create work2 (more clutter record, more logic, creating unnecessary resources, archiving old ones  etc.) but operate under work1
I used to design something similar to implementation, and with team we working on
the status (additional parameter)

You don't need a tree (surely) until you plan to list these works and then group them into level II or III scopes (it already requires a complicated backend)

enter image description here

I am considering a Tree Nav layout on webpage for ticket approvals. What could be some alternatives?

2 Answers

Add your own answers!

Ask a Question