Issue Security Based On Reporter Domain

We are trying to use our JIRA OnDemand instance with a single project for customer support. In general, its working OK, but we have customers where they want to be able to see each others issues.

I have read about the CC Users suggestion that JIRA uses, but we are hoping for something simpler. I can't allow users to browse the userlist (different customers should not be able to see each other) and having them type them in themselves (like Atlassian does) is not really an option as it is a large list.

My thought was to have a group for the customer that matched the reporter's domain name. Then somehow set the issues security to allow people from that group.

I have the reporter's domain name custom field included in the issue fields, but I can't figure out any way to use that in a workflow post-function or something like that to actually take advantage of it.

Any ideas would be greatly appreciated.

2 answers

1 accepted

Accepted Answer
1 vote

I have managed to partly answer my own question. The trick is to not use an issue security scheme, but rather a regular security scheme. On the approriate actions, you can include a customer group field.

So:

  • I create a user group for each customer that is the same as the name of their domain.
  • On the project, I have added a custom field: single group picker called Visible To.
  • I set security to Browse Project, and others, to include Custom Group Field: Visible To.

This works perfectly. Now, if the user is a member of the group specified in Visible To, they can see the issue.

BUT: In order for this to work, I need to issues to automatically have Visible To populated with the name of the appropriate group. I tried adding a Workflow Post-function after Create to copy the value of the Reporter Domain custom field (part of the Jira Toolkit plugin) to the Vsiible To field. Unfortunately it is not copying the value.

Any ideas?

I had to put the copy function after the create issue function.

Great description (and smart solution). I could not get the reporter domain to work so instead I used a user property called company. This way you could actually have companies with different e-mails in the same group. Thanks for the help :)

Great description (and smart solution). I could not get the reporter domain to work so instead I used a user property called company. This way you could actually have companies with different e-mails in the same group. Thanks for the help :)

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 25, 2018 in Jira

Atlassian Research Workshop opportunity on Sep. 28th in Austin, TX

We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...

432 views 7 5
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you