[Development] Changes to the Jira roles and workflow

shane.kearns at accenture.com shane.kearns at accenture.com
Thu Feb 9 13:14:57 CET 2012

It's easy to make a report on your personal dashboard to show issues reported on a given (set of) component(s).
It means polling rather than email notification, but the email notifications have poor signal:noise ratio.

> -----Original Message-----
> From: development-bounces+shane.kearns=accenture.com at qt-project.org
> [mailto:development-bounces+shane.kearns=accenture.com at qt-project.org]
> On Behalf Of marius.storm-olsen at nokia.com
> Sent: Thursday, February 09, 2012 11:47
> To: michael.goddard at nokia.com
> Cc: thiago.macieira at intel.com; development at qt-project.org
> Subject: Re: [Development] 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
> >> on it.
> >
> > Surely this is something that JIRA could support?  Watching a
> > component or similar?  (also can Gerrit do this too?)
> Not by default. But there is a 3rdparty pluging to allow adding Watcher
> on components:
> https://studio.plugins.atlassian.com/wiki/display/JCWP/JIRA+Component+Wa
> tcher+Plugin
> --
> .marius
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

Subject to local law, communications with Accenture and its affiliates including telephone calls and emails (including content), may be monitored by our systems for the purposes of security and the assessment of internal compliance with Accenture policy.


More information about the Development mailing list