--
You received this message because you are subscribed to the Google Groups "Scala IDE Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-dev/CAOwe9fZMnwHPYF4XVpRYgvXB2D_Lsrjjb9ksSau9%2BG0jj5gCWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Hi everyone,
Assembla was never really easy to use, but it seems it's getting increasingly confusing for occasional bug reporters. For example, it is very unclear for a new user that it can create a free account, and even once you have the account, permissions may subtly prevent new tickets or comments. The UI is also sluggish and unintuitive.
Is it time to move off Assembla to something better?
My suggestions:
1. JIRA
I know Jira is pretty good and they have an open-source program, so we'd probably get a free account. I used it on Apache projects and I like it. It has all the features you could wish for, relatively good UI. No good support for Markdown, but I think there's an additional plugin.
2. GitHub Issues
It is getting better, though it is very unstructured. Labels are cool, but I can't see them as good enough when it comes to required fields, like Eclipse version or product version. We could ditch all fields and ask the OP when we need more info, but it will make it hard to know what tickets are still valid. I'm also not sure how well it will cope with several thousand tickets. And only committers can assign labels. :-/ On the plus side, everything is on GitHub now, so it's familiar and centralized.
There's still the issue of importing existing tickets, but I imagine there's a solution with either system.
Any thoughts?
iulian--
« Je déteste la montagne, ça cache le paysage »
Alphonse Allais
On 10/22/2015 10:05 AM, iulian dragos wrote:
I don't think there really exists a better alternative. Beside from that it seems to be the exception that users don't find out how to create a ticket. There are a lot of names on the first page of newest tickets. And just one person in the last weeks who complained that they didn't find out how to open a ticket. Github would be the only issue tracker that could make user entry easier because everyone already has a Github account.Hi everyone,
Assembla was never really easy to use, but it seems it's getting increasingly confusing for occasional bug reporters. For example, it is very unclear for a new user that it can create a free account, and even once you have the account, permissions may subtly prevent new tickets or comments. The UI is also sluggish and unintuitive.
Is it time to move off Assembla to something better?
The amount of work that is necessary to setup JIRA and the time to learn it (at least for me) is not worth it imho. And users still have to create an account, don't they?My suggestions:
1. JIRA
I know Jira is pretty good and they have an open-source program, so we'd probably get a free account. I used it on Apache projects and I like it. It has all the features you could wish for, relatively good UI. No good support for Markdown, but I think there's an additional plugin.
These are also my thoughts. We just would loose features by moving to Github.
2. GitHub Issues
It is getting better, though it is very unstructured. Labels are cool, but I can't see them as good enough when it comes to required fields, like Eclipse version or product version. We could ditch all fields and ask the OP when we need more info, but it will make it hard to know what tickets are still valid. I'm also not sure how well it will cope with several thousand tickets. And only committers can assign labels. :-/ On the plus side, everything is on GitHub now, so it's familiar and centralized.
We would loose history for sure and internal references like referenced tickets, which is a big loss.
There's still the issue of importing existing tickets, but I imagine there's a solution with either system.
iulian
--
You received this message because you are subscribed to the Google Groups "Scala IDE Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-dev/CAOwe9fYFPxLodn4g0otCfR738sFz0R-3p1g4S99ptF0GtDYNeg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-dev/562A09DE.7080301%40antoras.de.
I don't think any of those have custom fields, or relationships between issues
--
You received this message because you are subscribed to the Google Groups "Scala IDE Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scala-ide-dev/fca656bf-1355-4333-bfbe-a97a96be779a%40googlegroups.com.