[Jenkins-infra] Project Infrastructure, Component CI, ticket needs to go to group of people
Larry Shatzer, Jr.
larrys at gmail.com
Tue Sep 6 14:01:25 UTC 2016
JIRA does not allow assigning an issue to a group. There are some
I'm also guessing the people who would be in that "group" probably already
get a ton of JIRA spam, I mean email... :)
Another possibility is to leave them as unassigned, instead of having a
default assignee, and then creating a filter in JIRA, that is on peoples
dashboards, and sends an email once a day if there are tickets unassigned
(and still open) in that queue. Then this email be filtered differently by
There are possibly other solutions as well.
On Mon, Sep 5, 2016 at 12:25 PM, Craig Rodrigues <rodrigc at freebsd.org>
> I cannot attend the Jenkins governance meeting,
> so at Arnaud Héritier's suggestion I am posting here.
> I would like to propose that if a ticket is filed with Project t
> * Infrastructure*, Component *CI* that the ticket go to a group of people
> where it can
> be triaged and assigned, rather than a direct assignee.
> For example, I filed https://issues.jenkins-ci.org/browse/INFRA-741 ,
> and it went to a direct assignee, but no action happened on this until
> I raised the issue on jenkinsci-dev, and Arnaud jumped in and addressed
> the issue.
> This is not an efficient way to handle requests.
> Due to the popularity of Jenkins, the mailing lists receive a high volume
> traffic, and are very difficult to track and follow the status of requests.
> Jenkins-infra mailing list
> Jenkins-infra at lists.jenkins-ci.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Jenkins-infra