Hi Rafael, > I believe this was briefly discussed on IRC, but just to recapitulate, is it > possible to have JIRA bugs assigned automatically to non-approvers?
The automatic assignment of new tasks is based on component ownership. Anyone who is assignable can be the owner of a component, and they can elect to be the default assignee for tasks raised against that component (the other option is to default new tasks to Unassigned). > We are in the process of revamping Blackberry's Qt page on Github > (github.com/blackberry/Qt), and one of the things we would like to do is to do > away with the 'Issues' area, and direct all the QNX/BB Qt bugs to the Qt > bugtracker - to allow closer community interaction and to be coherent with the > rest of the Qt ecosystem. Those bugs should certainly go to the Qt bug tracker. You will probably find that many of them aren't specific to QNX/BB and that people interested in other platforms can help. At present the bug tracker doesn't have components for specific platforms. We used to have those and they unfortunately became a dumping ground for any bug seen on a platform, rather than only getting bugs that were specific to those platforms. Bugs should generally be raised against the appropriate component, with the affected platform(s) noted in Environment field. The maintainer of that component can then reassign to people looking after specific platforms if they determine that the bug is in the platform support code (or if the reporter is already certain that the bug is platform-specific, they can assign directly). > It would be nice if someone could point out if this is possible, and if so, > what has to be done to comply with the requirements (if any). I think the main thing is to make sure that Maintainers know who the potential assignees are when they discover a bug in platform-specific code. I don't think we have that documented very well at present, even for the desktop platforms. Cheers, -- Jason _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
