0

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 aproves it then c confirms it. But b can disaprove and open a ticket for x to do on that same task and c can do the same. Its confusing but I want to see them all in a single page about 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?

  • I can't really picture how you would use a tree view to solve this problem so you might need to elaborate. I would take a look at other ticketing systems like Jira -- they don't typically display history information right up front. It's usually enough to know the current status and assignee of the ticket and if you wanted to know the history, you could go into the ticket's details. – Justin Oct 25 at 18:39
  • Can the same task be over and over go A B C or just once ? Is this useful information ? I'm thinking showimg the last 1 or changes with a dropdown to see the history. But depends. – Cristian Negraia Oct 25 at 18:50
  • yes its a task but the task can have many cases.. x submits saying the task is done but b finds a new problem or a case in that task so b creates a case on that task elaborating what the problem is then x submits fixing that thing then b accepts then c.. @Justin yes i need this information.. clients wants it bad – Sunita Shrestha Oct 25 at 20:23
0

So, we have 3 roles with specified permissions:

  1. X - make work
  2. B - confirm work or reject work(return to X)
  3. 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

enter image description here

enter image description here

enter image description here enter image description here

  • yes you got it but one think was off. Before B and c rejects or accepts. They need to make a comment about it. so i wanted to show that comment as well. You have helped me to some extend thanks can you provide a ui design just a structure if you have an idea. thank you sir – Sunita Shrestha Oct 26 at 14:43
  • ok, if You provide me with a screen with the system, I will try to provide a quick sketch for tomorrow evening :) – Piotr Żak Oct 26 at 15:08
  • how can i provide a screen i dont get it – Sunita Shrestha Oct 26 at 15:11
  • This layout is something new? or You need to add this to existing system? – Piotr Żak Oct 26 at 15:39
  • its new. i just need a page where I show it. – Sunita Shrestha Oct 26 at 15:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.