How can I isolate a groups issues in a separate project but keep both projects congruent

[Brendan Jackson]

I am relatively new to JIRA so even if this isn't possible, I'm hoping to hear back about suggestions that get my company as close to this goal as possible.

We have a project that contains issues for all of our clients. The privileges are set so that the clients cannot see each other's projects (without downloading a CSV), but this also prevents them from seeing their issues progress or see the latest sprint.

I would like for our client's to only see issues reported by their group in this project. It could be my lacking knowledge of JIRA, but I do not see any permissions that would permit this. So I was hoping as a workaround I could create a new project that only contains issues reported by specific groups members. 

Now here's the difficult part, I want issues to still be linked to the original project. Some examples of this relationship would be...

Project A contains all client issues, Project B contains only group 1's issues from Project A. If I make any edits to group 1's issues in either Project A or Project B, the edits persist in both projects. UNIX uses symbolic links, which is similar to how I want the relationship to be. I want a single issue to be accessed from two different projects, with different permissions for groups on each project.

How can I give my client access to see their issues only?

[Joe Pitt]

@Brendan Jackson has the right idea about security schemes. Since you want to limit the issues by groups I think you'll have a problem with user applying the scheme for their group. You will also need for all the users to have the ability to apply the scheme. This is ripe for user error. I've only used this when I could apply it to the project such as the reporter can only see their issues. 

[Brendan Jackson]

How would you give user groups access exclusively to their own group's issues?

[Joe Pitt]

I don't believe you can do it by default. You'd need to have a scheme with the group name for them to pick.

[Brendan Jackson]

What is the best way to do that?

[Joe Pitt]

I don't know. I'd have to experiment and don't have the time. 

[Ismael Jimoh]

May I ask if having 2 projects, 2 separate boards for each team and one overarching board that includes projects from both projects is an option for you?

Your description is the teams work on separate tasks and you do not want them to overlap. If this is the case, having separate project slots in well.

And since boards are based off filters, you can have a filter that includes both projects:

project in (projA, projB) ORDER BY Rank ASC

To display the issues from both projects and you can even use swimlanes to separate the issues based on the projects.

This is just an alternative and do note that with what @[deleted] it is not that this is impossible but would involve a lot of work to make it work perfectly, oh and you would need add-ons like scriptrunner,JSU, JMWE (I know scriptrunner has this function but you can check the other 2 as they are easier to implement) that enhance your workflow so as to remove the need for users setting the security level.

• Scriptrunner has a post-function for setting Security Level and this can be added to the on Create transition.

These are just early suggestions and I would need to sit down and review lots of potential conditions to get this working properly.

[Ismael Jimoh]

Hi @Brendan Jackson 

If the issues must be in the same project then consider looking at issue security in Jira. It should achieve what you described. Just make sure you set the right issue security.

https://confluence.atlassian.com/adminjiraserver073/configuring-issue-level-security-861253265.html It let’s you specify which group has access to what issue and even a CSV export would not show issues they are not meant to see

[Brendan Jackson]

It sounds like you are saying I can use this to set a groups permissions to whatever I want, for their own groups issues, excluding issues they did not create?