From: Andrew Ardill <andrew.ardill@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Andreas Ericsson <ae@op5.se>,
Neal Kreitzinger <nkreitzinger@gmail.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Thomas Rast <trast@inf.ethz.ch>,
opticyclic <opticyclic@gmail.com>,
git@vger.kernel.org
Subject: Re: Why Is There No Bug Tracker And Why Are Patches Sent Instead Of Pull Requests
Date: Wed, 7 Mar 2012 19:03:17 +1100 [thread overview]
Message-ID: <CAH5451mcu=sQa8KL8ptGr5w_d-OmtzAD9B-fwtMGE0w5zELgGA@mail.gmail.com> (raw)
In-Reply-To: <7vk433eyts.fsf@alter.siamese.dyndns.org>
Just a quick status update on where the issue tracker experiment at
git-scm.atlassian.net is up to:
The basic structure of the issue tracker is set up, and is ready for
people to log bugs if they want to. So far no one seems to inclined,
but note that it is still locked down to only people who have both
registered, and been promoted to 'trusted'. I will promote everyone
who has registered so far to 'trusted' in the hope that some of them
might add bugs!
The next main step is to have conversations on the list automatically
converted into issues that can be tracked. This will be either by
forwarding selected threads to the tracker, or forwarding everything
to the tracker and managing it from there. Unfortunately, a recent
upgrade broke the (unsupported) ability to create issues from
emails[1]. This will hopefully be fixed soon, and when it is we will
be able to move this experiment to the next phase.
If anyone has any ideas they would like to test, please let me know!
Regards,
Andrew Ardill
[1] Reply from Atlassian:
Officially we do not support
(http://confluence.atlassian.com/display/AOD/Restricted+Functions+in+Atlassian+OnDemand)
issue creation from email in OnDemand. The feature request for this
functionality is located at:
https://studio.atlassian.com/browse/JST-5649
There was the ability to create issues from email if emails were sent
to jira@<instance domain> as you tried to setup, but this
functionality was not officially supported and broke in the recent
JIRA 5 upgrade (which is why you receive those errors).
I believe we are planning to fix this in an upcoming bugfix release
within the next several weeks though, so please try again later.
next prev parent reply other threads:[~2012-03-07 8:03 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 17:19 Why Is There No Bug Tracker And Why Are Patches Sent Instead Of Pull Requests opticyclic
2012-02-29 18:23 ` Brian Gernhardt
2012-02-29 18:53 ` Junio C Hamano
2012-02-29 22:53 ` Jonathan Nieder
2012-02-29 23:58 ` Andrew Ardill
2012-03-01 0:37 ` Greg Troxel
2012-03-01 0:45 ` Andrew Ardill
2012-03-01 0:50 ` Junio C Hamano
2012-03-01 1:05 ` Andrew Ardill
2012-03-01 1:05 ` Junio C Hamano
2012-03-01 1:20 ` Andrew Ardill
2012-03-01 5:16 ` Miles Bader
2012-03-01 5:40 ` Andrew Ardill
2012-03-01 16:52 ` Scott Chacon
2012-03-01 20:23 ` Junio C Hamano
2012-03-01 11:29 ` Thomas Rast
2012-03-01 11:54 ` Ævar Arnfjörð Bjarmason
2012-03-01 12:46 ` Andrew Ardill
2012-03-01 12:28 ` Andrew Ardill
2012-03-01 17:10 ` Junio C Hamano
2012-03-02 4:03 ` Neal Kreitzinger
2012-03-02 4:19 ` Jonathan Nieder
2012-03-02 4:21 ` Junio C Hamano
2012-03-02 5:50 ` Neal Kreitzinger
2012-03-02 6:25 ` Jonathan Nieder
2012-03-02 7:03 ` Junio C Hamano
2012-03-02 14:18 ` Andreas Ericsson
2012-03-02 16:45 ` Junio C Hamano
2012-03-07 8:03 ` Andrew Ardill [this message]
2012-03-07 9:52 ` Vincent van Ravesteijn
2012-03-07 13:04 ` Joern Huxhorn
2012-03-07 13:53 ` Jonathan Nieder
2012-03-07 14:47 ` Joern Huxhorn
2012-03-07 15:08 ` Pau Garcia i Quiles
2012-03-07 17:18 ` Phil Hord
2012-02-29 19:18 ` Carlos Martín Nieto
2012-02-29 21:37 ` Sitaram Chamarty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH5451mcu=sQa8KL8ptGr5w_d-OmtzAD9B-fwtMGE0w5zELgGA@mail.gmail.com' \
--to=andrew.ardill@gmail.com \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=nkreitzinger@gmail.com \
--cc=opticyclic@gmail.com \
--cc=trast@inf.ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).