| It doesn't have to be this way. Most PM tools are designed to have a somehow central enforcement of the process and workflow with some central admins that have ways to change that (permissions, fields, workflows & all). This cannot be anything but a failure if the central admin doesn't say NO to 99% of modification requests because there will always be this influential project manager that will come to "add this little field I need to track this stuff for $IMPORTANT_CUSTOMER". So, by design, it will either be bloated (everyone get it's change so bug template is fat) or useless because the form will be so simple that everything will need to be managed with text content in comments. That's why we (Tuleap team) propose an alternative:
- You want a simple -github like- issue tracker because you are 3 in your team and just a title and a description, please go ahead.
- You want a full blown, CMMI Level 5, Spice 3, what not issue, requirement, risk tracker, please let the craziest process guy do. What's the difference with Jira (and others) ? Each "tracker" (issue definition) is local to one project (of course you can template for re-use) and 100% owned by the project. You are not limited to 3 or 4 central templates that nobody can modify, you own them. Let say the "simple" team is mad of tracking which component of the application an issue is raised on or how much effort was need to complete the issue, in 30 seconds the template is modified and usable without impacting anyone else. See https://www.tuleap.org/how-easy-it-customize-my-project-trac... |