Re: [Development] Changes to the Jira roles and workflow

2012-02-13 Thread shane.kearns
-bounces+shane.kearns=accenture@qt-project.org [mailto:development-bounces+shane.kearns=accenture@qt-project.org] On Behalf Of Alan Alpert Sent: 09 February 2012 22:26 To: development@qt-project.org Cc: j...@qt-project.org Subject: Re: [Development] Changes to the Jira roles and workflow

Re: [Development] Changes to the Jira roles and workflow

2012-02-13 Thread marius.storm-olsen
On 02/13/2012 01:27 PM, ext shane.kea...@accenture.commailto:shane.kea...@accenture.com wrote: Maybe you're looking at a triage role, if the role is prioritizing and assigning of tasks among a team that is mostly funded by one company. Another role we need in JIRA is contributor. This is

Re: [Development] Changes to the Jira roles and workflow

2012-02-09 Thread Thiago Macieira
On Thursday, 9 de February de 2012 10.20.47, bradley.hug...@nokia.com wrote: There is call for discussion around default assignee – is it the module maintainer? Which tasks are up for grabs if everything new goes to the maintainer? Unassigned should be the default. When someone picks up the

Re: [Development] Changes to the Jira roles and workflow

2012-02-09 Thread Daniel Teske
Default Assignee There is call for discussion around default assignee – is it the module maintainer? Which tasks are up for grabs if everything new goes to the maintainer? Unassigned should be the default. When someone picks up the task, they should assign it to themselves. Anything

Re: [Development] Changes to the Jira roles and workflow

2012-02-09 Thread marius.storm-olsen
On 09/02/2012 04:33, ext Thiago Macieira wrote: On Thursday, 9 de February de 2012 10.20.47, bradley.hug...@nokia.com wrote: There is call for discussion around default assignee – is it the module maintainer? Which tasks are up for grabs if everything new goes to the maintainer? Unassigned

Re: [Development] Changes to the Jira roles and workflow

2012-02-09 Thread michael.goddard
Howdy, Assigning new tasks unassigned will not notify the maintainer about issues in the modules that have come up, and the maintainer will not by notified when someone takes a task and starts working on it. Surely this is something that JIRA could support? Watching a component or similar?

Re: [Development] Changes to the Jira roles and workflow

2012-02-09 Thread marius.storm-olsen
On 09/02/2012 05:41, Goddard Michael (Nokia-MP/Brisbane) wrote: Assigning new tasks unassigned will not notify the maintainer about issues in the modules that have come up, and the maintainer will not by notified when someone takes a task and starts working on it. Surely this is something

Re: [Development] Changes to the Jira roles and workflow

2012-02-09 Thread shane.kearns
] Changes to the Jira roles and workflow On 09/02/2012 05:41, Goddard Michael (Nokia-MP/Brisbane) wrote: Assigning new tasks unassigned will not notify the maintainer about issues in the modules that have come up, and the maintainer will not by notified when someone takes a task and starts working

Re: [Development] Changes to the Jira roles and workflow

2012-02-09 Thread Alan Alpert
On Thu, 9 Feb 2012 12:58:40 ext marius.storm-ol...@nokia.com wrote: Hi, ... There is some discussion over if we should burden maintainers with Release Management work. There is a suggestion of a new workflow Nokia Engineer - no privileges in Gerrit only in Jira. That role might be