[Jenkins-infra] Project Infrastructure, Component CI, ticket needs to go to group of people

R. Tyler Croy tyler at monkeypox.org
Tue Sep 6 20:21:35 UTC 2016

(replies inline)

On Tue, 06 Sep 2016, Larry Shatzer, Jr. wrote:

> JIRA does not allow assigning an issue to a group. There are some
> "workarounds"
> https://confluence.atlassian.com/jira/how-do-i-assign-issues-to-multiple-users-207489749.html
> and
> https://answers.atlassian.com/questions/248664/assign-issue-to-group-in-jira
> 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
> the recipients.
> There are possibly other solutions as well.

I went ahead and made unassigned the default for the 'ci' component.
Personally, I understand the frustration/timing here, but I interpret this as a
stronger need to get `Jenkinsfile` and GitHub Organization Folder support
on ci.jenkins.io with some suitable ACLs in place.

- R. Tyler Croy

     Code: <https://github.com/rtyler>
  Chatter: <https://twitter.com/agentdero>

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20160906/b540cb06/attachment.asc>

More information about the Jenkins-infra mailing list