|
|
|
|
|
|
by a_c
1723 days ago
|
|
|
I can't articulate what I find deal breaking in these tools. I would love to see more contenders to jira. From my understanding people generally hate jira for its ocean of configuration and slowness. Would love to learn more what problem jira is not solving, and would love to try more alternative. I have used github issues, basecamp, trello, among others for project management. They are all okay. At the same time definitely not miles better than jira. In my case, project management is something has to be there, doesn't matter which tool to use (given that most of okay). |
|
|
An organization has 5 weird workflow issues that they can somehow shoehorn into Jira. Trello does 4 of them better, but doesn't do the last one; Github issues does 3 of them better than Jira but does two of them in an opinionated way that differs from the company expected workflow. Etc. So, the other options are disqualified because they don't handle all the requirements and often eventually only Jira remains as an option.
Random things I've seen (not all in the same place) as a must-have requirements for a project management system:
* doing cost allocation between departments for time spent on tickets.
* doing cost allocation between departments for time spent on tickets subject to a weird set of criteria that no sane product would include out of the box.
* integration of user roles, permissions and attributes (e.g. what's being billed) from whatever is configured in company Active Directory.
* track time allocation of people in teams distributed in an organization, disqualifying any solution that won't integrate all the people in a multinational company and all the projects in which a particular person might spend their time.
* having automated CI/CD deployment be contingent on actions taken on that ticket.
* having automated CI/CD deployment be restricted to actions taken on that ticket following a very specific set of rules who can approve what and what needs to be reviewed. etc.
As you can see, these aren't really "project management" features but aspects adjacent to it, but those are things required from a project tracking system in larger companies.
In essence, it's not sufficient for a product to provide a feature in one way; the key requirement is to have a product that can have software support for your particular way of doing that business process; and a solution must fit all the boxes, because the company won't use one tool for half of the process and a different solution for other half - well, not unless the data is magically synchronized, which is a very very hard thing to do properly.