I believe Alex can help you with setting up your JIRA account to be able to
assign stuff to yourself.

As for non-committers, a comment saying 'I am on it'  should be
sufficient.  Regularly updating tasks/sub-tasks with progress updates would
also be helpful in case someone else wants to continue from where things
are.

This is an issue I struggled with at the beginning as well.  It became
easier as I got used to the process  and stuck to it.

Take a look at FLEX-33106 for an example of how multiple developers worked
together by creating sub tasks and posting regular progress updates.

Thanks,
Om
On Oct 23, 2012 8:16 AM, "Michael Schmalle" <apa...@teotigraphix.com> wrote:

> Quoting Carol Frampton <cfram...@adobe.com>:
>
>
>
>>> I don't have permission as a committer? I created the task and
>>> assigned it to myself, am I missing something? I know I can't assign a
>>> task to Chema since he is not a listed user.
>>>
>>
>> If it wasn't you then it was Chema that said he couldn't can't assign a
>> task.  If he is one of the people working on this how is he suppose to
>> indicate this if he can't assign the task to himself?
>>
>> At this point I'm staying out of this.  You guys can figure out how you
>> want to do it.  I was just trying to help but I only seem to have
>> complicated matters.
>>
>
>
> No, I'm listening to what you are saying, and your not complicating
> things. :)
>
> I'm new to this stuff to be honest and I'm just looking for a little
> guidance.
>
> Chema wanted to help, so he went ahead and tried to find all the files
> that needed to be updated.
>
> He then just tired to create sub tasks himself to organize the effort. I
> think he didn't realize he couldn't assign tasks to himself.
>
> So I think the question is how actually a committer and contributor can
> work on something together as large as this task is and communicate to each
> other what the other is doing so we don't duplicate work.
>
> Mike
>
> --
> Michael Schmalle - Teoti Graphix, LLC
> http://www.teotigraphix.com
> http://blog.teotigraphix.com
>
>

Reply via email to