41–50 of 238 posts
Has anyone had a play with this and know whether it supports multiple different issue types and/or tiered issues (parent/child-level1/child-level2)?
I love seeing competition for Jira, because it needs to die, but I think you need to do a better job explaining your value prop. Your first bullet list of features doesn't really make it sound all that different. Why would I have a better time using this than Jira, bearing in mind that I'd be giving up custom workflows and probably a lot of integrations? (No shade intended. If you can answer that concisely, put that…
I haven't tried the app, but I'm almost certain you can make certain favourable comparisons of page render speed.
Earlier quoted context omitted.
It is just weird to me that using those names was perceived as a necessary step.
Native Spanish speaker that builds software for English speaking markets: I don't think I would write a software or make screenshots where I would think first to put names like Juan or Pedro in them if the target audience is English speakers. When you're writing English it just feels like the names flow better, that's all (like, avoiding stutter in a sentence, but with names). I don't think it would be fair to say we…
Also you could use "Joe" and "Pedro" instead. To me it seems even more global.
What's the tl;dr comparison with Linear?
Can you compare it with Height too?
Earlier quoted context omitted.
Native Spanish speaker that builds software for English speaking markets: I don't think I would write a software or make screenshots where I would think first to put names like Juan or Pedro in them if the target audience is English speakers. When you're writing English it just feels like the names flow better, that's all (like, avoiding stutter in a sentence, but with names). I don't think it would be fair to say we…
Why not? Also you could use "Joe" and "Pedro" instead. To me it seems even more global.
I love seeing competition for Jira, because it needs to die, but I think you need to do a better job explaining your value prop. Your first bullet list of features doesn't really make it sound all that different. Why would I have a better time using this than Jira, bearing in mind that I'd be giving up custom workflows and probably a lot of integrations? (No shade intended. If you can answer that concisely, put that…
I think when I die in ~50 years that HN will still be filled with stories ragging on Jira, or whatever it is that eventually replaces it. It's like the pastime that will never end.
To be clear, I think it's great to see open source projects like this, and I think increasing competition is a really wonderful thing. I also totally agree that Jira has lots of room for improvement, with performance probably being the most common gripe. But I always smirk a little to myself when I hear complaints that are solely from a particular point of view (usually an individual developer). Project management tools have an extremely difficult task of needing to fulfill a gargantuan range of requirements for many varied stakeholders (frontline devs, dev managers, product managers, business leads and execs, sometimes end users depending on ticketing functionality, etc.)
Some simple pieces of evidence:
1. For one, just look at the varied list of comments already coming in on this story "does it support multiple issue types or tiered issues?", "Does Plane offer all the pro features for free because we can't afford to pay anything for it?", "Does it support Google login or other identity providers?", "It needs a walkthrough video that must be short, I'm not going to look at a long video", "Is Ctrk+K a good shortcut?", "Can't add an issue on iPad", "Can it autodelete issues after 30 days of no changes?"... Point being, for any project management tool, you're going to basically get feature requests as varied as the number of comments, and I think I see this more frequently with project management tools than almost any other type of software.
2. Think about the legions of Jira competitors that have popped up: Asana, Basecamp, Monday.com, Linear, Rally, YouTrack, ClickUp, Trello (obv. under Atlassian now, but can't count the number of times I've heard "We loved Trello because it was simple and easy to get started, but we eventually outgrew it and needed additional features."), etc. etc. I have yet to ever hear one of those competitors being universally loved. On the contrary, I've seen cases where a competitor is touted as "the next big thing", and then when it gets more popular people talk about how much they hate it (Asana comes to mind in that regard).
In general, I don't think the problem is the tool, I think that most people just don't like to do ticket management, so it's all a case of looking for the "least bad" tool out there.
I love seeing competition for Jira, because it needs to die, but I think you need to do a better job explaining your value prop. Your first bullet list of features doesn't really make it sound all that different. Why would I have a better time using this than Jira, bearing in mind that I'd be giving up custom workflows and probably a lot of integrations? (No shade intended. If you can answer that concisely, put that…
Walk through video please. For people on mobile checking it out it’s more convenient to watch a short video. Serious about short, I’m not going to start a half hour long video while browsing. Also subtitles.
PRs would probably be welcomed.
Has anyone had a play with this and know whether it supports multiple different issue types and/or tiered issues (parent/child-level1/child-level2)?
Hey, we do have a feature of nested issues as part of Plane. You can go n-levels. You can have different type of issues via labelling.
I think labelling would get us out of the woods. Schema would be preferable, but there’s no reason why labeling won’t work.
I plan to give it a go at our consultancy next week, thanks