Extend worklow capability

Hello babynus,

In order to enhance workflow ProjeQtor's capabilities, I think it should be interesting to be able to have different display/usage dependant on user profile and workflow status.

I giving an example on ticket page :

For issuer profile,
- estimated time should never be displayed,
- description is not mandatory when creating ticket (next status = recorded)
- responsible should be displayed but not editable
- ...

For manager,
- estimated time and responsible are mandatory when affecting ticket
- ...

For every one, real time should not be displayed since ticket is not in progress

Actually, I made that using Simple ticket for issuers and Ticket for other users but that's not really sexy.

There are several uses that might be imagined with ProjeQtor with a more flexible workflow mecanism (the current version is already correct )

Other ideas

- Next status should not be a listbox but action buttons which will be display depending user profile (like today)

- A workflow button could be open a graph presenting current workflow and actual status (where I come from ? what will be next ?).

At your disposal if you would like to discuss in more detail

Best regards,

Lionel

lfrugere wrote: Other ideas

- Next status should not be a listbox but action buttons which will be display depending user profile (like today)

I tend to like this one, but I'm not sure about practical use: sometimes you need to "bypass" intermediate status, or you can e.g. "disapprove" either by rejecting OR canceling definitely (so you'd have two ways of saying "NO", but would have to choose only ONE of them.)
On the other hand, I like the idea of pre-defining what every user profile can do, and present only a two buttons' GUI: "go back" and "go on"

- A workflow button could be open a graph presenting current workflow and actual status (where I come from ? what will be next ?).

Nice! If it's technically "achievable" (possible AND not a very big amount of work), I think this could prove useful. Even better: to be able to show a short description of what the status means, what's supposed to have been achieved on certain status. Mainly for clients, who may not interact with the software a lot.

---

The rest of the proposal seems interesting (at least for us, the users... don't know if so much for Babynus )

Basically means more fine-granular approach on display / edit of fields, based on workflow definitions. This would be really nice (would be quite some work to configure entire portal's workflow, though... but once this gets achieved, it'd be very powerful) but I pressume it's a great amount of work from development perspective.