Good to hear you guys are on the case, James. I wasn't trying to bash
JIRA itself, just the (relatively small) part of it that is 'public
facing' so to say.
There are lots of projects out there that don't have too much control.
For example, I'm just looking for a quick way to get somebody else to
Someone at Atlassian is reading this! :-)
On Sun, Jul 19, 2009 at 12:38 AM, Reinier Zwitserloot wrote:
>
> If they WERE using jira, I can imagine that users, being flabbergasted
> about how to use jira, just mailed them. I honestly believe that a
> good, solid bug tracker that is designed with a
Couldn't agree more, Peter.
As a rule, laypeople reporting bugs have excellent motivation - they
ran into a bug and the best possible thing that could happen to them
is for the bug to be fixed right there, on the spot. That's unlikely,
but finding a workaround or at least some 'closure', such as
I think one of the core features on stackoverflow.com is that they take
your second point serious. When you ask a question there, it will list a
selection of possible duplicates once you entered the subject line.
At first I thought that is too early since there is not much data to
compare. In
If they WERE using jira, I can imagine that users, being flabbergasted
about how to use jira, just mailed them. I honestly believe that a
good, solid bug tracker that is designed with a clueless end-user in
mind is a big improvement over any email solution, and will be used
properly.
Simple thing
Yeah, I wouldn't do it at work. I'm not suggesting A. And maybe
IntelliJs tracker did B anyway. They use JIRA I noticed. Maybe
people were just emailing them anyway so they put up the email form.
http://www.jetbrains.com/support/support.jsp?pr=IDEA&ask=Bug%20Report
On Jul 17, 10:33 pm, Reini
Depends on the project, and what would you suggest fixes this? As far
as I can tell, you're either suggesting:
A) Nothing, let users stew, or let them flood a mailing list or forum
or some such, or
B) Let users email it to some central repository, where someone has to
take action. This is just l
I sent a bug to intellij the other day with a simple "email form". It
turns out the bug was already identified. I guess if it wasn't they
could have escalated it to a real bug. Allowing direct public access
to a bug system would probably result in lots of duplicates and low
quality reports.
On
>
> kenai:
> No continues build integration yet (rumor is that it is planned).
It was officially announced at JavaOne. I don't think it's live yet,
but it's definitely not a rumor.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
There are plenty of choices -
http://en.wikipedia.org/wiki/Comparison_of_open_source_software_hosting_facilities
I remember people being OK with http://codehaus.org/
My personal feedback is below. Rather than a rating it is my opinion
on what is nice/bad/missing at some of these.
On Tue, Jul 14,
I agree with you --- most trackers are just crammed.
Also, as is common, telling someone to file a bug report isn't the way to go
as it requires creating an account etc. Most people simply won't do it. I
guess Trac could help in this regard, because it's supports creating issues
from emails.
20
Mark Fortner wrote:
> It's fairly simple to create a mailto form that captures a minimal
> amount of information and generates a JIRA issue.
> http://www.atlassian.com/software/jira/docs/v3.13/issue_creation_email.html
>
> I would definitely "put in an issue" with the Atlassian folks though,
> i
It's fairly simple to create a mailto form that captures a minimal amount of
information and generates a JIRA issue.
http://www.atlassian.com/software/jira/docs/v3.13/issue_creation_email.html
I would definitely "put in an issue" with the Atlassian folks though, if you
want them to have a standard
You'd be surprised at what you can do with a Greasemonkey script.
I would prefer if JIRA gave much more options of customization in the
program. We use JIRA as our
internal issue tracking tool and the end users absolutely hate interfacing
with it. It is a constant struggle
to get the end users t
Speaking of bug tracker user interfaces - what do people here think of the
direction that Jetbrains new Charisma bug tracker is taking (heavily
search/ajax based):
http://jetbrains.net/tracker/welcome
I really need to put some time aside and install a recent EAP build and give
it a good run thro
Speaking of bug tracker user interfaces - what do people here think of the
direction that Jetbrains new Charisma bug tracker is taking (heavily
search/ajax based):
http://jetbrains.net/tracker/welcome
I really need to put some time aside and install a recent EAP build and give
it a good run thro
Unless the JIRA frontpage can be skinned into something without 85,000
links and buttons, JIRA is fundamentally not going to be a good idea
if its going to be used by end-users.
On Jul 15, 6:28 am, Mark Fortner wrote:
> JIRA supports voting and can also be configured to automatically
> create is
yes - but if you look at something like "user voice" it is designed to
get rapid feedback, and perhaps some votes out of people, and not much
more. It also is very good at finding an existing issue that matches
what you are trying to describe. I guess a "front end" like that to
JIRA would be nice
JIRA supports voting and can also be configured to automatically
create issues from emails. You would need to check with your provider
to find out which features have been enabled. Atlassian also provides
a hosted service if you don't want to handle managing the server
yourself.
Hope this helps
Yeah, expose helps, but in the end this isn't something like "A
Content Management System". If people are going to find this at all,
they already know what they are looking for. I did put in some effort
to make sure the name is sufficiently unique. Or 'googlable', or
whatever the kids are calling
Its interesting how people are never really satisfied with bug
tracking, despite there being quite a market and competition.
I guess cause they are really trying to solve 2 overlapping problems:
bugs and issue tracking for project teams with some project
management, and on the other side is it a
As an open source project surely you must rate exposure to your
community as highly desirable?
My only observation is that strangely Google code does not get much
exposure via Google itself, instead projects on SF get the best
exposure. This might be because the page ranking systems rate SF long
I'm not an expert on all the features, but I was quite enjoying google
code. But the problem it seems with these types of hosted services,
is that everything is fine... until its not. You can reset your svn
repository.. but only for a while. Then you can only go forward. And
you can't delete y
Reinier Zwitserloot wrote:
> I'm looking around for online project hosting, and frankly, I'm not
> really finding the perfect solution.
>
[...]
> sourceforge: Vague sense of being from the 90s (-), Supports git (++),
> no wiki (-), not so nice homegrown issue tracker (-).
>
Not that I would
On Tue, Jul 14, 2009 at 04:13:54AM -0700, Reinier Zwitserloot wrote:
> I'm looking around for online project hosting, and frankly, I'm not
> really finding the perfect solution.
>
> NB: JIRA gets a double negative because it's utterly useless for Joe
> Schmoe who would like to file a bug. You get
25 matches
Mail list logo
