Prevent some users from creating tickets via web, while allowing creation via email

Scenario: Service desk project. One issue type for the intake of tickets, created via email by JIRA and non-JIRA users. Other issue types for the real work, tickets are received via email and moved, or created by the team based on phone or walk up requests. Because of the email creation component, the project is open to others to create tickets.

Problem: Some people continue to create tickets manually circumventing the processes in place, creating SLA problems, causing issues to get missed. People who are not part of that that team need to be prevented from making tickets in the work issue types. If they were confined to just the intake issue type that's OK.

Some poorly thought out ideas:

- Maybe something with the behaviors plugin? Sabatoging a required piece of data on issue types 1-5 so that only the team can edit that field preventing creation, leaving the 6th that is used for all email creation as-is.

- The nuclear option is to peel the intake issue type off into it's own project, lock down the other.

- It's a training opportunity, sure, but that doesn't fix the problem technically

Any creative workarounds or ideas?

2 answers

1 accepted

Closing this question.

Here's a suggestion with JEMH, why not blacklist email submissions for particular mailbox (your input mailbox) for users from a given domain (your internal users). You dont say how many 'some' is, if its <10, you can add them individually, if its more like 500, you may want to consider flipping it over and blacklisting everyone internally, then whitelisting individuals that are allowed. more info.

If you block the project to internal users using an appropraite securirty scheme, add in you r'support peeps' only, you should be done?

But, of course, if there are internal users you do want to allow, well, just create a group for them and add the group to the users role?

If I limit creation to a group of people, doesn't that kill my ability to accept tickets from anyone via email that are not part of that group?

No, JEMH can force a specific 'default' reporter, whether the sender email is associated witha JIRA user or not; Email addresses can be stored separately and used for notifications in the same way.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,870 views 12 18
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot