gtg-user team mailing list archive

[Germán Gutiérrez <germang@xxxxxxxxx>]

Ok! let's face the jira backend approach, can you point me to a good
documentation link about (just in case, I'll try to find it myself)

On Wed, Nov 9, 2011 at 2:17 PM, Izidor Matušov <izidor.matusov@xxxxxxxxx> wrote:
> Hi Germán,
>
> Am 09.11.2011 14:15, schrieb Germán Gutiérrez:
>>
>> OK, I'll try to describe the process I have as simple as possible:
>> * I Take notes with GTG for some new (or old!) things to do
>> * Some of them become a Jira Ticket
>> * I want to import ticket number and summary to the title of the
>> GTGTask, the description appended to the text and the components and
>> assignee as tags
>>
>> I think I can do something like that from the takslist view, I'll try
>> that way, if I have one task focused I can do what I want without
>> opening the task from GTG, and instead do that from the plugin.
>
> Do you know the concept of backends? It is a new feature of GTG. Backends
> can import/export/synchronize your tasks (or a part of your tasks) with
> external services like Google Tasks, Remember the Milk.
>
> As far as I understand your needs, a backend would be a better solution. You
> take some notes and after that assign a special tag @jira which adds the
> task to your backend. Backend can export your task to Jira. The backend also
> synchronize your tickets in Jira and imports them into GTG.
>
> I know that backends infrastructure is not 100% perfect because there were
> no real usage so far and many details must to be polished. If you decide to
> make it as a backend (the best way is to make it general so other users can
> use it), I can do support for you (implement missing features, debug
> problems) in exchange.
>
> Izidor
>



-- 
Saludos,
                         Germán

Delivering common sense since 1969 <Epoch Fail!>.

The Nature is not amiable; It treats impartially to all the things.
The wise person is not amiable; He treats all people impartially.