commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rahul Akolkar <>
Subject Re: [SCXML] creating GSoC tasks in JIRA
Date Thu, 06 May 2010 20:26:45 GMT
On Thu, May 6, 2010 at 3:42 PM, Jacob Beard <> wrote:
> Hi Rahul,
> I've created a number of sub-tasks under the original JIRA issue.

Thanks, this is useful. Two quick comments:

 * I've updated the 'GSoC' fix version to 3 sub-task issues that were missing it
 * For clarity, please add a short description of what the term
"benchmark models" means in SCXML-119

> One
> thing that I thought was possible, which I am now not sure about, is
> whether it is possible to create arbitrarily nested sub-tasks. It
> seemed I was unable to do so, but this may have been because the task
> was not assigned to me, or because I was not "working" on the task.
> Rather than create sub-sub-tasks, I instead simply broke the task down
> by providing a list in the task description. But, in order to track
> where I spend my time, I think it would be better to use
> sub-sub-tasks, if this is possible. What do you think about this?

Doesn't look to be possible. A similar effect can be achieved by
opening new issues and then setting up dependency links to the
sub-tasks. This is similar in the sense that it will be possible to
drill down from SCXML-115 to any of these issues and also trace back
from any of these issues up to SCXML-115.

> Also, would it be possible for you to assign the tasks to me please?
> It seems I do not have permissions to assign them to myself.

You will need to be added to the Commons Developers group in JIRA. I
can do related changes for that this weekend.

> Finally, I'd like to add an RSS feed to my blog which tracks the work
> I do on this. Do you know, is it possible to obtain an RSS feed from
> JIRA that tracks updates on a particular task?

There may be easier means, but one way would be to pipe the specific
email notifications using an email filter to some email to RSS
service. You will receive all notifications for the issues mentioned
above since you are the reporter for these issues. If there are issues
you are not the reporter of that you'd like to include, you can start
watching them in JIRA and have changes delivered to your inbox that
way. Finally, if you subscribe to (if you
haven't already) you will get email notifications for all Commons
components' issues.


> Thanks,
> Jake
> On Tue, May 4, 2010 at 9:36 PM, Jacob Beard <> wrote:
>> The first usage pattern seems preferable to me. I'll probably start
>> entering data tomorrow.
>> Thanks,
>> Jake
>> On Tue, May 4, 2010 at 9:23 PM, Rahul Akolkar <> wrote:
>>> On Tue, May 4, 2010 at 8:54 PM, Rahul Akolkar <>
>>>> On Tue, May 4, 2010 at 11:23 AM, Jacob Beard <>
>>>>> Hi,
>>>>> I'd like to start populating JIRA with tasks and milestones related to
>>>>> my GSoC project,
>>>> <snip/>
>>>> +1
>>>>> and I'm wondering what is the best way to go about
>>>>> this. I think these tasks should go under the SCXML project in
>>>>> JIRA[1], but I'm not sure if I should do more to differentiate them as
>>>>> a separate sub-project.
>>>> <snap/>
>>>> One option is to create sub-tasks for the original issue you have,
>>>> SCXML-115 [1] (see LHS menu).
>>>> This will create separate issues in JIRA for each task, so they can be
>>>> managed independently, but it will also neatly roll everything up
>>>> under the above umbrella issue. For an example of this (from another
>>>> project), see ATTIC-1 [2].
>>>> What do you think about using this approach?
>>> <snip/>
>>> Alternative is I can add a suitable component (a short label) to the
>>> SCXML project in JIRA, and issues can then be marked against that
>>> component. In this case, the issue dependencies will have to be set up
>>> manually so readers can get a good sense of the dependency tree for
>>> these tasks.
>>> Slight preference to the former JIRA usage pattern.
>>> -Rahul
>>>> [1]
>>>> [2]
>>>>> Please let me know what you think. Thanks,
>>>>> Jake
>>>>> [1]

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message