Content
View differences
Updated by Wieland Lindenthal 7 days ago
###
### User story
###
**As a** project manager or administrator
**I want to** define and customize work package workflows using a visual, drag-and-drop interface
**So that** I can easily model my team's processes without technical knowledge and ensure issues follow the correct lifecycle.
###
###
###
### Pain point
Multiple users contacted us with bug reports/feature requests/questions, because they did not use the workflows correctly. Some even did not know, that they are changeable at all.
The page itself is completely outdated and not intuitive. I'll list here some of the problems:
* The checkbox in the filter section is ignored by most of the users. They then wonder why they don't see all statuses.
* To setup a whole workflow takes a lot of time, as you have to define it for each pair of role and type.
* The table is really messy as it
* you need to be an OP expert to understand what it is supposed to do
* gets super long/wide very quick and you have to scroll or zoom out to reach all statuses
* Opening two additional sections does not help to keep the page clean and intuitive.
* Nobody (even I myself) understands at the first glance, that the additional workflows do not override the ones defined before but only extend it. Thus I can define workflows for authors, which cannot be saved as the default area says something else. Have a look at #33456
### Solution
* I would recommend to rebuild the whole page from scratch based on angular.
* However, the concrete details need to be determined.
### User story
###
**As a** project manager or administrator
**I want to** define and customize work package workflows using a visual, drag-and-drop interface
**So that** I can easily model my team's processes without technical knowledge and ensure issues follow the correct lifecycle.
###
###
###
### Pain point
Multiple users contacted us with bug reports/feature requests/questions, because they did not use the workflows correctly. Some even did not know, that they are changeable at all.
The page itself is completely outdated and not intuitive. I'll list here some of the problems:
* The checkbox in the filter section is ignored by most of the users. They then wonder why they don't see all statuses.
* To setup a whole workflow takes a lot of time, as you have to define it for each pair of role and type.
* The table is really messy as it
* you need to be an OP expert to understand what it is supposed to do
* gets super long/wide very quick and you have to scroll or zoom out to reach all statuses
* Opening two additional sections does not help to keep the page clean and intuitive.
* Nobody (even I myself) understands at the first glance, that the additional workflows do not override the ones defined before but only extend it. Thus I can define workflows for authors, which cannot be saved as the default area says something else. Have a look at #33456
### Solution
* I would recommend to rebuild the whole page from scratch based on angular.
* However, the concrete details need to be determined.