I’m thinking about using JIRA Studio for our .NET development team. We’re moving from a Java background and I really liked how JIRA Studio worked for us before. But I’m not sure if it’s as good for .NET work.
Does anyone have experience with JIRA Studio in a .NET environment? I’m worried that some parts might not work well with .NET code. For example, I’m not sure if the source code viewer will handle .NET files properly.
If you’ve used JIRA Studio with .NET, what was good about it? What didn’t work so well? Are there any other tools that work better for .NET teams?
Thanks for any advice you can share!
I’ve been using JIRA Studio for our .NET projects for about a year now, and I can say it’s been a mixed bag. The issue tracking and project management features are top-notch, no complaints there. However, we’ve had some frustrations with the CI/CD pipeline integration. It took quite a bit of tweaking to get it working smoothly with our .NET build processes.
One thing I really appreciate is the code review functionality. It handles .NET files well, and it’s been a game-changer for our team’s code quality. That said, if you’re heavily invested in the Microsoft ecosystem, you might find some areas where JIRA Studio feels a bit disconnected.
Have you considered Azure DevOps? It’s more tightly integrated with .NET development tools, which could be a significant advantage depending on your team’s needs. Ultimately, JIRA Studio can work for .NET projects, but be prepared for some potential friction points along the way.
hey pete, i’ve used jira studio for .net projects and it works pretty well. the source code viewer handles .net files fine. integration with visual studio is decent too. only issue i had was some hiccups with the build server for complex .net solutions. overall, its a solid choice for .net teams
I’ve been using JIRA Studio with .NET for the past 18 months, and it’s generally suitable for our needs. The issue tracking and project management features are robust and work well regardless of the technology stack. However, we’ve encountered some challenges with the build pipeline for complex .NET solutions, particularly when dealing with multiple projects and dependencies.
One area where JIRA Studio shines is its flexibility in adapting to different workflows. We’ve customized our boards and workflows to fit our .NET development process quite effectively. The integration with Git repositories is smooth, which is crucial for version control.
That said, if your team heavily relies on Microsoft-specific tools or you need seamless Visual Studio integration, you might find JIRA Studio lacking in some aspects. In such cases, Azure DevOps or GitHub Enterprise might be worth considering as alternatives that are more tailored to the .NET ecosystem.