Azure DevOps

We were struggling as well, when we searched for usefull task management that would encompass task management, dev support and PM, but we did choose Azure DevOps and overall we were happy with the decision. I dont know ClickUp, but after years of experience with ADO, I would went for it. Also for high level tracking, there is a feature in ADO: https://learn.microsoft.com/en-us/azure/devops/boards/plans/review-team-plans?view=azure-devops

This is the best devops platform, period. Have you searched for extensions to fulfill this need?

If you are looking for CI, BitBucket is not the preferred solution - it has many limitations that Azure DevOps does not have. That being said, GitLab is probably a superior solution to either as it has a very sophisticated and flexible CI solution and you can even run your own CI workers if you need access to resources that aren't available on the hosted service: such as specific hardware, very long run times or licensed software.

Other than that, if you are only interested in source control, and specifically git - either will be a good offering as well as quite a few others. You do need to make sure that the software you plan to control is a good fir for git - specifically, if you are looking to store large data sets (I'm thinking BI, yes) as a source of truth, git will be a poor choice and you should look for hosting based on Subversion or Mercurial.

If you need just the source control feature, there aren't much difference. Azure DevOps has slight advantage since it has TFVC besides git. But, if you need some other features, like CI/CD, ticket/task management, etc. Well, that is completely another thing. For example, it is very easy to integrate BitBucket with JIRA. You could even combine BitBucket source control with Azure DevOps pipelines for easy CI/CD.

This is what I know:

1 - User Friendly is relative to what background you are coming from. I am not familiar with Azure. It sounds like you may be the Project Manager. I have used both Jira and Asana. I think Jira feels and looks more simple. Jira is more Project and software-dev oriented. Asana is more general, not to say it isn't designed to handle a development project. I think your decision is going to come down to: *Who is currently using what? *How is it going to be to get the individual outliers to adopt a new management style? Some will adapt and some will refuse. 2 - I believe they all have a level of automation 3 - I know Asana will let you tag and prioritize. Jira will allow you to prioritize, tag, make teams, and separate the projects by teams if you like. 4 - Again you can create teams and you can control the team visibility to projects. 5 - I know Jira will allow you to create a human resource with a burndown. 6 - Jira can assign tasks, projects, etc. to individual team members. 7 - With Jira comes Confluence. Here you can keep lots of support documentation. They have lots of templates that can be used as well. 8 - Jira does allow a lot of integration. It is designed for Product and Project management of HR and Software. If software devs didn't see a robust integration feature they would be very disappointed.

JIRA is the clear choice for you based on your use case. JIRA has been around for more than 15 years and they defintly are pioneer in this field. JIRA will perfectly match up with your use cases (data governance compliance, etc.). JIRA can be as simple or as complex as you want it to be. You can choose one of the starter templates or build a custom transition with a dedicated workflow for each. If done correctly, even though the first step takes time, it makes life much easier for everyone in the end. I don't work for JIRA just a big fan!