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. :unsure:

What you request cannot be set as is, as it is only your own use of the tool.

For issuer profile,
- description is not mandatory when creating ticket (next status = recorded)

IMO description is mandatory on creation.

- responsible should be displayed but not editable

When storing tickets for "internal" issues (when running integration tests) issuer may directly define Responsible.

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

Not IMO : the responsible may estimlate tile himself, aflter analysis, so cannot be mandatory on affectation

Actually, I made that using Simple ticket for issuers and Ticket for other users

This is exactely what Simple Ticket is designed for :woohoo:

but that's not really sexy.

🙁

=> I recorded Ticket #1353 about this request ,but not sure iot will be implemented one day.

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

This is a simplified way only if next status choise is limited to few (less than 4)

=> Ticket #1354 recorded

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

Ticket #1355 recorded

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"

This is already possible, defining correct workflow. Only display is a listbox, not buttons.
Target solution could be a mix of existing.
1 button to go next (the most used) + 1 list for other possibilities

I appreciate this idea.

Just let me chip in following:

We have an approval step, which could not be set by everyone. In this case there will be no button "go next" possible, as long the manager didn't approve.