I do agree it’s hard, I’d love to know though, if there was a way for you to use the tool internally. How would you envision that happening, could it be a plugin, something working side by side JIRA perhaps?
Well, for tools of this kind, they could never be hosted, it would have to be on-premise.
I think if a tool like this would ever be adopted the first thing it’d need to do is sync with Jira, so things that happen in the tool happen in Jira too, and vice versa.
I’m not too sure though, I guess I kind of feel that the inertia is just too big. Unless it can do the same things that people (not developers, business people) want to do with Jira all the time (add thousands of custom fields, do arbitrary queries on those, build lots of unuseable dashboards, tens of different issue types with different fields and tabs for each, link issues with semantic types) and do them better, Jira will never be replaced.
I guess what I’d hope for is a way I can use the app while not having to deal with Jira, but then so much of our process is based on obscure Jira features that I’m not sure it’s possible.
Aeolun|4 years ago
I think if a tool like this would ever be adopted the first thing it’d need to do is sync with Jira, so things that happen in the tool happen in Jira too, and vice versa.
I’m not too sure though, I guess I kind of feel that the inertia is just too big. Unless it can do the same things that people (not developers, business people) want to do with Jira all the time (add thousands of custom fields, do arbitrary queries on those, build lots of unuseable dashboards, tens of different issue types with different fields and tabs for each, link issues with semantic types) and do them better, Jira will never be replaced.
I guess what I’d hope for is a way I can use the app while not having to deal with Jira, but then so much of our process is based on obscure Jira features that I’m not sure it’s possible.