How to view the bugs raised by other Users in restricted Group

Hi 

I have created group A -  product A, Product B to Group B and added group restriction options

Group A
ENTRY, MANDATORY MANDATORY, CanEdit selected
Users in Group A  are not able to view the bugs raised by the other users in Group A but able to view the bugs raised by them. 

I have played with group permissions but i am not able to achieve

Group permission selected for this group
Groups That Can See This Group
("Users in X can see users in GroupA" - admin, groupA

Could you please help in this issue
Users in GroupA should able to view the bugs raised by other users in same GroupA
How to achieve this issue?

Thanks
Renuka
0
prenuka
4/11/2019 4:49:56 AM
mozilla.support.bugzilla 10054 articles. 0 followers. Post Follow

6 Replies
13 Views

Similar Articles

[PageSpeed] 14

Guten Tag prenuka@gmail.com,
am Donnerstag, 11. April 2019 um 06:49 schrieben Sie:

> Group A
> ENTRY, MANDATORY MANDATORY, CanEdit selected
> Users in Group A  are not able to view the bugs raised by the other
> users in Group A but able to view the bugs raised by them.=20

Are these really all settings for product A or does it specifiy
additonal restrictions for other groups? Into which groups are the
bugs ultimately placed you created using different users of your group
A in product A? Check with the individual users if necessary. Are
those bugs really all in the same product and group in the end?

> Group permission selected for this group
> Groups That Can See This Group
> ("Users in X can see users in GroupA" - admin, groupA

I'm somewhat sure that this only affects user searches and such and I
doubt it has influence on placing bugs into groups per product. That's
how I read the docs for "usevisibilitygroups" as well:

> Do you wish to restrict visibility of users to members of specific groups?

Mit freundlichen Gr=FC=DFen,

Thorsten Sch=F6ning

--=20
Thorsten Sch=F6ning       E-Mail: Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Gesch=E4ftsf=FChrer: Andreas Muchow

0
windows
4/11/2019 6:45:57 AM
Guten Tag

Danke Schon fur die Antwort

I have created separate groups for each products.

Yes for product A , i have provided following permission for Group A
ENTRY, MANDATORY MANDATORY, CanEdit selected

Only Group A users will be able to raise bugs  for Product A only i.e obsol=
utely for one  customer in that group

Group A users are able to view the bug raised by themselves but not other u=
sers in the same group for the same product.

I have created similar groups and product restricting to different customer=
s

Thank you
Renuka=20
=20
On Thursday, April 11, 2019 at 12:16:10 PM UTC+5:30, Thorsten Sch=C3=B6ning=
 wrote:
> Guten Tag prenuka@gmail.com,
> am Donnerstag, 11. April 2019 um 06:49 schrieben Sie:
>=20
> > Group A
> > ENTRY, MANDATORY MANDATORY, CanEdit selected
> > Users in Group A  are not able to view the bugs raised by the other
> > users in Group A but able to view the bugs raised by them.=20
>=20
> Are these really all settings for product A or does it specifiy
> additonal restrictions for other groups? Into which groups are the
> bugs ultimately placed you created using different users of your group
> A in product A? Check with the individual users if necessary. Are
> those bugs really all in the same product and group in the end?
>=20
> > Group permission selected for this group
> > Groups That Can See This Group
> > ("Users in X can see users in GroupA" - admin, groupA
>=20
> I'm somewhat sure that this only affects user searches and such and I
> doubt it has influence on placing bugs into groups per product. That's
> how I read the docs for "usevisibilitygroups" as well:
>=20
> > Do you wish to restrict visibility of users to members of specific grou=
ps?
>=20
> Mit freundlichen Gr=C3=BC=C3=9Fen,
>=20
> Thorsten Sch=C3=B6ning
>=20
> --=20
> Thorsten Sch=C3=B6ning       E-Mail: Thorsten.Schoening@AM-SoFT.de
> AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
>=20
> Telefon...........05151-  9468- 55
> Fax...............05151-  9468- 88
> Mobil..............0178-8 9468- 04
>=20
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Gesch=C3=A4ftsf=C3=BChrer: Andreas Muchow

0
prenuka
4/11/2019 8:44:19 AM
On Thursday, April 11, 2019 at 12:16:10 PM UTC+5:30, Thorsten Sch=C3=B6ning=
 wrote:
> Guten Tag prenuka@gmail.com,
> am Donnerstag, 11. April 2019 um 06:49 schrieben Sie:
>=20
> > Group A
> > ENTRY, MANDATORY MANDATORY, CanEdit selected
> > Users in Group A  are not able to view the bugs raised by the other
> > users in Group A but able to view the bugs raised by them.=20
>=20
> Are these really all settings for product A or does it specifiy
> additonal restrictions for other groups? Into which groups are the
> bugs ultimately placed you created using different users of your group
> A in product A? Check with the individual users if necessary. Are
> those bugs really all in the same product and group in the end?
>=20
> > Group permission selected for this group
> > Groups That Can See This Group
> > ("Users in X can see users in GroupA" - admin, groupA
>=20
> I'm somewhat sure that this only affects user searches and such and I
> doubt it has influence on placing bugs into groups per product. That's
> how I read the docs for "usevisibilitygroups" as well:
>=20
> > Do you wish to restrict visibility of users to members of specific grou=
ps?
yes, i want to restrict visibility of users to members of specific groups=
=20

I have created one company group who can see all the bugs from all the prod=
ucts=20
And created products and groups for each different customer

I want restrict the customers groups to view only their own group bugs and =
not other group bugs

I could able to restrict from viewing other product bugs for each group, bu=
t somewhere i have missed.

the user could able to see the bugs raised by themselves but not other user=
 bugs for the same group and for the same product.

I have crosschecked the bugs, the bugs are in the same group and same produ=
ct. I have moved couple of bugs to that product from other product.


Kindly please help me


>=20
> Mit freundlichen Gr=C3=BC=C3=9Fen,
>=20
> Thorsten Sch=C3=B6ning
>=20
> --=20
> Thorsten Sch=C3=B6ning       E-Mail: Thorsten.Schoening@AM-SoFT.de
> AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
>=20
> Telefon...........05151-  9468- 55
> Fax...............05151-  9468- 88
> Mobil..............0178-8 9468- 04
>=20
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Gesch=C3=A4ftsf=C3=BChrer: Andreas Muchow

0
prenuka
4/11/2019 9:20:50 AM
Guten Tag prenuka@gmail.com,
am Donnerstag, 11. April 2019 um 11:20 schrieben Sie:

> I have crosschecked the bugs, the bugs are in the same group and
> same product. I have moved couple of bugs to that product from other prod=
uct.

I suggest creating from scratch with one new test product, two new
test users and one new test group. Configure it like you think is
correct and see what happens with the second test user being part of
the group and not. If things don't work as expected, take screenshots
of the test users and their group membership and the group config of
your product, upload them to some image hoster and provide the links
to the files here.

This list removes attachments!

I just configured one of my test products and groups like I understood
your use case and things workes like expected: Some test bug is
visible to both users of my test group depending on if those users are
part of the group or not. So it's not like in your case that only the
reporter can see the bug, but other group members as well and in my
case the new test user was even created after the bug and things.

Said that, the following comes into mind: Make sure that you didn't
customize Bugzilla so that only reporters can access their bugs or
such:

https://bugzilla.readthedocs.io/en/5.0/integrating/extensions.html#altering=
-who-can-change-what

Mit freundlichen Gr=C3=BC=C3=9Fen,

Thorsten Sch=C3=B6ning

--=20
Thorsten Sch=C3=B6ning       E-Mail: Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Gesch=C3=A4ftsf=C3=BChrer: Andreas Muchow

0
utf
4/11/2019 1:34:56 PM
Thank you very much.
Issue has been solved

Danke schon
On Thursday, April 11, 2019 at 7:05:08 PM UTC+5:30, Thorsten Sch=C3=B6ning =
wrote:
> Guten Tag prenuka@gmail.com,
> am Donnerstag, 11. April 2019 um 11:20 schrieben Sie:
>=20
> > I have crosschecked the bugs, the bugs are in the same group and
> > same product. I have moved couple of bugs to that product from other pr=
oduct.
>=20
> I suggest creating from scratch with one new test product, two new
> test users and one new test group. Configure it like you think is
> correct and see what happens with the second test user being part of
> the group and not. If things don't work as expected, take screenshots
> of the test users and their group membership and the group config of
> your product, upload them to some image hoster and provide the links
> to the files here.
>=20
> This list removes attachments!
>=20
> I just configured one of my test products and groups like I understood
> your use case and things workes like expected: Some test bug is
> visible to both users of my test group depending on if those users are
> part of the group or not. So it's not like in your case that only the
> reporter can see the bug, but other group members as well and in my
> case the new test user was even created after the bug and things.
>=20
> Said that, the following comes into mind: Make sure that you didn't
> customize Bugzilla so that only reporters can access their bugs or
> such:
>=20
> https://bugzilla.readthedocs.io/en/5.0/integrating/extensions.html#alteri=
ng-who-can-change-what
>=20
> Mit freundlichen Gr=C3=BC=C3=9Fen,
>=20
> Thorsten Sch=C3=B6ning
>=20
> --=20
> Thorsten Sch=C3=B6ning       E-Mail: Thorsten.Schoening@AM-SoFT.de
> AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
>=20
> Telefon...........05151-  9468- 55
> Fax...............05151-  9468- 88
> Mobil..............0178-8 9468- 04
>=20
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Gesch=C3=A4ftsf=C3=BChrer: Andreas Muchow

0
prenuka
4/12/2019 10:41:39 AM
Guten Tag prenuka@gmail.com,
am Freitag, 12. April 2019 um 12:41 schrieben Sie:

> Thank you very much.
> Issue has been solved

That's good news of course, but it would be even better if you told us
about what the actual problem was in the end and how you solved it. :-)
Questions like yours are pretty popular on the list and what you have
done wrong and did to resolve it might help others solve their
problems as well.

Mit freundlichen Gr=C3=BC=C3=9Fen,

Thorsten Sch=C3=B6ning

--=20
Thorsten Sch=C3=B6ning       E-Mail: Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Gesch=C3=A4ftsf=C3=BChrer: Andreas Muchow

0
utf
4/12/2019 12:22:24 PM
Reply: