Description of problem: The JBoss team receives a lot of notifications from Bugzilla due to the Bugzilla integration. A request states that implemented behaviour is correct, but things have changed and the notifications become a problem. This ticket describes the problem: * https://engineering.redhat.com/rt/Ticket/Display.html?id=186984 Discontinue complete propagation between JIRA and BugZilla This is the request to make the comments go away: * https://engineering.redhat.com/rt/Ticket/Display.html?id=191662 Remove cross posting of comments between Jira and Bugzilla Since more people may rely on this functionality, the proposed solution is to make the notifications configurable: * Give the product owner the ability to configure the propagation flag. * Standard behaviour should remain the current behaviour.
This is the opposite behavior from what I had proposed/required. I think I speak for the majority of JIRA project owners on issues.jboss.org with the following statements: "I've identified three different categories of requirements from JIRA project admins. 1) The first group own projects which want no propagation at all other than the original link. I think this represents the majority of users. 2) The second group own projects which want propagation of comments only - no status or flag changes or anything like that. This is the minority of users. 3) The third group are content with things as they are. As far as I know, there is nobody in this category. The tricky part is that these dividing lines are between projects on the JIRA side, not the Bugzilla side. For example it doesn't help us to prevent propagation for one Bugzilla project only to end up with the same level of noise from another; likewise those users who *want* comment-level propagation won't be well-served by having some BZ projects sending information and some not. So, here is my counter-proposal for the short term: 1) Modify BZ to propagate comments only, but otherwise keep the same behavior as today 2) Have the JBoss.org team make administrative changes to JIRA on a per-project basis to prevent propagation of comments from the BZ integration user, based on the preference of the JIRA project owner" I'm not sure of any group that depends on/uses the status propagation but that would play in to the requirements as well. But either way, the JIRA project owner is the real decision maker here because they're the owners of the directly affected systems.
My proposal from the perspective of JIRA project users is that we definitely do not want or need BZ status updates of any sort pushed into our projects, but things I'd seen on the mailing lists led me to believe that some people were in fact interested in the comments. But this is what has become clear: only certain JIRA projects want any input from Bugzilla at all, and those projects (represented by Anne-Louise) seem to want status changes only. The far most important change is to respect the desires of the people who own the projects this spam is being pushed into. The real requirement is here. Just doing half of the solution isn't any solution at all - we all lose measurable amounts of time tracking down what look like new issues but are actually just the reanimated dead of old JIRA issues only just now being brought into Bugzilla due to project/product lag time. I wasn't proposing "1 or 2", I was proposing "1 and 2". Without 2, 1 is pretty much pointless. It must be up to the JIRA project admin to decide what is pushed in. If we cannot select this on the JIRA side then I'd ask the Bugzilla side to be configurable and configured as to which projects it is allowed to push to, status or comments or otherwise. This absolutely must be an *opt-in* system with the full approval of the JIRA project owner, due to its invasive nature.
My understanding is that the consensus among the Middleware Team is that status changes should continue to be propagated.
David, to make the requirements perfectly clear, please confirm that: 1. Comments made in Bugzilla items shall no longer be propagated to linked Jira issues. 2. Status changes made in Bugzilla shall continue to be propagated to linked Jira issues as comments.
(In reply to Jason McDonald from comment #17) > David, to make the requirements perfectly clear, please confirm that: 3. The same should be applied in the other direction too (i.e. Only status changes in JIRA will make a comment in Red Hat Bugzilla)
JIRA issue ORG-1831 has been created to make the change in JIRA. This bug is to make the change in Red Hat Bugzilla.
This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug. -- simon
Vlastimil Eliáš <velias> updated the status of jira ORG-1831 to Closed