You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@any23.apache.org by Michele Mostarda <mi...@gmail.com> on 2012/01/14 17:38:00 UTC

[DISCUSS] Jira Issue Management

Hi guys,

  I was thinking: how to coordinate the activity source code without the
'Start Progress' status update on Jira issues?
For example now I would start to work on ANY23-21, but it is assigned to
Lewis and I don't know if he already started working on it.
It would be useful if possible to (re)activate the status management for
the project issues.

In this particular case It is better if I take in charge the issue: there
is a small code refactoring related to the PluginManager
 and package names that must be done to restore the test cases after a root
package renaming.

The best.

Mic


-- 
Michele Mostarda
Senior Software Engineer
skype: michele.mostarda
twitter: micmos
mail: me@michelemostarda.com
site : http://www.michelemostarda.com

Re: [DISCUSS] Jira Issue Management

Posted by Michele Mostarda <mi...@gmail.com>.
On 14 January 2012 18:24, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:

> Hi Michele,
>
> There should be a start progress icon when it's assigned to you --
> do you have the ability to assign JIRA issues to yourself? It might
> be a permissions issue, so if not, let me know.
>

Don't worry Chris, just a mental issue :)
The start button appears only if the viewer is the owner of the issue.


>
> Cheers,
> Chris
>

The best.
Mic


>
> On Jan 14, 2012, at 8:38 AM, Michele Mostarda wrote:
>
> > Hi guys,
> >
> >  I was thinking: how to coordinate the activity source code without the
> > 'Start Progress' status update on Jira issues?
> > For example now I would start to work on ANY23-21, but it is assigned to
> > Lewis and I don't know if he already started working on it.
> > It would be useful if possible to (re)activate the status management for
> > the project issues.
> >
> > In this particular case It is better if I take in charge the issue: there
> > is a small code refactoring related to the PluginManager
> > and package names that must be done to restore the test cases after a
> root
> > package renaming.
> >
> > The best.
> >
> > Mic
> >
> >
> > --
> > Michele Mostarda
> > Senior Software Engineer
> > skype: michele.mostarda
> > twitter: micmos
> > mail: me@michelemostarda.com
> > site : http://www.michelemostarda.com
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>


-- 
Michele Mostarda
Senior Software Engineer
skype: michele.mostarda
twitter: micmos
mail: me@michelemostarda.com
site : http://www.michelemostarda.com

Re: [DISCUSS] Jira Issue Management

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Michele,

There should be a start progress icon when it's assigned to you -- 
do you have the ability to assign JIRA issues to yourself? It might
be a permissions issue, so if not, let me know.

Cheers,
Chris

On Jan 14, 2012, at 8:38 AM, Michele Mostarda wrote:

> Hi guys,
> 
>  I was thinking: how to coordinate the activity source code without the
> 'Start Progress' status update on Jira issues?
> For example now I would start to work on ANY23-21, but it is assigned to
> Lewis and I don't know if he already started working on it.
> It would be useful if possible to (re)activate the status management for
> the project issues.
> 
> In this particular case It is better if I take in charge the issue: there
> is a small code refactoring related to the PluginManager
> and package names that must be done to restore the test cases after a root
> package renaming.
> 
> The best.
> 
> Mic
> 
> 
> -- 
> Michele Mostarda
> Senior Software Engineer
> skype: michele.mostarda
> twitter: micmos
> mail: me@michelemostarda.com
> site : http://www.michelemostarda.com


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Re: [DISCUSS] Jira Issue Management

Posted by Michele Mostarda <mi...@gmail.com>.
Ok, forget about it!

The 'Start progress' button was already there and appears only for issues
assigned to the current user.

Sorry.

Mic

On 14 January 2012 17:38, Michele Mostarda <mi...@gmail.com>wrote:

>
> Hi guys,
>
>   I was thinking: how to coordinate the activity source code without the
> 'Start Progress' status update on Jira issues?
> For example now I would start to work on ANY23-21, but it is assigned to
> Lewis and I don't know if he already started working on it.
> It would be useful if possible to (re)activate the status management for
> the project issues.
>
> In this particular case It is better if I take in charge the issue: there
> is a small code refactoring related to the PluginManager
>  and package names that must be done to restore the test cases after a
> root package renaming.
>
> The best.
>
> Mic
>
>
> --
> Michele Mostarda
> Senior Software Engineer
> skype: michele.mostarda
> twitter: micmos
> mail: me@michelemostarda.com
> site : http://www.michelemostarda.com
>
>


-- 
Michele Mostarda
Senior Software Engineer
skype: michele.mostarda
twitter: micmos
mail: me@michelemostarda.com
site : http://www.michelemostarda.com