81–90 of 182 posts
Not sure if it's only me. But there's some funky funky things happening on that frontend. There's a white modal that covers that whole screen that pops out at every page load.
This looks great! Any plans for Gitlab integration?
Well done for getting your project out there ! I'm sure its great. I've commented on this in the past. This is what I want from my "ticketing-software": -I don't want 100 ways todo things or configure a ticketing tool... -Sell me the BEST "Software Development PROCESS" with a tool. -Don't give me a "Great Ticketing-System" ! I want to know what is the fastest, best process to develop software and track it. All of "th…
The "best" sound system is worthless if the acoustics of the room it is in aren't upto it.
Well done for getting your project out there ! I'm sure its great. I've commented on this in the past. This is what I want from my "ticketing-software": -I don't want 100 ways todo things or configure a ticketing tool... -Sell me the BEST "Software Development PROCESS" with a tool. -Don't give me a "Great Ticketing-System" ! I want to know what is the fastest, best process to develop software and track it. All of "th…
I'd absolutely love to give it a go at my company. I want an on-premise version.
JIRA sprint planning is painful. In my current company, we use it, and its shortcomings shape our way of working. I.e., not able to link histories' subtasks to a sprint, causing that the backlog is full of long histories, and you need to go looking around to see how the histories are going.
If we were able to sync epics and histories (JIRA Tara), we could probably have the better of both worlds. I see Tara very focused on devs, but not all JIRA users are devs. For instance, how would critical bugs - reported by users - be handled in Tara?
I imagine this synchronization as bidirectional, where you write the specs as a list in JIRA's issue description, but they are actionable in Tara. So no more subtasks in JIRA and Tara become a complementary tool that, once you are used to it, you can go with entirely standalone.
Just writing this quickly, with no deep thought, but it was my very first thought after checking your website.
I hope this feedback can be useful to you.
Well done for getting your project out there ! I'm sure its great. I've commented on this in the past. This is what I want from my "ticketing-software": -I don't want 100 ways todo things or configure a ticketing tool... -Sell me the BEST "Software Development PROCESS" with a tool. -Don't give me a "Great Ticketing-System" ! I want to know what is the fastest, best process to develop software and track it. All of "th…
I am working on SaaS solution in different area. We would LOVE to sell our approach to the problem but then you start getting big customers...
Guess what, each one of them wants this changed that different color, "tasks" should be named "todos" or whatever. Then everything has to have customization options because next customer contact changes mind and the other one is leaving company.
For now our sales reps do loads of configuration for those big customers, but yeah you have to have big bucks to have sales rep do config tailored for you.
But.. How can this be free?
It’s a nice looking tool, but the marketing feels oh so very Enterprise Agile(tm) in ethos. “Run your weekly sprints on time” — as opposed to them taking two weeks? To achieve predictability, something has to give. It’s usually “learning” which is never on the plan. The next release will be done when the right top priorities are met well enough. When’s that? You decide by prioritizing how many priorities are in the r…
As a manager I follow two principles that help me to prioritise tasks for a weekly sprint. First, every project has three levers: budget, timeliness, features. Choose two. So it's not about not trusting the development team. It's about understanding the tradeoffs and how the delivery date will be affected. Second, how well can you predict what you can achieve as a developer in one day vs one hundred days? The estimat…
I’m not so sure that’s true. I mean, it’s probably not worse but often I find that my gut feel of “it’ll take for weeks” is more accurate than trying to break the feature down beforehand and add up the parts. I’ve always said that the estimation process rests on the hope that if you break a big wild-ass guess into a lot of smaller wild-ass guesses, the errors will cancel out. I don’t think that’s always the case.