issue tracking reorganisation proposal

Most of these things are symptoms, home remedies attempted by a grievously sick patient, arms and legs windmilling around spastically.  The real problems in my illustrious opinion are:

 - there's way more work than there are people to do it  - the bug tracker is made of excrement
Then these two problems combine to spawn a new problem: the guy who has historically done the majority of the work has become heavily disinclined to do it - not because there's a lot of it, he doesn't mind that - but because he knows it's going to be largely wasted, and because just looking at jira puts him in a bad mood.
If there is energy to reorganize, then I suggest that energy be channeled into moving off jira.
On Wed, Feb 15, 2012 at 2:19 AM, Adriaan Moors <adriaan.moors@epfl.ch> wrote:

Hi,
I'd like to propose a few changes to how we organize our issue tracking.

• use components rather than virtual assignees to categorize bugs
• we should be able change who is responsible independently from what part of the project the issue belongs to
• an issue can belong to multiple components, yet only one assignee
• similarly, leave unassigned issues "unassigned" -- don't use virtual users (scala meeting and scala reviewer: I'm looking at you)
• issues start in state Open, unassigned -- reviewer assigns ASAP
• scala meeting discusses unassigned Open issues (for those issues the reviewer can't decide unilaterally who to assign to; there should be few of those)
• assignee changes issue's state from Open to Accepted (can we impose a deadline for this?), then to In Progress and finally to Resolved
• maybe Accepted and In Progress can be collapsed (we don't currently have Accepted, but it would be good to track time spent actually working on issues)
• suggestions should not be in a separate project -- that's what "issue type" is for (it's called "Suggestion", though not currently available in the issue type scheme)
• by having them in a separate project, we can't categorize them using the main project's components

thoughts? experiences?
cheers adriaan

On Wednesday, 15. February 2012 at 15:43, Paul Phillips wrote:

If there is energy to reorganize, then I suggest that energy be channeled into moving off jira.

Not considering any issues related to migration, which is the bug tracker that you wouldpick today for the Scala project?

On Wed, Feb 15, 2012 at 7:02 AM, Lukas Rytz <lukas.rytz@epfl.ch> wrote:

Not considering any issues related to migration, which is the bug tracker that you wouldpick today for the Scala project?

If there was a gun to my head and I had to pick something immediately, I would try RedMine.  If I was able to imagine gambling on something which has a few jira-like warning signs, it would be YouTrack.
However I know next to nothing about these systems nor do I have a remotely comprehensive understanding of the available alternatives.  What I can say with confidence is that even trac, as sucky as it was, was way better than the current situation.  I don't spend any time looking into this because I figured the only person likely to do the work to move out of jira was me, and I wasn't going to do it, so it would be a waste of time.  If I believed there would be some tangible benefit to my having a better informed opinion, I would be willing to cultivate one.

On Wed, Feb 15, 2012 at 4:13 PM, Paul Phillips wrote:
>
>
> On Wed, Feb 15, 2012 at 7:02 AM, Lukas Rytz wrote:
>>
>> Not considering any issues related to migration, which is the bug tracker
>> that you would
>> pick today for the Scala project?
>
>
> If there was a gun to my head and I had to pick something immediately, I
> would try RedMine.  If I was able to imagine gambling on something which has
> a few jira-like warning signs, it would be YouTrack.
>
> However I know next to nothing about these systems nor do I have a remotely
> comprehensive understanding of the available alternatives.  What I can say
> with confidence is that even trac, as sucky as it was, was way better than
> the current situation.  I don't spend any time looking into this because I
> figured the only person likely to do the work to move out of jira was me,
> and I wasn't going to do it, so it would be a waste of time.  If I believed
> there would be some tangible benefit to my having a better informed opinion,
> I would be willing to cultivate one.
>

The only other tracker I know well from the Scala-IDE is Assembla. It
has its won set of warts but I tend to prefer it over JIRA.

Cheers

On 15/02/2012 16:13, Paul Phillips wrote:

CAEaELhSgffm8+cxw+7i5_MSXvh+iich+GxNcdbWDO6zkCLiuiw [at] mail [dot] gmail [dot] com" type="cite">

On Wed, Feb 15, 2012 at 7:02 AM, Lukas Rytz <lukas [dot] rytz [at] epfl [dot] ch" rel="nofollow">lukas.rytz@epfl.ch> wrote:

Not considering any issues related to migration, which is the bug tracker that you would pick today for the Scala project?

If there was a gun to my head and I had to pick something immediately, I would try RedMine.  If I was able to imagine gambling on something which has a few jira-like warning signs, it would be YouTrack.
However I know next to nothing about these systems nor do I have a remotely comprehensive understanding of the available alternatives.  What I can say with confidence is that even trac, as sucky as it was, was way better than the current situation.  I don't spend any time looking into this because I figured the only person likely to do the work to move out of jira was me, and I wasn't going to do it, so it would be a waste of time.  If I believed there would be some tangible benefit to my having a better informed opinion, I would be willing to cultivate one.

For our (very little open-source project, with very little contributors), we use Redmine. It's more or less satisfying for us. It's integration with Github is ok, workflow for bugs rather configurable and hookable, notifications are ok for me, and for my personal tastes, it's the best bugtracker I used.

But I only used Jira (never get it, it feels and behave totally alien to me, and I *do* understand Paul feeling about it), mantis (no comment), bugzilla (well, ugly but it did its job), track (was an improvement over the others), and redmine. I was a little exposed to Assembla as a bug reporter only, and so I have no real opinion safe that it does not feel completly right to have a bugtracker in Saas. We quickly looked to the redmine fork, https://www.chiliproject.org/, but it was just when the fork happened, and we chose to let some time pass to see how it will evolves. Today, it seems interesting.


That said, Redmine is a RoR program in all its beauty, and so a sysadmin nightmare - or at least, I hear our sysadmins grumbling about it quite often.
In the end, it works ok most of the time (even better since they chose to simply don't try to understand why it leaks, and simply kill it regularly).

Our project is here, if you want to see it in action:
https://github.com/normation/
http://www.rudder-project.org/
The actual redmine:
http://www.rudder-project.org/redmine/projects/rudder/issues

Our next steps will be to see how gerrit of the such a tools can be added in the stack.

Of course, all of that is only relevant for our use case, and YMMV.

Cheers,

-- 
Francois ARMAND
http://fanf42.blogspot.com
http://www.normation.com

On Wed, Feb 15, 2012 at 4:13 PM, Paul Phillips <paulp@improving.org> wrote:

What I can say with confidence is that even trac, as sucky as it was, was way better than the current situation.

I'm willing to invest some time to remedy this.
What is it exactly that grinds your gears?
We should have a clear idea of what we're (not) looking for when moving to a new system (if we can't fix JIRA).
In any case, your involvement need not go beyond detailing your wish list.

If there was a gun to my head and I had to pick something immediately, I would try RedMine.  If I was able to imagine gambling on something which has a few jira-like warning signs, it would be YouTrack.

youtrack looks better to me. pretty good i would say.
redmine seems to lack keyboard shortcuts and advanced search features.fanf says it's hard to admin. youtrack is easy to install and upgrade, at least.
both seem to have an ok rest api that would allow to script stuff - batch operations after import - actions from commit messages
importing from jira looks easy on youtrack, hackisher on redmine.

However I know next to nothing about these systems nor do I have a remotely comprehensive understanding of the available alternatives.  What I can say with confidence is that even trac, as sucky as it was, was way better than the current situation.

if we want to consider options we need to have some spec sheet of required functionality.

 I don't spend any time looking into this because I figured the only person likely to do the work to move out of jira was me,

i can help if there's consensus that we should move, and where to.

and I wasn't going to do it, so it would be a waste of time.  If I believed there would be some tangible benefit to my having a better informed opinion, I would be willing to cultivate one.

In any case, your involvement need not go beyond detailing your wish list.

don't know if this is anywhere close to paul's wish list:https://issues.scala-lang.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+INF+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide

On Wed, Feb 15, 2012 at 5:04 PM, Lukas Rytz <lukas.rytz@epfl.ch> wrote:

redmine seems to lack keyboard shortcuts

https://github.com/netaustin/redmine_keyboard_shortcuts

On 15/02/2012 17:06, Adriaan Moors wrote:
>
>
> On Wed, Feb 15, 2012 at 5:04 PM, Lukas Rytz > wrote:
>
> redmine seems to lack keyboard shortcuts
>
> https://github.com/netaustin/redmine_keyboard_shortcuts

I must admit I am enjoying this thread a lot.
Can I gloat a little bit? :)
Toni

PS: I tried to promote Redmine over Jira when we did the migration, but
the flashy interface of Jira won the vote at the time.

PS2: Still willing to administer a Redmine server, if needed.

On Wed, Feb 15, 2012 at 5:25 PM, Antonio Cunei <antonio.cunei@epfl.ch> wrote:

PS: I tried to promote Redmine over Jira when we did the migration, but the flashy interface of Jira won the vote at the time.

so what are the key benefits of redmine over JIRA in your opinion?

On 15/02/2012 18:21, Adriaan Moors wrote:
>
>
> On Wed, Feb 15, 2012 at 5:25 PM, Antonio Cunei > wrote:
>
> PS: I tried to promote Redmine over Jira when we did the migration,
> but the flashy interface of Jira won the vote at the time.
>
> so what are the key benefits of redmine over JIRA in your opinion?

This sounds like it may be the beginning of a lengthy argument, and I
don't think I necessarily want to be caught into it. Not again, at
least: we already discussed pros and cons extensively in the past. For a
pre-baked flamewar on Redmine vs JIRA you can check, for instance:

http://www.redmine.org/boards/1/topics/18986?r=23588

Suffice to say that, at the time, I found the interface of Redmine
rather simpler to use, according to my own taste. The fact that it is
open source makes it also easier to apply customizations or fix issues,
should that be necessary.

The point is that Paul seems to have formed a rather negative opinion of
JIRA, after using it quite extensively; although at this time I have
really no reasons to promote one or the other, I am nonetheless willing
to offer some help with Redmine if the discussion, in the end, happens
to be in favor of that particular tool. But, again, Paul is the main
user and it should be his decision in the end, after evaluating pros and
cons of the available systems out there.
Toni

On Wed, Feb 15, 2012 at 8:16 AM, Lukas Rytz <lukas.rytz@epfl.ch> wrote:

don't know if this is anywhere close to paul's wish list:https://issues.scala-lang.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+INF+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide

That is more of a list of grievances against jira than a wish list.
OK, I guess I have to attempt to articulate what I want.
Let me use some motivating examples taken from real life.  The degree to which tickets are linked to relevant commits is all over the place:
 - pre-JIRA tickets are linked to nothing, markup lost in move.  - for a sliver of time before we moved to git, new svn references were linked  - git hashes / tags / describes go nowhere
If I could call "every line in database".map(myFunction) I could fix this, in very large part if not for every imaginable corner case, in about ten minutes.  The same goes for the $ -> $$ mangling and whatever additional breakage I'm blocking out.  The cost imposed by these things, day in and day out, is not small.  I am sure if I arrange for the right kind of local access and figure out how to modify the database and etc. it is technically possible to do this.  However the fact that INF-65, INF-66, etc are still open is more than sufficient evidence that it's not within a large constant factor of easy enough.
So what I want more than anything is the ability to fix things that are broken without having to take a course and correspond with a bunch of different people to get my hands on all the administration idiosyncrasies and installation-specific knowledge.
The script which used to respond to commit messages has been broken since we moved to git.  It's performing the most basic tasks I can imagine of an API - adding a comment and closing a ticket.  This should-be-one-line rest query has apparently been overcomplicated to the point that nobody is going to touch it.  So here I am manually closing tickets and cut/pasting git hashes into them, although god knows why I'm doing this given that they don't link to anything.
tl;dr: It must be easily programmable, as in REST.  Data must be represented in a form which can be globally manipulated without special tools and local access.
Or: it is 100x more important what *I* can do than what *IT* can do.  Most of what it CAN do it either won't do or I'll wish like hell it wouldn't.
I haven't even started on requirements for something else, I'm only painting the picture a little.

so we need a JIRA manipulation DSL
sounds like a fun project -- also does not sound like something readily offered by redmine, say
Also, I saw there were some JavaScript efforts to turn rXXXX and commit hashes into links, this is definitely something we should finish. It doesn't sound too hard, either.
I think as long as we can reasonably hope to engineer our way out of these limitations,we should spend the time on fixing JIRA rather than moving yet again (not that I am strictly against moving; I do consider it a variation on NIH)

On Wed, Feb 15, 2012 at 7:02 PM, Paul Phillips <paulp@improving.org> wrote:

On Wed, Feb 15, 2012 at 8:16 AM, Lukas Rytz <lukas.rytz@epfl.ch> wrote:

don't know if this is anywhere close to paul's wish list:https://issues.scala-lang.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+INF+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide

That is more of a list of grievances against jira than a wish list.
OK, I guess I have to attempt to articulate what I want.
Let me use some motivating examples taken from real life.  The degree to which tickets are linked to relevant commits is all over the place:
 - pre-JIRA tickets are linked to nothing, markup lost in move.  - for a sliver of time before we moved to git, new svn references were linked  - git hashes / tags / describes go nowhere
If I could call "every line in database".map(myFunction) I could fix this, in very large part if not for every imaginable corner case, in about ten minutes.  The same goes for the $ -> $$ mangling and whatever additional breakage I'm blocking out.  The cost imposed by these things, day in and day out, is not small.  I am sure if I arrange for the right kind of local access and figure out how to modify the database and etc. it is technically possible to do this.  However the fact that INF-65, INF-66, etc are still open is more than sufficient evidence that it's not within a large constant factor of easy enough.
So what I want more than anything is the ability to fix things that are broken without having to take a course and correspond with a bunch of different people to get my hands on all the administration idiosyncrasies and installation-specific knowledge.
The script which used to respond to commit messages has been broken since we moved to git.  It's performing the most basic tasks I can imagine of an API - adding a comment and closing a ticket.  This should-be-one-line rest query has apparently been overcomplicated to the point that nobody is going to touch it.  So here I am manually closing tickets and cut/pasting git hashes into them, although god knows why I'm doing this given that they don't link to anything.
tl;dr: It must be easily programmable, as in REST.  Data must be represented in a form which can be globally manipulated without special tools and local access.
Or: it is 100x more important what *I* can do than what *IT* can do.  Most of what it CAN do it either won't do or I'll wish like hell it wouldn't.
I haven't even started on requirements for something else, I'm only painting the picture a little.

I'm not sure if this was already discussed, but JIRA does have an
exposed REST API.

Scala's JIRA has the REST endpoint:

https://issues.scala-lang.org/rest/api/2.0.alpha1/

and some basic documentation is here:

http://docs.atlassian.com/jira/REST/latest/

As a member of the peanut gallery, I'll take a look and see if the
script that used to respond to commits could be fixed to use the REST
API.

--j

On Wed, Feb 15, 2012 at 1:19 PM, Adriaan Moors wrote:
> so we need a JIRA manipulation DSL
>
> sounds like a fun project -- also does not sound like something readily
> offered by redmine, say
>
> Also, I saw there were some JavaScript efforts to turn rXXXX and commit
> hashes into links,
> this is definitely something we should finish. It doesn't sound too hard,
> either.
>
> I think as long as we can reasonably hope to engineer our way out of these
> limitations,
> we should spend the time on fixing JIRA rather than moving yet again
> (not that I am strictly against moving; I do consider it a variation on NIH)
>
>
> On Wed, Feb 15, 2012 at 7:02 PM, Paul Phillips wrote:
>>
>>
>>
>> On Wed, Feb 15, 2012 at 8:16 AM, Lukas Rytz wrote:
>>>
>>> don't know if this is anywhere close to paul's wish list:
>>>
>>> https://issues.scala-lang.org/secure/IssueNavigator.jspa?reset=true&jqlQ...
>>>
>>
>> That is more of a list of grievances against jira than a wish list.
>>
>> OK, I guess I have to attempt to articulate what I want.
>>
>> Let me use some motivating examples taken from real life.  The degree to
>> which tickets are linked to relevant commits is all over the place:
>>
>>  - pre-JIRA tickets are linked to nothing, markup lost in move.
>>  - for a sliver of time before we moved to git, new svn references were
>> linked
>>  - git hashes / tags / describes go nowhere
>>
>> If I could call "every line in database".map(myFunction) I could fix this,
>> in very large part if not for every imaginable corner case, in about ten
>> minutes.  The same goes for the $ -> $$ mangling and whatever additional
>> breakage I'm blocking out.  The cost imposed by these things, day in and day
>> out, is not small.  I am sure if I arrange for the right kind of local
>> access and figure out how to modify the database and etc. it is technically
>> possible to do this.  However the fact that INF-65, INF-66, etc are still
>> open is more than sufficient evidence that it's not within a large constant
>> factor of easy enough.
>>
>> So what I want more than anything is the ability to fix things that are
>> broken without having to take a course and correspond with a bunch of
>> different people to get my hands on all the administration idiosyncrasies
>> and installation-specific knowledge.
>>
>> The script which used to respond to commit messages has been broken since
>> we moved to git.  It's performing the most basic tasks I can imagine of an
>> API - adding a comment and closing a ticket.  This should-be-one-line rest
>> query has apparently been overcomplicated to the point that nobody is going
>> to touch it.  So here I am manually closing tickets and cut/pasting git
>> hashes into them, although god knows why I'm doing this given that they
>> don't link to anything.
>>
>> tl;dr: It must be easily programmable, as in REST.  Data must be
>> represented in a form which can be globally manipulated without special
>> tools and local access.
>>
>> Or: it is 100x more important what *I* can do than what *IT* can do.  Most
>> of what it CAN do it either won't do or I'll wish like hell it wouldn't.
>>
>> I haven't even started on requirements for something else, I'm only
>> painting the picture a little.
>>
>

On Wed, Feb 15, 2012 at 10:33 AM, Josh Marcus <jmarcus@azavea.com> wrote:

As a member of the peanut gallery, I'll take a look and see if the
script that used to respond to commits could be fixed to use the REST
API.

 By the way , even when it worked, it sucked.  All tickets had to be closed by "anonymous" because there was apparently no authentication mechanism available without writing a jira plugin.  (I can't attest to that, I'm just passing along the explanation I remember.)

On Wed, Feb 15, 2012 at 10:19 AM, Adriaan Moors <adriaan.moors@epfl.ch> wrote:

we should spend the time on fixing JIRA rather than moving yet again (not that I am strictly against moving; I do consider it a variation on NIH)

I agree in principle, sort of.  However at casa du paulp, the well is poisoned against jira. Maybe life goes on without me, but when weighing alternatives, factor in my extremely limited jira participation going forward.  (You can factor that in as a positive if you want.)

Also be advised I'm not even out of the starting gate listing my issues.  (My jira issues, not my general issues.)
(Actually the overlap is amazingly high.)

On Wed, Feb 15, 2012 at 7:36 PM, Paul Phillips <paulp@improving.org> wrote:

On Wed, Feb 15, 2012 at 10:33 AM, Josh Marcus <jmarcus@azavea.com> wrote:

As a member of the peanut gallery, I'll take a look and see if the
script that used to respond to commits could be fixed to use the REST
API.

 By the way , even when it worked, it sucked.  All tickets had to be closed by "anonymous" because there was apparently no authentication mechanism available without writing a jira plugin.  (I can't attest to that, I'm just passing along the explanation I remember.)

yep, that is a major downside -- I'll see if we can enable "smart commits" (http://confluence.atlassian.com/display/FISHEYE/Enabling+Smart+Commits)

There's an authentication mechanism (post username & password to /rest/auth/latest/session), but it's does require your username and password.  So perhaps it needs to run on your local machine (with access to a local file with your password), unless there's a willingness to have a central store of passwords.  Not elegant, but could save you time.
--j
On Wed, Feb 15, 2012 at 1:36 PM, Paul Phillips <paulp@improving.org> wrote:

On Wed, Feb 15, 2012 at 10:33 AM, Josh Marcus <jmarcus@azavea.com> wrote:

As a member of the peanut gallery, I'll take a look and see if the
script that used to respond to commits could be fixed to use the REST
API.

 By the way , even when it worked, it sucked.  All tickets had to be closed by "anonymous" because there was apparently no authentication mechanism available without writing a jira plugin.  (I can't attest to that, I'm just passing along the explanation I remember.)

i don't mean to set the tipping point towards getting you a fresh well too high (just slightly above ground level),but let's see what we can do with some minimal, well-aimed, purification efforts first

On Wed, Feb 15, 2012 at 7:35 PM, Paul Phillips <paulp@improving.org> wrote:

On Wed, Feb 15, 2012 at 10:19 AM, Adriaan Moors <adriaan.moors@epfl.ch> wrote:

we should spend the time on fixing JIRA rather than moving yet again (not that I am strictly against moving; I do consider it a variation on NIH)

I agree in principle, sort of.  However at casa du paulp, the well is poisoned against jira. Maybe life goes on without me, but when weighing alternatives, factor in my extremely limited jira participation going forward.  (You can factor that in as a positive if you want.)

Also be advised I'm not even out of the starting gate listing my issues.  (My jira issues, not my general issues.)
(Actually the overlap is amazingly high.)

On Wed, Feb 15, 2012 at 10:37 AM, Adriaan Moors <adriaan.moors@epfl.ch> wrote:

i don't mean to set the tipping point towards getting you a fresh well too high (just slightly above ground level),but let's see what we can do with some minimal, well-aimed, purification efforts first

I'll go along with this if we can agree that the lion's share of the effort should be put into purifying the data, not jira itself.   Fixing the data we have to do anyway, and I will reap immediate benefits.  "Fixing" jira only invests us further, and the last thing I need is for the sunk cost fallacy to sing any louder.

well, it's every committer's password we need, assuming we want tickets to be closed by the person committing the change

On Wed, Feb 15, 2012 at 7:49 PM, Josh Marcus <jmarcus@azavea.com> wrote:

There's an authentication mechanism (post username & password to /rest/auth/latest/session), but it's does require your username and password.  So perhaps it needs to run on your local machine (with access to a local file with your password), unless there's a willingness to have a central store of passwords.  Not elegant, but could save you time.
--j
On Wed, Feb 15, 2012 at 1:36 PM, Paul Phillips <paulp@improving.org> wrote:

On Wed, Feb 15, 2012 at 10:33 AM, Josh Marcus <jmarcus@azavea.com> wrote:

As a member of the peanut gallery, I'll take a look and see if the
script that used to respond to commits could be fixed to use the REST
API.

 By the way , even when it worked, it sucked.  All tickets had to be closed by "anonymous" because there was apparently no authentication mechanism available without writing a jira plugin.  (I can't attest to that, I'm just passing along the explanation I remember.)

Well, I asked @YouTrack/@JetBrains on twitter if they'd be willing to donate a license, then I saw this: http://www.jetbrains.com/youtrack/buy/buy.jsp:  

OS-Project License 

 

Who Qualifies  

 

Open Source Project license is available free to non-commercial open source software development projects that meet the Open Source definition, have a dedicated website, and an active community. 

 

An Open Source Licenses entitles you to use YouTrack Unlimited User Pack and is valid for an initial period of one year. Annual renewals are provided on request, subject to JetBrains' approval. 

 

License Terms 

 

An Open Source Project license allows you to:

• use YouTrack for non-commercial, open source software development only
• run a single instance of YouTrack Server
• create an unlimited number of User Accounts

-0xe1a

TBH,
An issue tracker should have the following properties:
1) No "workflow" crap2) Be able to show code and stack traces in a non-disruptive way3) Have a REST API for creating and updating tickets 4) Arbitrary tagging of tickets5) Absolute ordering of tickets, no "priority" BS6) Should support discussions regarding the ticket7) Have great search/filtering capabilities
Almost everything else just complicates and makes working with the issue tracker a painful exercise.
An issue tracker should be a tool that helps in documenting the past, illustrating the current and aids in planning the future of some software project. That means low overhead, no handwaving and no fluff.
Cheers,√

On Wed, Feb 15, 2012 at 8:58 PM, Alex Cruise <alex@cluonflux.com> wrote:

Well, I asked @YouTrack/@JetBrains on twitter if they'd be willing to donate a license, then I saw this: http://www.jetbrains.com/youtrack/buy/buy.jsp:  

OS-Project License 

 

Who Qualifies  

 

Open Source Project license is available free to non-commercial open source software development projects that meet the Open Source definition, have a dedicated website, and an active community. 

 

An Open Source Licenses entitles you to use YouTrack Unlimited User Pack and is valid for an initial period of one year. Annual renewals are provided on request, subject to JetBrains' approval. 

 

License Terms 

 

An Open Source Project license allows you to:

• use YouTrack for non-commercial, open source software development only
• run a single instance of YouTrack Server
• create an unlimited number of User Accounts

-0xe1a

--
Viktor Klang

Akka Tech LeadTypesafe - The software stack for applications that scale

Twitter: @viktorklang

indeed, this issue is a major annoyance.

On Wednesday, 15. February 2012 at 19:53, Adriaan Moors wrote:

well, it's every committer's password we need, assuming we want tickets to be closed by the person committing the change

On Wed, Feb 15, 2012 at 7:49 PM, Josh Marcus <jmarcus@azavea.com> wrote:

There's an authentication mechanism (post username & password to /rest/auth/latest/session), but it's does require your username and password.  So perhaps it needs to run on your local machine (with access to a local file with your password), unless there's a willingness to have a central store of passwords.  Not elegant, but could save you time.
--j
On Wed, Feb 15, 2012 at 1:36 PM, Paul Phillips <paulp@improving.org> wrote:

On Wed, Feb 15, 2012 at 10:33 AM, Josh Marcus <jmarcus@azavea.com> wrote:

As a member of the peanut gallery, I'll take a look and see if the
script that used to respond to commits could be fixed to use the REST
API.

 By the way , even when it worked, it sucked.  All tickets had to be closed by "anonymous" because there was apparently no authentication mechanism available without writing a jira plugin.  (I can't attest to that, I'm just passing along the explanation I remember.)

we used jira's rest api before (https://github.com/lrytz/jira-commenter)

On Wednesday, 15. February 2012 at 19:49, Josh Marcus wrote:

There's an authentication mechanism (post username & password to /rest/auth/latest/session), but it's does require your username and password.  So perhaps it needs to run on your local machine (with access to a local file with your password), unless there's a willingness to have a central store of passwords.  Not elegant, but could save you time.
--j
On Wed, Feb 15, 2012 at 1:36 PM, Paul Phillips <paulp@improving.org> wrote:

On Wed, Feb 15, 2012 at 10:33 AM, Josh Marcus <jmarcus@azavea.com> wrote:

As a member of the peanut gallery, I'll take a look and see if the
script that used to respond to commits could be fixed to use the REST
API.

 By the way , even when it worked, it sucked.  All tickets had to be closed by "anonymous" because there was apparently no authentication mechanism available without writing a jira plugin.  (I can't attest to that, I'm just passing along the explanation I remember.)

i'd love to hear which one you think meets your requirements the best.
On Wednesday, 15. February 2012 at 21:32, √iktor Ҡlang wrote:

TBH,
An issue tracker should have the following properties:
1) No "workflow" crap2) Be able to show code and stack traces in a non-disruptive way3) Have a REST API for creating and updating tickets 4) Arbitrary tagging of tickets5) Absolute ordering of tickets, no "priority" BS6) Should support discussions regarding the ticket7) Have great search/filtering capabilities
Almost everything else just complicates and makes working with the issue tracker a painful exercise.
An issue tracker should be a tool that helps in documenting the past, illustrating the current and aids in planning the future of some software project. That means low overhead, no handwaving and no fluff.
Cheers,√

On Wed, Feb 15, 2012 at 8:58 PM, Alex Cruise <alex@cluonflux.com> wrote:

Well, I asked @YouTrack/@JetBrains on twitter if they'd be willing to donate a license, then I saw this: http://www.jetbrains.com/youtrack/buy/buy.jsp:  

OS-Project License   Who Qualifies     Open Source Project license is available free to non-commercial open source software development projects that meet the Open Source definition, have a dedicated website, and an active community.   An Open Source Licenses entitles you to use YouTrack Unlimited User Pack and is valid for an initial period of one year. Annual renewals are provided on request, subject to JetBrains' approval.    License Terms   An Open Source Project license allows you to:

• use YouTrack for non-commercial, open source software development only
• run a single instance of YouTrack Server
• create an unlimited number of User Accounts

-0xe1a

--
Viktor Klang

Akka Tech LeadTypesafe - The software stack for applications that scale

Twitter: @viktorklang

Then what about the github tracker? Simple, to the point, and Scala is
already on github.

See:
https://github.com/blog/831-issues-2-0-the-next-generation

API:
http://develop.github.com/p/issues.html

-Erik

2012/2/15 √iktor Ҡlang :
> TBH,
>
> An issue tracker should have the following properties:
>
> 1) No "workflow" crap
> 2) Be able to show code and stack traces in a non-disruptive way
> 3) Have a REST API for creating and updating tickets
> 4) Arbitrary tagging of tickets
> 5) Absolute ordering of tickets, no "priority" BS
> 6) Should support discussions regarding the ticket
> 7) Have great search/filtering capabilities
>
> Almost everything else just complicates and makes working with the issue
> tracker a painful exercise.
>
> An issue tracker should be a tool that helps in documenting the past,
> illustrating the current and aids in planning the future of some software
> project. That means low overhead, no handwaving and no fluff.
>
> Cheers,
> √
>
>
> On Wed, Feb 15, 2012 at 8:58 PM, Alex Cruise wrote:
>>
>> Well, I asked @YouTrack/@JetBrains on twitter if they'd be willing to
>> donate a license, then I saw
>> this: http://www.jetbrains.com/youtrack/buy/buy.jsp:
>>
>>>
>>> OS-Project License
>>>
>>>
>>>
>>> Who Qualifies
>>>
>>>
>>>
>>> Open Source Project license is available free to non-commercial open
>>> source software development projects that meet the Open Source definition,
>>> have a dedicated website, and an active community.
>>>
>>>
>>>
>>> An Open Source Licenses entitles you to use YouTrack Unlimited User Pack
>>> and is valid for an initial period of one year. Annual renewals are provided
>>> on request, subject to JetBrains' approval.
>>>
>>>
>>>
>>> License Terms
>>>
>>>
>>>
>>> An Open Source Project license allows you to:
>>>
>>> use YouTrack for non-commercial, open source software development only
>>> run a single instance of YouTrack Server
>>> create an unlimited number of User Accounts
>>
>>
>> -0xe1a
>
>
>
>
> --
> Viktor Klang
>
> Akka Tech Lead
> Typesafe - The software stack for applications that scale
>
> Twitter: @viktorklang
>

that looks pretty awesome! firsthand experiences, anyone? --a

On Thu, Feb 16, 2012 at 6:56 PM, Erik Bruchez <ebruchez@gmail.com> wrote:

Then what about the github tracker? Simple, to the point, and Scala is
already on github.

See:
https://github.com/blog/831-issues-2-0-the-next-generation

API:
http://develop.github.com/p/issues.html

-Erik

2012/2/15 √iktor Ҡlang <viktor.klang@gmail.com>:
> TBH,
>
> An issue tracker should have the following properties:
>
> 1) No "workflow" crap
> 2) Be able to show code and stack traces in a non-disruptive way
> 3) Have a REST API for creating and updating tickets
> 4) Arbitrary tagging of tickets
> 5) Absolute ordering of tickets, no "priority" BS
> 6) Should support discussions regarding the ticket
> 7) Have great search/filtering capabilities
>
> Almost everything else just complicates and makes working with the issue
> tracker a painful exercise.
>
> An issue tracker should be a tool that helps in documenting the past,
> illustrating the current and aids in planning the future of some software
> project. That means low overhead, no handwaving and no fluff.
>
> Cheers,
> √
>
>
> On Wed, Feb 15, 2012 at 8:58 PM, Alex Cruise <alex@cluonflux.com> wrote:
>>
>> Well, I asked @YouTrack/@JetBrains on twitter if they'd be willing to
>> donate a license, then I saw
>> this: http://www.jetbrains.com/youtrack/buy/buy.jsp:
>>
>>>
>>> OS-Project License
>>>
>>>
>>>
>>> Who Qualifies
>>>
>>>
>>>
>>> Open Source Project license is available free to non-commercial open
>>> source software development projects that meet the Open Source definition,
>>> have a dedicated website, and an active community.
>>>
>>>
>>>
>>> An Open Source Licenses entitles you to use YouTrack Unlimited User Pack
>>> and is valid for an initial period of one year. Annual renewals are provided
>>> on request, subject to JetBrains' approval.
>>>
>>>
>>>
>>> License Terms
>>>
>>>
>>>
>>> An Open Source Project license allows you to:
>>>
>>> use YouTrack for non-commercial, open source software development only
>>> run a single instance of YouTrack Server
>>> create an unlimited number of User Accounts
>>
>>
>> -0xe1a
>
>
>
>
> --
> Viktor Klang
>
> Akka Tech Lead
> Typesafe - The software stack for applications that scale
>
> Twitter: @viktorklang
>

When I looked at it the last time it was totally inadequate, but maybe that changed ...

On Thu, Feb 16, 2012 at 07:09:16PM +0100, Adriaan Moors wrote:
> that looks pretty awesome! firsthand experiences, anyone? --a

We use it for some projects at work, and I have used it on other
open-source projects as well. I am not an issue tracker "power user"
but I have found it pleasing to use and easy to navigate (better than
JIRA I would say).

I can't speak to many of the particular concerns raised except to say
that it has good integration with Git and pull requests (go figure!).

On 16/02/2012 19:09, Adriaan Moors wrote:

cqH9-x0jUcghzeGRA5MDwT+OJQ2wdvjLaqhJA [at] mail [dot] gmail [dot] com" type="cite">that looks pretty awesome! firsthand experiences, anyone? --a

On Thu, Feb 16, 2012 at 6:56 PM, Erik Bruchez <ebruchez [at] gmail [dot] com" rel="nofollow">ebruchez@gmail.com> wrote:

Then what about the github tracker? Simple, to the point, and Scala is
already on github. [...]

In my (little) experience, it was much too simple and rather confusing. But I had a bad a priori after a couple of minutes, and so I *might* be a little biased...

-- 
Francois ARMAND
http://fanf42.blogspot.com
http://www.normation.com

On Thu, Feb 16, 2012 at 10:09 AM, Adriaan Moors <adriaan.moors@epfl.ch> wrote:

that looks pretty awesome! firsthand experiences, anyone? --a

I desperately *want* to like it, because it would be so convenient and the pluses are obvious.  But in my opinion, it blows.  And if we're going to move somewhere which is closed-source or otherwise leaves us dependent on some unknown quantity to implement things we need, it had better look pretty freaking perfect at the time we move there.  No more of these JIRA tickets which have been open for 5+ years (or was it 10?) like "threaded comments".

On Thu, Feb 16, 2012 at 16:09, Adriaan Moors wrote:
> that looks pretty awesome! firsthand experiences, anyone? --a

As a user, it never bothered me. The puppet stuff I use/contribute to
use it, but that's very light. Also, I have no idea how it would
behave when multiple people must have access to it, and I haven't
looked into whatever tooling/API it might have. I'd be surprised if it
didn't come down to git-based text files, however, which would be very
amenable to scripting.

>
>
> On Thu, Feb 16, 2012 at 6:56 PM, Erik Bruchez wrote:
>>
>> Then what about the github tracker? Simple, to the point, and Scala is
>> already on github.
>>
>> See:
>> https://github.com/blog/831-issues-2-0-the-next-generation
>>
>> API:
>> http://develop.github.com/p/issues.html
>>
>> -Erik
>>
>> 2012/2/15 √iktor Ҡlang :
>> > TBH,
>> >
>> > An issue tracker should have the following properties:
>> >
>> > 1) No "workflow" crap
>> > 2) Be able to show code and stack traces in a non-disruptive way
>> > 3) Have a REST API for creating and updating tickets
>> > 4) Arbitrary tagging of tickets
>> > 5) Absolute ordering of tickets, no "priority" BS
>> > 6) Should support discussions regarding the ticket
>> > 7) Have great search/filtering capabilities
>> >
>> > Almost everything else just complicates and makes working with the issue
>> > tracker a painful exercise.
>> >
>> > An issue tracker should be a tool that helps in documenting the past,
>> > illustrating the current and aids in planning the future of some
>> > software
>> > project. That means low overhead, no handwaving and no fluff.
>> >
>> > Cheers,
>> > √
>> >
>> >
>> > On Wed, Feb 15, 2012 at 8:58 PM, Alex Cruise wrote:
>> >>
>> >> Well, I asked @YouTrack/@JetBrains on twitter if they'd be willing to
>> >> donate a license, then I saw
>> >> this: http://www.jetbrains.com/youtrack/buy/buy.jsp:
>> >>
>> >>>
>> >>> OS-Project License
>> >>>
>> >>>
>> >>>
>> >>> Who Qualifies
>> >>>
>> >>>
>> >>>
>> >>> Open Source Project license is available free to non-commercial open
>> >>> source software development projects that meet the Open Source
>> >>> definition,
>> >>> have a dedicated website, and an active community.
>> >>>
>> >>>
>> >>>
>> >>> An Open Source Licenses entitles you to use YouTrack Unlimited User
>> >>> Pack
>> >>> and is valid for an initial period of one year. Annual renewals are
>> >>> provided
>> >>> on request, subject to JetBrains' approval.
>> >>>
>> >>>
>> >>>
>> >>> License Terms
>> >>>
>> >>>
>> >>>
>> >>> An Open Source Project license allows you to:
>> >>>
>> >>> use YouTrack for non-commercial, open source software development only
>> >>> run a single instance of YouTrack Server
>> >>> create an unlimited number of User Accounts
>> >>
>> >>
>> >> -0xe1a
>> >
>> >
>> >
>> >
>> > --
>> > Viktor Klang
>> >
>> > Akka Tech Lead
>> > Typesafe - The software stack for applications that scale
>> >
>> > Twitter: @viktorklang
>> >
>
>

The API for GitHub Issues: http://developer.github.com/v3/issues/

On Thu, Feb 16, 2012 at 17:11, Daniel Sobral wrote:
> On Thu, Feb 16, 2012 at 16:09, Adriaan Moors wrote:
>> that looks pretty awesome! firsthand experiences, anyone? --a
>
> As a user, it never bothered me. The puppet stuff I use/contribute to
> use it, but that's very light. Also, I have no idea how it would
> behave when multiple people must have access to it, and I haven't
> looked into whatever tooling/API it might have. I'd be surprised if it
> didn't come down to git-based text files, however, which would be very
> amenable to scripting.
>
>>
>>
>> On Thu, Feb 16, 2012 at 6:56 PM, Erik Bruchez wrote:
>>>
>>> Then what about the github tracker? Simple, to the point, and Scala is
>>> already on github.
>>>
>>> See:
>>> https://github.com/blog/831-issues-2-0-the-next-generation
>>>
>>> API:
>>> http://develop.github.com/p/issues.html
>>>
>>> -Erik
>>>
>>> 2012/2/15 √iktor Ҡlang :
>>> > TBH,
>>> >
>>> > An issue tracker should have the following properties:
>>> >
>>> > 1) No "workflow" crap
>>> > 2) Be able to show code and stack traces in a non-disruptive way
>>> > 3) Have a REST API for creating and updating tickets
>>> > 4) Arbitrary tagging of tickets
>>> > 5) Absolute ordering of tickets, no "priority" BS
>>> > 6) Should support discussions regarding the ticket
>>> > 7) Have great search/filtering capabilities
>>> >
>>> > Almost everything else just complicates and makes working with the issue
>>> > tracker a painful exercise.
>>> >
>>> > An issue tracker should be a tool that helps in documenting the past,
>>> > illustrating the current and aids in planning the future of some
>>> > software
>>> > project. That means low overhead, no handwaving and no fluff.
>>> >
>>> > Cheers,
>>> > √
>>> >
>>> >
>>> > On Wed, Feb 15, 2012 at 8:58 PM, Alex Cruise wrote:
>>> >>
>>> >> Well, I asked @YouTrack/@JetBrains on twitter if they'd be willing to
>>> >> donate a license, then I saw
>>> >> this: http://www.jetbrains.com/youtrack/buy/buy.jsp:
>>> >>
>>> >>>
>>> >>> OS-Project License
>>> >>>
>>> >>>
>>> >>>
>>> >>> Who Qualifies
>>> >>>
>>> >>>
>>> >>>
>>> >>> Open Source Project license is available free to non-commercial open
>>> >>> source software development projects that meet the Open Source
>>> >>> definition,
>>> >>> have a dedicated website, and an active community.
>>> >>>
>>> >>>
>>> >>>
>>> >>> An Open Source Licenses entitles you to use YouTrack Unlimited User
>>> >>> Pack
>>> >>> and is valid for an initial period of one year. Annual renewals are
>>> >>> provided
>>> >>> on request, subject to JetBrains' approval.
>>> >>>
>>> >>>
>>> >>>
>>> >>> License Terms
>>> >>>
>>> >>>
>>> >>>
>>> >>> An Open Source Project license allows you to:
>>> >>>
>>> >>> use YouTrack for non-commercial, open source software development only
>>> >>> run a single instance of YouTrack Server
>>> >>> create an unlimited number of User Accounts
>>> >>
>>> >>
>>> >> -0xe1a
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > Viktor Klang
>>> >
>>> > Akka Tech Lead
>>> > Typesafe - The software stack for applications that scale
>>> >
>>> > Twitter: @viktorklang
>>> >
>>
>>
>
>
>
> --
> Daniel C. Sobral
>
> I travel to the future all the time.

On Thu, Feb 16, 2012 at 8:09 PM, Paul Phillips <paulp@improving.org> wrote:

I desperately *want* to like it, because it would be so convenient and the pluses are obvious.

me too, that's why I wanted to believe the hype from that article, but I just poked around a bit myself...  

But in my opinion, it blows.

... and I have to say it's a tad too minimalist

Hi Alex, Hi All,

I went through your discussion, and according to the requirements
you've specified I can tell that YouTrack would suit you perfectly:
* Advanced search capabilities via smart search queries with
completion
* Complete keyboard support
* Extensive REST API
* Tagging issues
* Complete customization (set of custom attributes) and customizable
workflows
* Support discussions, reflecting changes related to comments
* Batch issue modification via smart commands
* GitHub and Git Integration
And much more...

To be more specific, we would like to suggest you checking YouTrack in
action on your own issues. We'll be happy to offer you any kind of
license, YouTrack InCloud or YouTrack Stand-Alone absolutely free of
charge. For the beginning, we can import your projects from your
current Jira installation to YouTrack InCloud, make all the
configuration and customization you need, we'll just need more
detailed use case to configure custom fields and create workflows for
you.
What do you think? :)
Alex, feel free to contact me at valerie.andrianova@jetbrains.com

Regards,
Valerie Andrianova

On Feb 15, 11:58 pm, Alex Cruise wrote:
> Well, I asked @YouTrack/@JetBrains
> on twitter if they'd be willing to donate a license,
> then I saw this:http://www.jetbrains.com/youtrack/buy/buy.jsp:
>
> > *OS-Project License *
>
> *Who Qualifies  *
>
> Open Source Project license is available free to non-commercial open source
>
> > software development projects that meet the Open Source definition, have a
> > dedicated website, and an active community.
>
> An Open Source Licenses entitles you to use YouTrack Unlimited User Pack
>
> > and is valid for an initial period of one year. Annual renewals are
> > provided on request, subject to JetBrains' approval.
>
> *License Terms *
>
> An Open Source Project license allows you to:
>
> >    - use YouTrack for non-commercial, open source software development
> >    only
> >    - run a single instance of YouTrack Server
> >    - create an unlimited number of User Accounts
>
> -0xe1a

Hi Valerie,
Great! I had a look at http://www.jetbrains.com/youtrack/features/issue_tracking.html, and am impressed.
A few questions remain:

• Does the syntax highlighter support Scala?
• Does wiki syntax automatically link git commit hashes to github?
• Would it be feasible to rewrite old issue descriptions/comments to update old SVN rXXXX references to the current git commit hash (using YouTrack's python client api?)
• Can we map GitHub users to YouTrack users, so that when I (as the author of that commit, not necessarily the committer) close a ticket in a commit message, my YouTrack user is recorded as closing the ticket?
• How fine-grained are the permissions? Could we, say, restrict setting the priority field of an issue to a certain group of users?
• How can we export our issue database (just in case :-))?
• Is there any integration with code review?

thanks,adriaan
On Fri, Feb 17, 2012 at 11:34 AM, Valerie Andrianova <valery.andrianova@gmail.com> wrote:

Hi Alex, Hi All,

I went through your discussion, and according to the requirements
you've specified I can tell that YouTrack would suit you perfectly:
* Advanced search capabilities via smart search queries with
completion
* Complete keyboard support
*  Extensive REST API
*  Tagging issues
*  Complete customization (set of custom attributes) and customizable
workflows
*  Support discussions, reflecting changes related to comments
*  Batch issue modification via smart commands
*  GitHub and Git Integration
And much more...

To be more specific, we would like to suggest you checking YouTrack in
action on your own issues. We'll be happy to offer you any kind of
license, YouTrack InCloud or YouTrack Stand-Alone absolutely free of
charge. For the beginning, we can import your projects from your
current Jira installation to YouTrack InCloud, make all the
configuration and customization you need, we'll just need more
detailed use case to configure custom fields and create workflows for
you.
What do you think? :)
Alex, feel free to contact me at valerie.andrianova@jetbrains.com

Regards,
Valerie Andrianova


On Feb 15, 11:58 pm, Alex Cruise <a...@cluonflux.com> wrote:
> Well, I asked <https://twitter.com/#!/alexcruise/status/169871134966284288>@YouTrack/@JetBrains
> on twitter if they'd be willing to donate a license,
> then I saw this:http://www.jetbrains.com/youtrack/buy/buy.jsp:
>
> > *OS-Project License *
>
> *Who Qualifies  *
>
> Open Source Project license is available free to non-commercial open source
>
> > software development projects that meet the Open Source definition, have a
> > dedicated website, and an active community.
>
> An Open Source Licenses entitles you to use YouTrack Unlimited User Pack
>
> > and is valid for an initial period of one year. Annual renewals are
> > provided on request, subject to JetBrains' approval.
>
> *License Terms *
>
> An Open Source Project license allows you to:
>
> >    - use YouTrack for non-commercial, open source software development
> >    only
> >    - run a single instance of YouTrack Server
> >    - create an unlimited number of User Accounts
>
> -0xe1a

Three Things

1. JIRA's REST API seems to improve a lot with 5.0 (currently RC2). more APIs andthey will support OAuth - maybe this will help with the authentification limitations?   https://developer.atlassian.com/static/rest/jira/5.0-rc2.html
compared to the old https://developer.atlassian.com/static/rest/jira/4.4.1.html

2. YouTrack also doesn't have threads in comments (AFAICT)

3. In any case it cannot be wrong to have a toy instance of YouTrack to play with, andsince Valerie offered to set it up, I contacted her.

Lukas   

On Friday, 17. February 2012 at 12:08, Adriaan Moors wrote:

Hi Valerie,
Great! I had a look at http://www.jetbrains.com/youtrack/features/issue_tracking.html, and am impressed.
A few questions remain:

• Does the syntax highlighter support Scala?
• Does wiki syntax automatically link git commit hashes to github?
• Would it be feasible to rewrite old issue descriptions/comments to update old SVN rXXXX references to the current git commit hash (using YouTrack's python client api?)
• Can we map GitHub users to YouTrack users, so that when I (as the author of that commit, not necessarily the committer) close a ticket in a commit message, my YouTrack user is recorded as closing the ticket?
• How fine-grained are the permissions? Could we, say, restrict setting the priority field of an issue to a certain group of users?
• How can we export our issue database (just in case :-))?
• Is there any integration with code review?

thanks,adriaan
On Fri, Feb 17, 2012 at 11:34 AM, Valerie Andrianova <valery.andrianova@gmail.com> wrote:

Hi Alex, Hi All,

I went through your discussion, and according to the requirements
you've specified I can tell that YouTrack would suit you perfectly:
* Advanced search capabilities via smart search queries with
completion
* Complete keyboard support
*  Extensive REST API
*  Tagging issues
*  Complete customization (set of custom attributes) and customizable
workflows
*  Support discussions, reflecting changes related to comments
*  Batch issue modification via smart commands
*  GitHub and Git Integration
And much more...

To be more specific, we would like to suggest you checking YouTrack in
action on your own issues. We'll be happy to offer you any kind of
license, YouTrack InCloud or YouTrack Stand-Alone absolutely free of
charge. For the beginning, we can import your projects from your
current Jira installation to YouTrack InCloud, make all the
configuration and customization you need, we'll just need more
detailed use case to configure custom fields and create workflows for
you.
What do you think? :)
Alex, feel free to contact me at valerie.andrianova@jetbrains.com

Regards,
Valerie Andrianova


On Feb 15, 11:58 pm, Alex Cruise <a...@cluonflux.com> wrote:
> Well, I asked <https://twitter.com/#!/alexcruise/status/169871134966284288>@YouTrack/@JetBrains
> on twitter if they'd be willing to donate a license,
> then I saw this:http://www.jetbrains.com/youtrack/buy/buy.jsp:
>
> > *OS-Project License *
>
> *Who Qualifies  *
>
> Open Source Project license is available free to non-commercial open source
>
> > software development projects that meet the Open Source definition, have a
> > dedicated website, and an active community.
>
> An Open Source Licenses entitles you to use YouTrack Unlimited User Pack
>
> > and is valid for an initial period of one year. Annual renewals are
> > provided on request, subject to JetBrains' approval.
>
> *License Terms *
>
> An Open Source Project license allows you to:
>
> >    - use YouTrack for non-commercial, open source software development
> >    only
> >    - run a single instance of YouTrack Server
> >    - create an unlimited number of User Accounts
>
> -0xe1a

Hi Adriaan,
Please find the answers to your questions below:

• Does the syntax highlighter support Scala? - Yes,   use {code lang=scala} tag.
  
• Does wiki syntax automatically link git commit hashes to github? - Unfortunately, nope.
• Would it be feasible to rewrite old issue descriptions/comments to update old SVN rXXXX references to the current git commit hash (using YouTrack's python client api?) - Yes, using our REST API or Python client library.
• Can we map GitHub users to YouTrack users, so that when I (as the author of that commit, not necessarily the committer) close a ticket in a commit message, my YouTrack user is recorded as closing the ticket? - Yes, simply use the same email address both accounts. For more details, please watch demo or read this blog post.
•  How fine-grained are the permissions? Could we, say, restrict setting the priority field of an issue to a certain group of users? - Yes, if a field is set as "Private" it will be available for viewing and editing only to users which have proper permissions: "Read Issue Private Fields" and "Update Issue Private Fields" respectively.
• How can we export our issue database (just in case :-))? You can get your issues in CSV format, get DB backup (to migrate from Youtrack stand-alone to InCloud, for example), or export issues to any other format using REST API. 
• Is there any integration with code review? - Not yet.

Cheers,Valerie
On Fri, Feb 17, 2012 at 3:08 PM, Adriaan Moors <adriaan.moors@epfl.ch> wrote:

Hi Valerie,
Great! I had a look at http://www.jetbrains.com/youtrack/features/issue_tracking.html, and am impressed.
A few questions remain:

• Does the syntax highlighter support Scala?
• Does wiki syntax automatically link git commit hashes to github?
• Would it be feasible to rewrite old issue descriptions/comments to update old SVN rXXXX references to the current git commit hash (using YouTrack's python client api?)
• Can we map GitHub users to YouTrack users, so that when I (as the author of that commit, not necessarily the committer) close a ticket in a commit message, my YouTrack user is recorded as closing the ticket?
• How fine-grained are the permissions? Could we, say, restrict setting the priority field of an issue to a certain group of users?
• How can we export our issue database (just in case :-))?
• Is there any integration with code review? 

thanks,adriaan
On Fri, Feb 17, 2012 at 11:34 AM, Valerie Andrianova <valery.andrianova@gmail.com> wrote:

Hi Alex, Hi All,

I went through your discussion, and according to the requirements
you've specified I can tell that YouTrack would suit you perfectly:
* Advanced search capabilities via smart search queries with
completion
* Complete keyboard support
*  Extensive REST API
*  Tagging issues
*  Complete customization (set of custom attributes) and customizable
workflows
*  Support discussions, reflecting changes related to comments
*  Batch issue modification via smart commands
*  GitHub and Git Integration
And much more...

To be more specific, we would like to suggest you checking YouTrack in
action on your own issues. We'll be happy to offer you any kind of
license, YouTrack InCloud or YouTrack Stand-Alone absolutely free of
charge. For the beginning, we can import your projects from your
current Jira installation to YouTrack InCloud, make all the
configuration and customization you need, we'll just need more
detailed use case to configure custom fields and create workflows for
you.
What do you think? :)
Alex, feel free to contact me at valerie.andrianova@jetbrains.com

Regards,
Valerie Andrianova


On Feb 15, 11:58 pm, Alex Cruise <a...@cluonflux.com> wrote:
> Well, I asked <https://twitter.com/#!/alexcruise/status/169871134966284288>@YouTrack/@JetBrains
> on twitter if they'd be willing to donate a license,
> then I saw this:http://www.jetbrains.com/youtrack/buy/buy.jsp:
>
> > *OS-Project License *
>
> *Who Qualifies  *
>
> Open Source Project license is available free to non-commercial open source
>
> > software development projects that meet the Open Source definition, have a
> > dedicated website, and an active community.
>
> An Open Source Licenses entitles you to use YouTrack Unlimited User Pack
>
> > and is valid for an initial period of one year. Annual renewals are
> > provided on request, subject to JetBrains' approval.
>
> *License Terms *
>
> An Open Source Project license allows you to:
>
> >    - use YouTrack for non-commercial, open source software development
> >    only
> >    - run a single instance of YouTrack Server
> >    - create an unlimited number of User Accounts
>
> -0xe1a

--
Best Regards,
Valerie Andrianova
Marketing Manager
JetBrains
http://www.jetbrains.com
"Develop with Pleasure!"

Hi Valery,
Do your answers of  no  or  not yet  have YouTrack feature requests we can vote on?
Thanks,Jon

On Fri, Feb 17, 2012 at 9:40 AM, Valery Andrianova <valery.andrianova@gmail.com> wrote:

Hi Adriaan,
Please find the answers to your questions below:

• Does the syntax highlighter support Scala? - Yes,   use {code lang=scala} tag.
  
• Does wiki syntax automatically link git commit hashes to github? - Unfortunately, nope.
• Would it be feasible to rewrite old issue descriptions/comments to update old SVN rXXXX references to the current git commit hash (using YouTrack's python client api?) - Yes, using our REST API or Python client library.
• Can we map GitHub users to YouTrack users, so that when I (as the author of that commit, not necessarily the committer) close a ticket in a commit message, my YouTrack user is recorded as closing the ticket? - Yes, simply use the same email address both accounts. For more details, please watch demo or read this blog post.
•  How fine-grained are the permissions? Could we, say, restrict setting the priority field of an issue to a certain group of users? - Yes, if a field is set as "Private" it will be available for viewing and editing only to users which have proper permissions: "Read Issue Private Fields" and "Update Issue Private Fields" respectively.
• How can we export our issue database (just in case :-))? You can get your issues in CSV format, get DB backup (to migrate from Youtrack stand-alone to InCloud, for example), or export issues to any other format using REST API. 
• Is there any integration with code review? - Not yet.

Cheers,Valerie
On Fri, Feb 17, 2012 at 3:08 PM, Adriaan Moors <adriaan.moors@epfl.ch> wrote:

Hi Valerie,
Great! I had a look at http://www.jetbrains.com/youtrack/features/issue_tracking.html, and am impressed.
A few questions remain:

• Does the syntax highlighter support Scala?
• Does wiki syntax automatically link git commit hashes to github?
• Would it be feasible to rewrite old issue descriptions/comments to update old SVN rXXXX references to the current git commit hash (using YouTrack's python client api?)
• Can we map GitHub users to YouTrack users, so that when I (as the author of that commit, not necessarily the committer) close a ticket in a commit message, my YouTrack user is recorded as closing the ticket?
• How fine-grained are the permissions? Could we, say, restrict setting the priority field of an issue to a certain group of users?
• How can we export our issue database (just in case :-))?
• Is there any integration with code review? 

thanks,adriaan
On Fri, Feb 17, 2012 at 11:34 AM, Valerie Andrianova <valery.andrianova@gmail.com> wrote:

Hi Alex, Hi All,

I went through your discussion, and according to the requirements
you've specified I can tell that YouTrack would suit you perfectly:
* Advanced search capabilities via smart search queries with
completion
* Complete keyboard support
*  Extensive REST API
*  Tagging issues
*  Complete customization (set of custom attributes) and customizable
workflows
*  Support discussions, reflecting changes related to comments
*  Batch issue modification via smart commands
*  GitHub and Git Integration
And much more...

To be more specific, we would like to suggest you checking YouTrack in
action on your own issues. We'll be happy to offer you any kind of
license, YouTrack InCloud or YouTrack Stand-Alone absolutely free of
charge. For the beginning, we can import your projects from your
current Jira installation to YouTrack InCloud, make all the
configuration and customization you need, we'll just need more
detailed use case to configure custom fields and create workflows for
you.
What do you think? :)
Alex, feel free to contact me at valerie.andrianova@jetbrains.com

Regards,
Valerie Andrianova


On Feb 15, 11:58 pm, Alex Cruise <a...@cluonflux.com> wrote:
> Well, I asked <https://twitter.com/#!/alexcruise/status/169871134966284288>@YouTrack/@JetBrains
> on twitter if they'd be willing to donate a license,
> then I saw this:http://www.jetbrains.com/youtrack/buy/buy.jsp:
>
> > *OS-Project License *
>
> *Who Qualifies  *
>
> Open Source Project license is available free to non-commercial open source
>
> > software development projects that meet the Open Source definition, have a
> > dedicated website, and an active community.
>
> An Open Source Licenses entitles you to use YouTrack Unlimited User Pack
>
> > and is valid for an initial period of one year. Annual renewals are
> > provided on request, subject to JetBrains' approval.
>
> *License Terms *
>
> An Open Source Project license allows you to:
>
> >    - use YouTrack for non-commercial, open source software development
> >    only
> >    - run a single instance of YouTrack Server
> >    - create an unlimited number of User Accounts
>
> -0xe1a

--
Best Regards,
Valerie Andrianova
Marketing Manager
JetBrains
http://www.jetbrains.com
"Develop with Pleasure!"

They set up an instance and imported our current state of JIRA.http://scala.myjetbrains.com/youtrack/issues/SI?q=for%3A+extempore+%23Open+sort+by%3A+Priority
Login with your JIRA credentials.
Feel free to play around, changes will be discarded.
Lukas

On Friday, 17. February 2012 at 15:40, Valery Andrianova wrote:

Hi Adriaan,
Please find the answers to your questions below:

• Does the syntax highlighter support Scala? - Yes,   use {code lang=scala} tag.
  
• Does wiki syntax automatically link git commit hashes to github? - Unfortunately, nope.
• Would it be feasible to rewrite old issue descriptions/comments to update old SVN rXXXX references to the current git commit hash (using YouTrack's python client api?) - Yes, using our REST API or Python client library.
• Can we map GitHub users to YouTrack users, so that when I (as the author of that commit, not necessarily the committer) close a ticket in a commit message, my YouTrack user is recorded as closing the ticket? - Yes, simply use the same email address both accounts. For more details, please watch demo or read this blog post.
•  How fine-grained are the permissions? Could we, say, restrict setting the priority field of an issue to a certain group of users? - Yes, if a field is set as "Private" it will be available for viewing and editing only to users which have proper permissions: "Read Issue Private Fields" and "Update Issue Private Fields" respectively.
• How can we export our issue database (just in case :-))? You can get your issues in CSV format, get DB backup (to migrate from Youtrack stand-alone to InCloud, for example), or export issues to any other format using REST API. 
• Is there any integration with code review? - Not yet.

Cheers,Valerie
On Fri, Feb 17, 2012 at 3:08 PM, Adriaan Moors <adriaan.moors@epfl.ch> wrote:

Hi Valerie,
Great! I had a look at http://www.jetbrains.com/youtrack/features/issue_tracking.html, and am impressed.
A few questions remain:

• Does the syntax highlighter support Scala?
• Does wiki syntax automatically link git commit hashes to github?
• Would it be feasible to rewrite old issue descriptions/comments to update old SVN rXXXX references to the current git commit hash (using YouTrack's python client api?)
• Can we map GitHub users to YouTrack users, so that when I (as the author of that commit, not necessarily the committer) close a ticket in a commit message, my YouTrack user is recorded as closing the ticket?
• How fine-grained are the permissions? Could we, say, restrict setting the priority field of an issue to a certain group of users?
• How can we export our issue database (just in case :-))?
• Is there any integration with code review? 

thanks,adriaan
On Fri, Feb 17, 2012 at 11:34 AM, Valerie Andrianova <valery.andrianova@gmail.com> wrote:

Hi Alex, Hi All,

I went through your discussion, and according to the requirements
you've specified I can tell that YouTrack would suit you perfectly:
* Advanced search capabilities via smart search queries with
completion
* Complete keyboard support
*  Extensive REST API
*  Tagging issues
*  Complete customization (set of custom attributes) and customizable
workflows
*  Support discussions, reflecting changes related to comments
*  Batch issue modification via smart commands
*  GitHub and Git Integration
And much more...

To be more specific, we would like to suggest you checking YouTrack in
action on your own issues. We'll be happy to offer you any kind of
license, YouTrack InCloud or YouTrack Stand-Alone absolutely free of
charge. For the beginning, we can import your projects from your
current Jira installation to YouTrack InCloud, make all the
configuration and customization you need, we'll just need more
detailed use case to configure custom fields and create workflows for
you.
What do you think? :)
Alex, feel free to contact me at valerie.andrianova@jetbrains.com

Regards,
Valerie Andrianova


On Feb 15, 11:58 pm, Alex Cruise <a...@cluonflux.com> wrote:
> Well, I asked <https://twitter.com/#!/alexcruise/status/169871134966284288>@YouTrack/@JetBrains
> on twitter if they'd be willing to donate a license,
> then I saw this:http://www.jetbrains.com/youtrack/buy/buy.jsp:
>
> > *OS-Project License *
>
> *Who Qualifies  *
>
> Open Source Project license is available free to non-commercial open source
>
> > software development projects that meet the Open Source definition, have a
> > dedicated website, and an active community.
>
> An Open Source Licenses entitles you to use YouTrack Unlimited User Pack
>
> > and is valid for an initial period of one year. Annual renewals are
> > provided on request, subject to JetBrains' approval.
>
> *License Terms *
>
> An Open Source Project license allows you to:
>
> >    - use YouTrack for non-commercial, open source software development
> >    only
> >    - run a single instance of YouTrack Server
> >    - create an unlimited number of User Accounts
>
> -0xe1a

--
Best Regards,
Valerie Andrianova
Marketing Manager
JetBrains
http://www.jetbrains.com
"Develop with Pleasure!"

On Mon, Feb 20, 2012 at 1:26 PM, Lukas Rytz wrote:
> They set up an instance and imported our current state of JIRA.
> http://scala.myjetbrains.com/youtrack/issues/SI?q=for%3A+extempore+%23Op...
>
> Login with your JIRA credentials.
>
> Feel free to play around, changes will be discarded.

Here are some tips to learn the UI:

http://scala.myjetbrains.com/youtrack/dashboard?tab=Reports#tab=Hints

It would be worthwhile to see the git integration in action.

-jason

1) Can we hide not important issue fields in notifications? Personally I'm only interested in description, and maybe affected versions + subsystem.

2) Why two subsystem fields?
3) Do we really need the "story points" and "business value" fields?
On 20 February 2012 13:26, Lukas Rytz <lukas.rytz@epfl.ch> wrote:

They set up an instance and imported our current state of JIRA.http://scala.myjetbrains.com/youtrack/issues/SI?q=for%3A+extempore+%23Open+sort+by%3A+Priority
Login with your JIRA credentials.
Feel free to play around, changes will be discarded.
Lukas

On Friday, 17. February 2012 at 15:40, Valery Andrianova wrote:

Hi Adriaan,
Please find the answers to your questions below:

• Does the syntax highlighter support Scala? - Yes,   use {code lang=scala} tag.
  
• Does wiki syntax automatically link git commit hashes to github? - Unfortunately, nope.
• Would it be feasible to rewrite old issue descriptions/comments to update old SVN rXXXX references to the current git commit hash (using YouTrack's python client api?) - Yes, using our REST API or Python client library.
• Can we map GitHub users to YouTrack users, so that when I (as the author of that commit, not necessarily the committer) close a ticket in a commit message, my YouTrack user is recorded as closing the ticket? - Yes, simply use the same email address both accounts. For more details, please watch demo or read this blog post.
•  How fine-grained are the permissions? Could we, say, restrict setting the priority field of an issue to a certain group of users? - Yes, if a field is set as "Private" it will be available for viewing and editing only to users which have proper permissions: "Read Issue Private Fields" and "Update Issue Private Fields" respectively.
• How can we export our issue database (just in case :-))? You can get your issues in CSV format, get DB backup (to migrate from Youtrack stand-alone to InCloud, for example), or export issues to any other format using REST API. 
• Is there any integration with code review? - Not yet.

Cheers,Valerie
On Fri, Feb 17, 2012 at 3:08 PM, Adriaan Moors <adriaan.moors@epfl.ch> wrote:

Hi Valerie,
Great! I had a look at http://www.jetbrains.com/youtrack/features/issue_tracking.html, and am impressed.
A few questions remain:

• Does the syntax highlighter support Scala?
• Does wiki syntax automatically link git commit hashes to github?
• Would it be feasible to rewrite old issue descriptions/comments to update old SVN rXXXX references to the current git commit hash (using YouTrack's python client api?)
• Can we map GitHub users to YouTrack users, so that when I (as the author of that commit, not necessarily the committer) close a ticket in a commit message, my YouTrack user is recorded as closing the ticket?
• How fine-grained are the permissions? Could we, say, restrict setting the priority field of an issue to a certain group of users?
• How can we export our issue database (just in case :-))?
• Is there any integration with code review? 

thanks,adriaan
On Fri, Feb 17, 2012 at 11:34 AM, Valerie Andrianova <valery.andrianova@gmail.com> wrote:

Hi Alex, Hi All,

I went through your discussion, and according to the requirements
you've specified I can tell that YouTrack would suit you perfectly:
* Advanced search capabilities via smart search queries with
completion
* Complete keyboard support
*  Extensive REST API
*  Tagging issues
*  Complete customization (set of custom attributes) and customizable
workflows
*  Support discussions, reflecting changes related to comments
*  Batch issue modification via smart commands
*  GitHub and Git Integration
And much more...

To be more specific, we would like to suggest you checking YouTrack in
action on your own issues. We'll be happy to offer you any kind of
license, YouTrack InCloud or YouTrack Stand-Alone absolutely free of
charge. For the beginning, we can import your projects from your
current Jira installation to YouTrack InCloud, make all the
configuration and customization you need, we'll just need more
detailed use case to configure custom fields and create workflows for
you.
What do you think? :)
Alex, feel free to contact me at valerie.andrianova@jetbrains.com

Regards,
Valerie Andrianova


On Feb 15, 11:58 pm, Alex Cruise <a...@cluonflux.com> wrote:
> Well, I asked <https://twitter.com/#!/alexcruise/status/169871134966284288>@YouTrack/@JetBrains
> on twitter if they'd be willing to donate a license,
> then I saw this:http://www.jetbrains.com/youtrack/buy/buy.jsp:
>
> > *OS-Project License *
>
> *Who Qualifies  *
>
> Open Source Project license is available free to non-commercial open source
>
> > software development projects that meet the Open Source definition, have a
> > dedicated website, and an active community.
>
> An Open Source Licenses entitles you to use YouTrack Unlimited User Pack
>
> > and is valid for an initial period of one year. Annual renewals are
> > provided on request, subject to JetBrains' approval.
>
> *License Terms *
>
> An Open Source Project license allows you to:
>
> >    - use YouTrack for non-commercial, open source software development
> >    only
> >    - run a single instance of YouTrack Server
> >    - create an unlimited number of User Accounts
>
> -0xe1a

--
Best Regards,
Valerie Andrianova
Marketing Manager
JetBrains
http://www.jetbrains.com
"Develop with Pleasure!"

On Monday, 20. February 2012 at 13:55, Eugene Burmako wrote:

1) Can we hide not important issue fields in notifications? Personally I'm only interested in description, and maybe affected versions + subsystem.

don't know. i saw something that there are "private" and "public", and thosecan have different visibilities. not sure how this affects notifications though. 

2) Why two subsystem fields?

migration thing, should not be the case. i did not do anything to the fields setup, it'sjust the way it turned out after import. 

3) Do we really need the "story points" and "business value" fields?

no. again, fields can be completely customized. 

On 20 February 2012 13:26, Lukas Rytz <lukas.rytz@epfl.ch> wrote:

They set up an instance and imported our current state of JIRA.http://scala.myjetbrains.com/youtrack/issues/SI?q=for%3A+extempore+%23Open+sort+by%3A+Priority
Login with your JIRA credentials.
Feel free to play around, changes will be discarded.
Lukas

On Friday, 17. February 2012 at 15:40, Valery Andrianova wrote:

Hi Adriaan,
Please find the answers to your questions below:

• Does the syntax highlighter support Scala? - Yes,   use {code lang=scala} tag.
  
• Does wiki syntax automatically link git commit hashes to github? - Unfortunately, nope.
• Would it be feasible to rewrite old issue descriptions/comments to update old SVN rXXXX references to the current git commit hash (using YouTrack's python client api?) - Yes, using our REST API or Python client library.
• Can we map GitHub users to YouTrack users, so that when I (as the author of that commit, not necessarily the committer) close a ticket in a commit message, my YouTrack user is recorded as closing the ticket? - Yes, simply use the same email address both accounts. For more details, please watch demo or read this blog post.
•  How fine-grained are the permissions? Could we, say, restrict setting the priority field of an issue to a certain group of users? - Yes, if a field is set as "Private" it will be available for viewing and editing only to users which have proper permissions: "Read Issue Private Fields" and "Update Issue Private Fields" respectively.
• How can we export our issue database (just in case :-))? You can get your issues in CSV format, get DB backup (to migrate from Youtrack stand-alone to InCloud, for example), or export issues to any other format using REST API. 
• Is there any integration with code review? - Not yet.

Cheers,Valerie
On Fri, Feb 17, 2012 at 3:08 PM, Adriaan Moors <adriaan.moors@epfl.ch> wrote:

Hi Valerie,
Great! I had a look at http://www.jetbrains.com/youtrack/features/issue_tracking.html, and am impressed.
A few questions remain:

• Does the syntax highlighter support Scala?
• Does wiki syntax automatically link git commit hashes to github?
• Would it be feasible to rewrite old issue descriptions/comments to update old SVN rXXXX references to the current git commit hash (using YouTrack's python client api?)
• Can we map GitHub users to YouTrack users, so that when I (as the author of that commit, not necessarily the committer) close a ticket in a commit message, my YouTrack user is recorded as closing the ticket?
• How fine-grained are the permissions? Could we, say, restrict setting the priority field of an issue to a certain group of users?
• How can we export our issue database (just in case :-))?
• Is there any integration with code review? 

thanks,adriaan
On Fri, Feb 17, 2012 at 11:34 AM, Valerie Andrianova <valery.andrianova@gmail.com> wrote:

Hi Alex, Hi All,

I went through your discussion, and according to the requirements
you've specified I can tell that YouTrack would suit you perfectly:
* Advanced search capabilities via smart search queries with
completion
* Complete keyboard support
*  Extensive REST API
*  Tagging issues
*  Complete customization (set of custom attributes) and customizable
workflows
*  Support discussions, reflecting changes related to comments
*  Batch issue modification via smart commands
*  GitHub and Git Integration
And much more...

To be more specific, we would like to suggest you checking YouTrack in
action on your own issues. We'll be happy to offer you any kind of
license, YouTrack InCloud or YouTrack Stand-Alone absolutely free of
charge. For the beginning, we can import your projects from your
current Jira installation to YouTrack InCloud, make all the
configuration and customization you need, we'll just need more
detailed use case to configure custom fields and create workflows for
you.
What do you think? :)
Alex, feel free to contact me at valerie.andrianova@jetbrains.com

Regards,
Valerie Andrianova


On Feb 15, 11:58 pm, Alex Cruise <a...@cluonflux.com> wrote:
> Well, I asked <https://twitter.com/#!/alexcruise/status/169871134966284288>@YouTrack/@JetBrains
> on twitter if they'd be willing to donate a license,
> then I saw this:http://www.jetbrains.com/youtrack/buy/buy.jsp:
>
> > *OS-Project License *
>
> *Who Qualifies  *
>
> Open Source Project license is available free to non-commercial open source
>
> > software development projects that meet the Open Source definition, have a
> > dedicated website, and an active community.
>
> An Open Source Licenses entitles you to use YouTrack Unlimited User Pack
>
> > and is valid for an initial period of one year. Annual renewals are
> > provided on request, subject to JetBrains' approval.
>
> *License Terms *
>
> An Open Source Project license allows you to:
>
> >    - use YouTrack for non-commercial, open source software development
> >    only
> >    - run a single instance of YouTrack Server
> >    - create an unlimited number of User Accounts
>
> -0xe1a

--
Best Regards,
Valerie Andrianova
Marketing Manager
JetBrains
http://www.jetbrains.com
"Develop with Pleasure!"

On Monday, 20. February 2012 at 13:52, Jason Zaugg wrote:

It would be worthwhile to see the git integration in action.

what can it do, and how can i enable it?

On Mon, Feb 20, 2012 at 2:24 PM, Lukas Rytz wrote:
> On Monday, 20. February 2012 at 13:52, Jason Zaugg wrote:
>
> It would be worthwhile to see the git integration in action.
>
> what can it do, and how can i enable it?

- references to tickets in commits are noted in YouTrack
- tickets can be closed from commit comments.

But it involves one more moving part -- an installation of Jetbrains'
CI server, TeamCity. I this can be setup with a no-op build to perform
this integration, if you want to stick with Hudson to perform the
actual build. Would JetBrains also supply and configure this? How does
it integrate with the user database of YouTrack?

-jason

http://confluence.jetbrains.net/display/YTD3/Integration+with+TeamCity
http://confluence.jetbrains.net/display/YTD3/Executing+Commands+from+Com...

On Mon, Feb 20, 2012 at 2:24 PM, Lukas Rytz <lukas.rytz@epfl.ch> wrote:

On Monday, 20. February 2012 at 13:52, Jason Zaugg wrote:

It would be worthwhile to see the git integration in action.

what can it do,

close tickets from commits (http://www.jetbrains.com/youtrack/features/integrations.html -- actually, you can run arbitrary commands: http://confluence.jetbrains.net/display/YTHB/Executing+Commands+from+a+Comment+to+a+VCS+Change+Commit)
make sure your email address in your youtrack profile matches the one in your git(hub) config

and how can i enable it?

the instructions at http://confluence.jetbrains.net/display/YTD3/GitHub+Integration are a bit fuzzy
afaict, we should enable REST at: http://scala.myjetbrains.com/youtrack/settings (but where?)
and then enter the appropriate credentials for the YouTrack service hook: https://github.com/scala/scala/admin/hooks

On Monday, 20. February 2012 at 14:36, Adriaan Moors wrote:

On Mon, Feb 20, 2012 at 2:24 PM, Lukas Rytz <lukas.rytz@epfl.ch> wrote:

On Monday, 20. February 2012 at 13:52, Jason Zaugg wrote:

It would be worthwhile to see the git integration in action.

what can it do,

close tickets from commits (http://www.jetbrains.com/youtrack/features/integrations.html -- actually, you can run arbitrary commands: http://confluence.jetbrains.net/display/YTHB/Executing+Commands+from+a+Comment+to+a+VCS+Change+Commit)

OK. Well, we can anyway "do whatever we want" (whatever the YouTrack / JIRA REST API allows) with a customscript that runs on every commit, such as the https://scala-webapps.epfl.ch/jenkins/view/Misc/job/commit-actions/
The thing that is harder to achieve is links between GitHub and the issue tracker - link "SI-1234" in GitHub to the bugtracker - link commit hashes in the bugtracker to GitHub

The thing that is harder to achieve is links between GitHub and the issue tracker  - link "SI-1234" in GitHub to the bugtracker - link commit hashes in the bugtracker to GitHub

indeed -- those are the main show stoppers as I see it
worst case we'll have to write a greasemonkey script to do the rewrite client-side in the browser