3 ms·

One of my vendors uses Jira, so we have to use Jira to submit tickets for bugs on their stack/apps...and because apparently there are some config options within

by mxuribe 10y ago

One of my vendors uses Jira, so we have to use Jira to submit tickets for bugs on their stack/apps...and because apparently there are some config options within jira, its often tough to tell if the suckiness is Jira itself or how an admin has set it up. Our vendor has had to re-config things twice (and we might have to ask them to do so yet again). On the flip side, I have another vendor, and they moved to youtrack earlier this year...As a former developer youtrack just gels so well for me; everything clicks awesomely and makes sense. It may not be as pretty as Jira, but extremely powerful for search. My vendor is self-hosting a youtrack instance, and who knows there may be similar config. issues like jira, so YMMV...but have a look-see: https://www.jetbrains.com/youtrack/ https://www.jetbrains.com/youtrack/

agentgt 10y ago
We switched from Bitbucket-> Jira -> Bitbucket -> Youtrack We use Bitbucket for SCM hosting because .. yes we are still on mercurial (and yes we still love it) but mainly because Bitbucket allows unlimited repositories which is far far better for our workflow (Java + Maven). It is important to understand that we have a lot of projects each in their own repository as I still firmly believe this is the right way to do things. I guess users of github private must do the giant repository thing. Bitbuckets issue tracking was almost good enough but because as mentioned earlier we have lots of projects however business wise those projects map to a few singular products. Many SCM+issue management including Bitbucket only allow one repository. That is checkins from different repositories don't get picked up by some parent aggregation project. So Atlassian pushed us on to Jira... what an epic failure that was. The cloud hosting was so slow and was generally overly complicated. Finally we moved to youtrack. It is dorky but so awesome. It is the issue tracker for developers. Is a great product but its integration pieces are sort of buggy. For example bitbucket integration no longer works because of 2FA (reminds me I need to check if they have fixed it now). It is pretty sad because we are essentially loyal Atlassian customers (Bitbucket) and yet we were forced to moved to another product. I really wish they would just improve Bitbucket's issue tracking as I still like having the code close to the issue management.

by mxuribe 10y ago

agentgt 10y ago

We switched from Bitbucket-> Jira -> Bitbucket -> Youtrack We use Bitbucket for SCM hosting because .. yes we are still on mercurial (and yes we still love it) but mainly because Bitbucket allows unlimited repositories which is far far better for our workflow (Java + Maven). It is important to understand that we have a lot of projects each in their own repository as I still firmly believe this is the right way to do things. I guess users of github private must do the giant repository thing. Bitbuckets issue tracking was almost good enough but because as mentioned earlier we have lots of projects however business wise those projects map to a few singular products. Many SCM+issue management including Bitbucket only allow one repository. That is checkins from different repositories don't get picked up by some parent aggregation project. So Atlassian pushed us on to Jira... what an epic failure that was. The cloud hosting was so slow and was generally overly complicated. Finally we moved to youtrack. It is dorky but so awesome. It is the issue tracker for developers. Is a great product but its integration pieces are sort of buggy. For example bitbucket integration no longer works because of 2FA (reminds me I need to check if they have fixed it now). It is pretty sad because we are essentially loyal Atlassian customers (Bitbucket) and yet we were forced to moved to another product. I really wish they would just improve Bitbucket's issue tracking as I still like having the code close to the issue management.