Permissions problem

[forums-5]

Hi,
my name is Cristian and I use Jira in my company. I am responsible for Jira manager.
I`ve created three different projects, each with groups and users.
My question is how to do users of the same group did not see the issue of other users in that  group.

Any idea.
 
Thank you
--
Post by cristiano - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38525
_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user

[forums-5]

That's pretty straightforward. Permission schemes are used for this. You set the Browse permission on project A to Group A, etc.
--
Post by napplebaum - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38525
_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user

[forums-5]

If you set the browse permission to "reporter" instead of the group then they will only be able to see their own issues and not everyone's issues. Is that what you want?
--
Post by MHarper - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38525
_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user

[forums-5]

thank you very much for your reply. That was what he wanted, but when you add that option (reporter) was a problem that had not happened. All groups can see all projects.

Any thoughts?
--
Post by cristiano - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38525
_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user

[forums-5]

Matt and I gave different suggestions. By using Matt's suggestion, allowing "Reporter" to view issues, then that's exactly what will happen. All users will see all projects (but only their own issues within them). My suggestion was to restrict Browse permission by group. Then they will only see their own projects.
--
Post by napplebaum - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38525
_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user

[forums-5]

I suspect you need to use groups to segregate your projects.  If, for example, you have projects A, B and C, then you can create groups called A, B and C, with three permission schemes, one saying "Group A = browse", the second "Group B = browse" and you can guess the third.

Another option would be to define a single permission scheme that uses "roles" instead of groups.  For example set "Browse = role of user".  Then, you (or your project leads) can add users into each project as appropriate, and they'll only be able to see the projects they have been added to.


Also, re Matt's suggestion - The "reporter" permission doesn't work the way most people expect it to when it comes to "browse" permissions.

The problem is that there is a hidden assumption in the code which sort of makes sense, but gets in the way.  It's quite difficult to explain, and I'm not sure I would do it any justice.

But, I do know the fix - you need to edit ./atlassian-jira/WEB-INF/classes/permission-types.xml and uncomment the second-to-last block, restarting Jira when you're done.
{code}
    <!--  Uncomment & use this permission to show only projects where the user has create permission and issues within that where they are the reporter. -->
    <!--  This permission type should only ever be assigned to the "Browse Projects" permission. -->
    <!--  Other permissions can use the "reporter" or "create" permission type as appropriate. -->
    <type id="reportercreate" enterprise="true">
        <class>com.atlassian.jira.security.type.CurrentReporterHasCreatePermission</class>
    </type>
{code}

You will then have an extra option on the bottom of the list of people-types you can allow.  That will allow a user to browse issues in a project that they've reported in without opening up the project to all users.
--
Post by broughn2 - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38525
_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user

[forums-5]

Yes - Nic is suggesting the same as what I did originally. The link to Nic's "Reporter with Create" permission can be found here:

http://confluence.atlassian.com/display/JIRA/Current+Reporter+Browse+Project+Permission

Although that won't help you for what you want.
--
Post by napplebaum - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38525
_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user

[forums-5]

NICE! That's a cool feature that will help out a lot :)
--
Post by MHarper - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38525
_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user