Content
Added by Detlev Bielz almost 2 years ago
Hi there. As a relatively new user of OpenProject (since 3 months) I struggle with this issue on each and every task: Our instance of OpenProject is hosted and administrated by our data center staff for the whole university: staff, students, guests, ... . So they have set rather generalized default settings to meet possibly every imaginable need and avoid complaints. The workflow for simple tasks e. g. includes each and every existing status. As well as the workflow for work packages, features, etc.. , there is no difference between the workflows. This means for me (and every other user in my team), that we have to scroll down a loooong list of statuses on every single status change in every single task. If I would ask the admistrators of this instance, if they would define shorter workflows at least for tasks, I am quite sure that they will respond "yeah, this is YOUR need, but what if other members have different needs?". And in fact, this is not even near of being absurd, since the usage profiles in such a heterogeneous user basis can be quite different.
Hence my question: Is there any way to define individual workflows for different projects (recursively) if the defaults don't really apply? And, if not, wouldn't this be a very useful feature? ;-)
Replies (3)
Workflow in openproject defined on Project bases period. I assume they used large template to create your project.
Not a OpenProject expert by far, but OpenProject is no different than MicrosoftProject... If you create giant workflow you will be scrolling.
For a typical classic project (1) never create the tasks you do NOT need. (2) OpenProject "gear" allows you to create a view with a filter that filter may be able to hide a tasks you do not need (3) You can rename that private view "Biology Project" and mark it public. To make it available to everyone.
Honestly, It sounds like you have an issue with your administrators, that are refusing to customize your project for you and your needs. 💩 If you don't need those task for your project let's say created from some template, they should be deleting them. (they could always be recreated from another project or template)
According to the docs, workflows are always defined by the system admins. There is no option to do this for individual projects.
As Brian pointed out, this seems to be an issue with your organization or rather a mismatch between requirements and user groups. Usually an organizsation is supposed to established common criteria and standards projects have to satisfy. However, your situation seems to be more like: "Here's a ticket system for everyone to use to their liking."
Anyways, I have configured an OP instance, where I encountered a similar situation. The best thing you can do is the following:
This way no other projects are affected and you can use work packages that are more tailored to your needs. Still, you will need your admins to do that.
@Detlev Bielz
I agree with these existing replies regards your administration.
On a different note, if you don't need any interaction with the remaining university, you could easily set up you own instance; alternatively what about a second instance administrated by you but hosted on your university infrastructure?